Computer History Wiki - User contributions [en]

DUP11 synchronous serial line interface

2026-10-02T07:53:26Z

Vaxorcist: /* External links */ Fixed external links

[[Image:DUP11-M7867.jpg|300px|thumb|right|DUP11 M7867 board]]

The '''DUP11''' is an early [[synchronous serial line]] [[peripheral|interface]] for the [[UNIBUS]]. It was basically a [[DU11 synchronous serial line interface|DU11]] with [[cyclic redundancy check|CRC]] computation in [[hardware]]. Like the earlier DU11, it used [[programmed I/O]] (with separate receive and transmit [[interrupt]]s) to transfer data; it was double-[[buffer]]ed for both input and output. It could operate in either [[half-duplex]] or [[full-duplex]], at [[baud rate]]s up to 9.6K bits/second.

Both [[byte]]-oriented (e.g. [[DDCMP]], [[BISYNC]]) and [[bit]]-oriented (e.g. [[SDLC]], [[HDLC]]) [[protocol]]s were supported; for error detection, a variety of CRC algorithms, depending on the protocol in use on the line, were supported. The [[character]] length was 8 [[bit]]s; the [[sync character]] was selectable under program control, as well as the modem control leads. It apparently supported idling (sending the sync character); the line could also be set to a [[serial line|mark]] condition when not transmitting characters. The DUP11 could also be set to discard additional incoming sync characters.

It was intended to interface to Bell 200 series [[modem]]s (models 201, 208 and 209) and equivalents.

It was a [[DEC card form factor|hex]] card, the '''M7867'''; it plugged into an [[Small Peripheral Controller|SPC]] slot. A [[Berg connector|Berg header]] on the card connected to a short [[flat cable]] which led off to a connector.

==Registers==

{| border=1
! Register !! Abbreviation !! Address
|-
|Receiver Status Register || RxCSR || 16xxx0
|-
|Receiver Data Buffer Register (read only) || RxDBUF || 16xxx2
|-
|Parameter Status Register (write only) || PARCSR || 16xxx2
|-
|Transmitter Status Register || TxCSR || 16xxx4
|-
|Transmitter Data Buffer Register || TxDBUF || 16xxx6
|}


===16xxx0: Receiver Status Register (RxCSR)===

{{16bit-header}}
| DSCA || RING || CTS || CARR || RACT || SECRCV || DSR || SSYNC || RDN || RDIE || DSIE || REN || SECXMT || RTS || DTR || DSCB
{{16bitoctal-bitout}}

* DSCA - Data Set Change A; set for any change on Ring, Clear to Send (optionally DSCB lines)
* RING - Ring Indicator
* CTS - Clear to Send
* CARR - Carrier
* RACT - Receiver Active; set after the first character has been assembled
* SECRCV - Secondary Receive Data
* DSR - Data Set Ready
* SSYNC - Strip Sync; sync characters following the first are discarded - only used with byte-oriented protocols
* RDN - Receive Done Flag; set when the receive buffer contains an assembled character
* RDIE - Receive Interrupt Enable; allows an input interrupt when Receive Done is set
* DSIE - Data Set Interrupt Enable; allows an input interrupt when DSCA is set
* REN - Receiver Enable; when first set, the receiver looks for synchronization
* SECXMT - Secondary Transmit Data
* RTS - Ready to Send
* DTR - Data Terminal Ready
* DSCB - Data Set Change B; set for any change on Carrier, Data Set Ready, Secondary Received Data

===16xxx2: Receiver Data Buffer Register (RxDBUF)===

{{16bit-header}}
| ERR || OVR || Rsvd || RCRC || Rsvd || RABO || REOM || RSOM || colspan=8 | DDAT
{{16bitoctal-bitout}}

* ERR - Error
* OVR - Overrun
* RCRC - Receiver CRC
* RABO - Received Abort
* REOM - End of Received Message
* RSOM - Start of Received Message
* RDAT - Received Data Buffer

===16xxx2: Parameter Status Register (PARCSR)===

{{16bit-header}}
| DEC || colspan=2 | Rsvd || SEC MD || colspan=2 | Rsvd || CRC INH || Rsvd || colspan=8 | SEC ADDR/RSYNC
{{16bitoctal-bitout}}

* DEC - DEC Mode
* SEC MD - Secondary Mode
* CRC INH - CRC Inhibit
* SEC ADDR/RSYNC - Secondary Station Address / Receiver Sync

===16xxx4: Transmitter Status Register (TxCSR)===

{{16bit-header}}
| DLT || MTDO || MCLK || MMSB || MMSA || MID || TACT || DRST || TDN || TIE || Unused || SEND || HDFD || colspan=3 | Unused
{{16bitoctal-bitout}}

* DLT - Transmitter Data Late Error
* MTDO - Maintenance Transmit Data Out
* MCLK - Maintenance Clock
* MMSB - Maintenance Mode Select B
* MMSA - Maintenance Mode Select A
* MID - Maintenance Input Data
* TACT - Transmitter Active
* DRST - Device Reset
* TDN - Transmitter Done; set when the Transmitter Data Buffer id ready for the next character
* TIE - Transmitter Interrupt Enable; allows a transmit interrupt when Transmit Done is set
* SEND - Send; enables the transmitter logic
* HDFD - Half-Duplex/Full-Duplex

===16xxx6: Transmitter Data Buffer Register (TxDBUF)===

{{16bit-header}}
| Unused || RCRCIN || Unused || TCRCIN || MTIM || TABO || TEOM || TSOM || colspan=8 | TDBUF
{{16bitoctal-bitout}}

* RCRCIN - Receiver CRC Internal Maint
* TCRCIN - Transmitter CRC Internal Maint
* MTIM - Maintenance Timer
* TABO - Transmit Abort
* TEOM - Transmit End of Message
* TSOM - Transmit Start of Message
* TDBUF - Transmitter Data Buffer

==See also==

* [[DP11-A synchronous serial line interface]]

==External links==

* [https://www.vaxhaven.com/images/7/7c/EK-DUP11-OP-001.pdf DUP11 bit synchronous interface user's manual] (EK-DUP11-OP-001)
* [https://www.vaxhaven.com/images/5/55/EK-DUP11-OP-002.pdf DUP11 Bit Synchronous Interface User's Manual] (EK-DUP11-OP-002)
* [https://www.vaxhaven.com/images/a/a1/EK-DUP11-MM-003.pdf DUP11 Bit Synchronous Interface Maintenance Manual] (EK-DUP11-MM-003)

[[Category: UNIBUS Synchronous Serial Interfaces]]

DEC acronyms

2026-09-19T15:17:34Z

Vaxorcist: CDD = Common Data Dictionary and DTR = DATATRIEVE added

'''Acronyms''' from [[Digital Equipment Corporation]]. (Listings given in ''italics'' are not just DEC acronyms.)

{| class="wikitable"
|-
! Acronym
! Meaning
|-
| APT
| [[Automated Product Test]]
|-
| BR
| [[Bus request line|Bus Request]] ([[UNIBUS]])
|-
| CBOX
| Cache Box
|-
| CDD
| [[Common Data Dictionary]]
|-
| CFS
| [[Common File System]] ([[PDP-10]]/[[TOPS-20]])
|-
| CI
| [[Computer Interconnect]]
|-
| CMI
| [[CPU/Memory Interconnect]]
|-
| CRD
| [[Customer Runnable Diagnostic]]
|-
| CSC
| [[Customer Support Center]]
|-
| CSS
| [[Computer Special Systems]]
|-
| DBN
| [[DSA Standard Disk Format#Diagnostic Block Numbers (DBNs)|Diagnostic Block Number]]
|-
| DCL
| [[Digital Command Language]]
|-
| DCS
| [[Digital Classified Software]]
|-
| DDC
| [[Digital Diagnostic Center]]
|-
| DRS
| [[Diagnostic Runtime Services]]
|-
| DSA
| [[Digital Storage Architecture]]
|-
| DSC
| [[Disk Save and Compress]]
|-
| DSDF
| [[DSA Standard Disk Format]]
|-
| DSR
| [[Digital Standard Runoff]]
|-
| DSSI
| [[Digital Storage Systems Interconnect]]
|-
| DTR
| [[DATATRIEVE]]
|-
| DUP
| [[Diagnostic and Utility Protocol]]
|-
| EBOX
| Execution Box
|-
| ECO
| ''[[Engineering Change Order]]''
|-
| FRU
| ''[[Field Replaceable Unit]]''
|-
| IBOX
| Instruction Box
|-
| GPX
| [[Graphics Processing Extension]]
|-
| GIDIS
| [[General Image Display Instruction Set]]
|-
| JBOX
| Junction Box
|-
| LAD
| Local Area Disk
|-
| LAST
| Local Area System Transport
|-
| LAT
| Local Area Transport
|-
| LAVC
| [[Local Area VAXcluster]]
|-
| LBN
| ''[[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Logical Block Number]]''
|-
| MDM
| [[MicroVAX Diagnostic Monitor]]
|-
| MBOX
| Memory Box
|-
| MCR
| [[Monitor Console Routine]]
|-
| MDS
| [[Maintenance Documentation Service]]
|-
| MSCP
| [[Mass Storage Control Protocol]]
|-
| ODS-2
| [[On-disk Structure 2]]
|-
| OTS
| [[Object Time System]]
|-
| PPD
| [[Systems Communication Architecture|Port/Port Driver Layer]]
|-
| PPL
| [[Periodic Payment License]]
|-
| RBN
| [[DSA Standard Disk Format#Replacement Block Numbers (RBNs)|Replacement Block Number]]
|-
| RCT
| [[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Replacement/Revectoring Control Table]]
|-
| RDC
| [[Digital Remote Diagnosis Center]]
|-
| RMS
| [[Record Managment Services]]
|-
| SBB
| [[System Building Block]]
|-
| SBI
| [[Synchronous Backplane Interconnect]]
|-
| SCA
| [[Systems Communication Architecture]]
|-
| SCS
| [[Systems Communication Architecture|Systems Communication Services]]
|-
| SDA
| [[System Dump Analyzer]]
|-
| SDB
| [[Standard Drive Bus]]
|-
| SDI
| [[Standard Disk Interconnect]]
|-
| SDL
| Structure Definition Language
|-
| STI
| [[Standard Tape Interconnect]]
|-
| UETP
| [[User Environment Test Package]]
|-
| UPI
| [[DEC Unique Product Identifier|Unique Product Identifier]]
|-
| UQSSP
| [[UNIBUS]] [[QBUS]] Storage Systems Port
|-
| UUT
| Unit Under Test
|-
| UWS
| [[ULTRIX Worksystem Software]]
|-
| VAXBI
| [[VAX Bus Interconnect]]
|-
| VBOX
| Vector Box
|-
| VDS / VAX/DS
| [[VAX Diagnostic Supervisor]]
|-
| VUP
| [[VAX Unit of Performance]]
|-
| VWS
| [[VAX Workstation Software]]
|-
| WCS
| [[Writable Control Store]]
|-
| XBN
| [[DSA Standard Disk Format#External Block Numbers (XBNs)|External Block Number]]
|-
| XMI
| [[Extended Memory Interconnect]]
|}

[[Category: Digital Equipment Corporation]]
[[Category:DEC Naming/Numbering Schemes]]
[[Category: DEC Acronyms]]

PDP-11

2026-09-16T07:54:57Z

Vaxorcist: /* DEC OS's */ "TRAX" added

The '''PDP-11''' is a series of [[minicomputer]]s introduced in 1969 [1] by the [[Digital Equipment Corporation]] (DEC), in production by them from 1970-1990. Their life-time spanned a period of momentous changes in the computer world: when they were first introduced [[integrated circuit]]s had just been introduced (small ones, containing only a few simple [[gate]]s); and for a little less than half their life, [[core memory]] was still the standard [[main memory]] technology. By the end, the now-ubiquitous [[microprocessor]]s and [[dynamic RAM]] had completely taken over.

[[Image:KA11FrontPanel.jpg|right|thumb|300px|[[Front panel]] of the [[KA11 CPU|KA11]], the first PDP-11 model]]

It was the machine which made [[UNIX]], which now seems to have taken over the world (in the form of [[Linux]]) widely known and popular.

The machine [[word]] size was 16 bits, and it was a [[general register]] [[architecture]]. Although it was not the first to feature the latter, its wide distribution (in 1980, it was the world's best-selling computer) and its novel addressing modes (below) have helped influence almost all later machines to follow that path.

(For more information about the architecture, including its innovative and much-copied [[stack]]-oriented [[PDP-11 architecture#Addressing modes|addressing modes]], see [[PDP-11 architecture|here]].)

PDP-11's came in two groups: those which used the [[UNIBUS]] for a bus, and the later ones which used the [[QBUS]]. Eventually DEC stopped producing [[UNIBUS]] PDP-11's (the last were the [[PDP-11/44]] and [[PDP-11/24]]); later 'UNIBUS' machines (the [[PDP-11/84]] and [[PDP-11/94]]) actually contained QBUS processors with a QBUS<->UNIBUS adapter board.

Towards the end of its life, there were several microprocessor implementations of the PDP-11, as [[integrated circuit|chips]]. After DEC discontinued production of PDP-11's, the line was sold to [[Mentec]], who produced a few newer models.

== PDP-11 Models and notes ==

{| class="wikitable"
! Model !! Introduced !! Bus Type !! Addressing !! [[PDP-11 Memory Management|Split I & D]] !! Notes !! Speed (VUPS)
|-
| [[PDP-11/20|11/20]] || 1969[1] ||[[UNIBUS]] || 16-bit || no || ||
|-
| [[PDP-11/05|11/05]] || 1972 || UNIBUS || 16-bit || no || OEM model ||
|-
| [[PDP-11/10|11/10]][*] || 1972 || UNIBUS || 16-bit || no || ||
|-
| [[PDP-11/15|11/15]] || 1972 || UNIBUS || 16-bit || no || OEM model ||
|-
| [[PDP-11/35|11/35]] || 1973 || UNIBUS || 18-bit || no || OEM model ||
|-
| [[PDP-11/40|11/40]] || 1973 || UNIBUS || 18-bit || no || ||
|-
| [[PDP-11/45|11/45]] || 1973 || UNIBUS || 18-bit || yes || core memory ||
|-
| [[PDP-11/50|11/50]] || 1975 || UNIBUS || 18-bit || yes || [[Metal Oxide Semiconductor|MOS]] memory ||
|-
| [[PDP-11/55|11/55]] || 1976 || UNIBUS || 18-bit || yes || fast bipolar memory ||
|-
| [[PDP-11/70|11/70]] || 1975 || UNIBUS || 22-bit || yes || || 0.6
|-
| [[PDP-11/03|11/03]] || 1975 || [[QBUS]] || 16-bit || no || first QBUS model || 0.05
|-
| [[PDP-11/04|11/04]] || 1976 || UNIBUS || 16-bit || no || || 0.11
|-
| [[PDP-11/34|11/34]] || 1976 || UNIBUS || 18-bit || no || || 0.21
|-
| [[PDP-11/60|11/60]] || 1977 || UNIBUS || 18-bit || no || writable control store ||
|-
| [[PDP-11/23|11/23]] || 1979 || QBUS || 18-bit ''or'' 22-bit || no || first [[F-11]] || 0.12
|-
| [[PDP-11/24|11/24]] || 1979 || UNIBUS || 22-bit || no || only UNIBUS model to use F-11 chip || 0.18
|-
| [[PDP-11/44|11/44]] || 1979 || UNIBUS || 22-bit || yes || last non-LSI PDP-11 || 0.42
|-
|[[PDP-11/23-PLUS|11/23+]] || 1981 Nov || QBUS || 22-bit || no || || 0.18
|-
| [[PDP-11/73|11/73]] || 1983 || QBUS || 22-bit || yes || first [[J-11]] machine, 15MHz, integrated [[FPU]], also first [[PMI]] PDP-11 || 0.45
|-
| [[PDP-11/53|11/53]] || 1984 || QBUS || 22-bit || yes || S-box or standard QBUS, integrated FPU, 768KiW memory || 0.29
|-
| [[PDP-11/83|11/83]] || 1988 || QBUS || 22-bit || yes || J-11 at 18MHz, integrated FPU || 0.72
|-
| [[PDP-11/84|11/84]] || 1988 || UNIBUS || 22-bit || yes || J-11 at 18MHz, integrated FPU || 0.72
|-
| [[PDP-11/93|11/93]] || 1990 || QBUS || 22-bit || yes || J-11 at 18MHz, integrated FPU, 2MiW onboard memory || 1.0
|-
| [[PDP-11/94|11/94]] || 1990 || UNIBUS || 22-bit || yes || J-11 at 18MHz, integrated FPU, 2MiW onboard memory || 1.0
|}

''<span style="font-size:70%">[*]The name PDP-11/10 was recycled by DEC from an earlier [[KA11 CPU]]-based 11/10 from 1969, or at least it existed in advertisements[1]</span>''

==Operating Systems==

There were a number of well-known [[operating system]]s for the PDP-11. Many were produced by [[DEC]] themselves, but several were produced by third-parties. Often DEC would purchase or re-brand such an OS and re-sell it as their own product; for example, UNIX sold as [[Ultrix]] by DEC.

UNIX was not originally a PDP-11 system (it was born on the [[PDP-7]]), but it moved to the PDP-11 shortly after it was first created, and spread widely there (since PDP-11's were common machines, due to their relatively low cost and good engineering), with the real explosion of use starting with [[UNIX Sixth Edition]].

===UNIX===

* [[UNIX First Edition]]
* [[UNIX Second Edition]]
* [[UNIX Third Edition]]
* [[UNIX Fourth Edition]]
* [[UNIX Fifth Edition]]
* [[UNIX Sixth Edition]]
* [[Unix Seventh Edition]]

These are the original Bell Laboratories releases of Unix; the first 4 were only internal to Bell, the Fifth saw limited distribution outside it, and the Sixth took over the world.

* [[LSX]]
* [[MINI-UNIX]]

For PDP-11's without [[memory management]].

* [[System III]]

This was the first shipping Unix distro by AT&T. It only supported the PDP-11 and [[VAX]] computers.

* [[2.9 BSD]]

This version was a port of the [[4.3 BSD]] feature set to the PDP-11. Although considered an impossible goal by many, it accomplished this by using [[overlay]]s for portions of the [[kernel]], and to allow for user programs larger than 64KB.

* [[2.10 BSD]]
* [[2.11 BSD]]

This last version is still supported, and if one really felt the need to load a Unix for use on a PDP-11 this would be the best fit. It has support for [[TCP/IP]], large memory space and is the best UNIX experience one can get going to get on a 16-bit mini.

===DEC OS's===

* [[DOS-11]]
* [[RSX-11]]
* [[RSTS/E]] - a descendant of [[RSTS-11]]
* [[RT-11]]
* [[Interactive Application System|IAS]]
* [[TRAX]]

Technically also an OS is [[XXDP diagnostic package|XXDP]], which is an 'overseer' for running the PDP-11 [[diagnostic]]s produced/provided by DEC.

===Real-time OS's===

PDP-11's were very popular in [[real-time]] and [[data network]]ing uses; a number of OS's were developed for such environments:

* [[ANTS terminal system|ANTS]]
* [[ELF operating system|ELF]]
* [[MOS operating system|MOS]] - an ELF descendant
* [[MERT operating system|MERT]] - another Bell system
* [[MINITS]] - network appliance framework

===Miscellaneous===

* [[SITS]] - "Small [[Incompatible Timesharing System|ITS]]" for running Logo
* [[Camexec]] - hosted the Camex typesetting system
* Trantor - written for the MIT Applied Mathematics Department

==Simulators==

There a number of good [[simulator]]s for the PDP-11:

* [[SIMH]]
* [[Ersatz-11]]

The latter is less well known than the ubiquitous SIMH, but is very fast; simulated systems running on Ersatz-11 are usually faster than real PDP-11's.

==New Emulator Hardware==

* [[UniBone/QBone]]

==See also==

* [[PDP-11 architecture]]
* [[PDP-11 Memory Management]]
* [[MicroNote]]s
* [[UNIBUS memories]]
* [[QBUS memories]]
* [[UNIBUS peripherals]]
* [[QBUS peripherals]]
* [[UNIBUS boot ROMs]]
* [[QBUS boot ROMs]]
* [[H95xx-H96xx Series of DEC Cabinets and Accessories]]
* [[List of VAX models with PDP-11 compatibility mode]]
* [[PDP11GUI]]

==Further reading==

* ''PDP-11 Family Differences'', [[MicroNote]] #053

==External links==

* [http://www.bitsavers.org/pdf/dec/pdp11/ PDP11] - Documentation at [[Bitsavers]]
** [http://www.bitsavers.org/pdf/dec/pdp11/catalogs/ED-25116-18_PDP-11_Systems_and_Options_Catalog_Jul83.pdf PDP-11 Systems & Options Catalog] (July-September 1983) - late in the run, but a voluminous look at what was available at that time
** [http://www.bitsavers.org/pdf/dec/pdp11/memos/ memos] - Interesting internal DEC memos about the PDP-11
*** [http://www.bitsavers.org/pdf/dec/pdp11/memos/690111_How_Good_Is_The_PDP-11.pdf How Good is the PDP-11?] - interesting early comparison with competitors
* [https://gordonbell.azurewebsites.net/Digital/PDP%2011%20Handbook%201969.pdf PDP-11 Handbook (1969)]
* [http://s3data.computerhistory.org/brochures/dec.pdp-11.1977.102646131.pdf PDP-11 Variations on a Theme] - marketing brochure from DEC
* [https://gordonbell.azurewebsites.net/CGB%20Files/New%20Architecture%20PDP11%20SJCC%201970%20c.pdf A new architecture for mini-computers - The DEC PDP-11] - the [[AFIPS]] paper which introduced the PDP-11
* [http://ana-3.lcs.mit.edu/~jnc/tech/pdp11/PDP-11_Models.html PDP-11 Recognition] - Illustrated guide to identifying PDP-11 models
* [http://pdp-11.trailing-edge.com/ The PDP-11 archives] - miscellaneous software, links 
* [https://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/ The PDP-11 archives at metalab.unc.edu]
** [https://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/hardware/ PDP-11 hardware] - large collection of odds and ends
* [https://hampage.hu/pdp-11/ PDP-11]
** [https://hampage.hu/pdp-11/main.html The Pre-Life of a Legend is another Legend]
** [http://hampage.hu/pdp-11/birth.html How the PDP-11 Was Born (according to Larry McGowan)]
* [https://pdp-11.org/ PDP-11 history and links to materials]
* [https://www.pdp-11.nl/ Henk's DIGITAL computer room] - an amazing collection of PDP-11's
* [https://www.computercollection.net/pdp11/index.htm The PDP-11 Family] - another significant collection
* [https://arstechnica.com/gadgets/2022/03/a-brief-tour-of-the-pdp-11-the-most-influential-minicomputer-of-all-time/ A brief tour of the PDP-11, the most influential minicomputer of all time] - has some minor errors, but generally good
* [https://gordonbell.azurewebsites.net/Digital/PDP11_Arch_Enhance_Strategy_75.pdf Proposal for PDP-11 I/O Architecture]
* [http://gordonbell.azurewebsites.net/cgb%20files/what%20have%20we%20learned%20from%20the%20pdp-11%201977%20c.pdf What Have we Learned From the PDP-11?] - a retrospective on a group of papers by Gordon Bell
* [https://gordonbell.azurewebsites.net/Digital/Bell_Strecker_What_we%20_learned_fm_PDP-11c%207511.pdf Computer Structures: What Have we Learned From the PDP-11?]

==References==

# [http://vintagecomputer.net/digital/PDP11-20/PDP11_Price-List_19691215.pdf PDP-11/20 Price List]

{{PDP-11}}

[[Category: PDP-11s]]
[[Category: DEC Architectures]]
[[Category: 16-bit Computers‎]]

SIMH

2026-09-08T15:46:51Z

Vaxorcist: /* SIMH Flavors */ Update current SimH Classic version

'''SIMH''' consists of simulators for a lot of different machines, and as such, is a very important emulator for anyone interested in computer history; in particular, that of [[Digital Equipment Corporation|DEC]] systems, as the PDPs and even some [[VAX]] models are well emulated by it.

It can even emulate network interfaces for some of the simulated computers, e.g. the [[PDP-10]], [[PDP-11]] and VAX, so the emulated systems can network directly onto the [[Internet]], if the emulated operating system supports it, like BSD or [[VMS]].

SIMH was primarily written by Bob Supnik of [[Zork]] porting fame, and is now widely contributed to by others as well.

== SIMH Flavors ==

For some time passed there are three flavors of SIMH now:

* [[SimH Classic]] ([http://simh.trailing-edge.com/ http://simh.trailing-edge.com/])
* [["New" SIMH]] ([https://github.com/simh/simh https://github.com/simh/simh])
* [[OpenSIMH]] ([https://opensimh.org/ https://opensimh.org/])

It is relatively hard for a beginner to decide which way to go. I will not give any specific advice, but some short descriptions:

'''SimH Classic''' is the oldest one, whereof the others were forked later on. It is Bob Supnik work mostly, except for some HP simulators. Development apparently stopped (or at least slowed down) in December 2022. The current version is SIMH V3.12-5.

'''"New" SIMH''' was the first bigger fork and added a lot more simulated computer systems.

'''"OpenSIMH"''' forked from "New" SIMH because of insurmountable different opinions of both maintainers and contributors.

== Usage ==

SIMH can either take in configuration parameters interactively, or you can store them in a file. If the file is the name of the emulator+.ini it will load them automatically (eg vax.exe loads vax.ini automatically). Once running, the CONTROL+E key will break the emulation and bring you back to the SIMH console where you can alter the running state.

Networking is covered in the [[Networking with SIMH]] guide.

[[Category: Emulators]]

== SIMH Media Handling ==

SIMH handles computer storage media in the form of data files called "images" for:

* [[Punched card]]s
* [[Paper tape]]s
* [[DECtape]]s
* [[Magnetic tape]]s
* [[Disk]]s

All of these image files are said to be interchangeable between the three SIMH flavors with one exception: Image files used with "New" SIMH may be unreadable with the other two flavors because of 512 byte of meta data appended to the standard SIMH images.

Sorry, Windows folks, the next two commands are for [[Linux]] only! -
If someone knows how to do the same in [[Windows]], please add it here.

You can visualize the appended metadata under Linux with (example image file trek7.rk7):

$ tail -c 512 trek7.rk7 | hexdump -C
00000000 73 69 6d 68 56 41 58 20 31 31 2f 37 35 30 00 00 |simhVAX 11/750..|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000040 00 00 00 00 52 4b 30 37 00 00 00 00 00 00 00 00 |....RK07........|
00000050 00 00 00 00 00 00 02 00 00 00 d2 1e 00 00 00 02 |................|
00000060 4d 6f 6e 20 41 70 72 20 20 33 20 30 39 3a 31 39 |Mon Apr 3 09:19|
00000070 3a 32 34 20 32 30 32 33 0a 00 00 00 00 02 00 00 |:24 2023........|
00000080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 fa 1e 03 18 |................|
00000200

In the metadata you can see:
* the simulated computer model: <code>simhVAX 11/750</code>
* the disk model: <code>RK07</code>
* the time stamp: <code>Mon Apr 3 09:19:24 2023</code>

The problem can be cured under Linux using (example image file trek7.rk7):
$ truncate -s -512 trek7.rk7
This truncates 512 bytes (the metadata) at the end of the image file.

Keep in mind that the <code>truncate</code> command truncates whatever file you specify, so look first if metadata is present.

'''Another possible pitfall:''' <br>If you leave out the <code>-</code> (minus) before the <code>512</code>, you will end up with a corrupted image of 512 bytes only!

'''Caution:''' <br>
'''Truncating does not work with SIMH disk images in [[VHD]] format!!!'''

[[Category: Emulators]]

SIMH

2026-09-08T15:44:16Z

Vaxorcist: Vaxorcist moved page SIMH/Draft to SIMH: Distinction between SimH variants

'''SIMH''' consists of simulators for a lot of different machines, and as such, is a very important emulator for anyone interested in computer history; in particular, that of [[Digital Equipment Corporation|DEC]] systems, as the PDPs and even some [[VAX]] models are well emulated by it.

It can even emulate network interfaces for some of the simulated computers, e.g. the [[PDP-10]], [[PDP-11]] and VAX, so the emulated systems can network directly onto the [[Internet]], if the emulated operating system supports it, like BSD or [[VMS]].

SIMH was primarily written by Bob Supnik of [[Zork]] porting fame, and is now widely contributed to by others as well.

== SIMH Flavors ==

For some time passed there are three flavors of SIMH now:

* [[SimH Classic]] ([http://simh.trailing-edge.com/ http://simh.trailing-edge.com/])
* [["New" SIMH]] ([https://github.com/simh/simh https://github.com/simh/simh])
* [[OpenSIMH]] ([https://opensimh.org/ https://opensimh.org/])

It is relatively hard for a beginner to decide which way to go. I will not give any specific advice, but some short descriptions:

'''SimH Classic''' is the oldest one, whereof the others were forked later on. It is Bob Supnik work mostly, except for some HP simulators. Development apparently stopped (or at least slowed down) in December 2022. The current version is SIMH V3.12-3.

'''"New" SIMH''' was the first bigger fork and added a lot more simulated computer systems.

'''"OpenSIMH"''' forked from "New" SIMH because of insurmountable different opinions of both maintainers and contributors.

== Usage ==

SIMH can either take in configuration parameters interactively, or you can store them in a file. If the file is the name of the emulator+.ini it will load them automatically (eg vax.exe loads vax.ini automatically). Once running, the CONTROL+E key will break the emulation and bring you back to the SIMH console where you can alter the running state.

Networking is covered in the [[Networking with SIMH]] guide.

[[Category: Emulators]]

== SIMH Media Handling ==

SIMH handles computer storage media in the form of data files called "images" for:

* [[Punched card]]s
* [[Paper tape]]s
* [[DECtape]]s
* [[Magnetic tape]]s
* [[Disk]]s

All of these image files are said to be interchangeable between the three SIMH flavors with one exception: Image files used with "New" SIMH may be unreadable with the other two flavors because of 512 byte of meta data appended to the standard SIMH images.

Sorry, Windows folks, the next two commands are for [[Linux]] only! -
If someone knows how to do the same in [[Windows]], please add it here.

You can visualize the appended metadata under Linux with (example image file trek7.rk7):

$ tail -c 512 trek7.rk7 | hexdump -C
00000000 73 69 6d 68 56 41 58 20 31 31 2f 37 35 30 00 00 |simhVAX 11/750..|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000040 00 00 00 00 52 4b 30 37 00 00 00 00 00 00 00 00 |....RK07........|
00000050 00 00 00 00 00 00 02 00 00 00 d2 1e 00 00 00 02 |................|
00000060 4d 6f 6e 20 41 70 72 20 20 33 20 30 39 3a 31 39 |Mon Apr 3 09:19|
00000070 3a 32 34 20 32 30 32 33 0a 00 00 00 00 02 00 00 |:24 2023........|
00000080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 fa 1e 03 18 |................|
00000200

In the metadata you can see:
* the simulated computer model: <code>simhVAX 11/750</code>
* the disk model: <code>RK07</code>
* the time stamp: <code>Mon Apr 3 09:19:24 2023</code>

The problem can be cured under Linux using (example image file trek7.rk7):
$ truncate -s -512 trek7.rk7
This truncates 512 bytes (the metadata) at the end of the image file.

Keep in mind that the <code>truncate</code> command truncates whatever file you specify, so look first if metadata is present.

'''Another possible pitfall:''' <br>If you leave out the <code>-</code> (minus) before the <code>512</code>, you will end up with a corrupted image of 512 bytes only!

'''Caution:''' <br>
'''Truncating does not work with SIMH disk images in [[VHD]] format!!!'''

[[Category: Emulators]]

Talk:SIMH

2026-09-08T07:41:06Z

Vaxorcist: /* Renaming / Revising SIMH pages */

== SIMH flavors ==
I think it is time to distinguish between the three flavors of SIMH, although they have a lot in common, but the differences grow steadily.

My proposal is a generic SIMH page which might have the following section after the introduction:

<pre>== SIMH Flavors ==

For some time passed there are three flavors of SIMH now:

* [[Classic" SIMH]] ([http://simh.trailing-edge.com/ http://simh.trailing-edge.com/])
* [["New" SIMH]] ([https://github.com/simh/simh https://github.com/simh/simh])
* [["OpenSIMH"]] ([https://opensimh.org/ https://opensimh.org/])
It is relatively hard for a beginner to decide which way to go. I will not give any specific advice, but some short descriptions:

'''"Classic" SIMH''' is the oldest one, whereof the others were forked later on. It is Bob Supnik work mostly, except for some HP simulators. Development apparently stopped (or at least slowed down) in December 2022. The current version is SIMH V3.12-3.

'''"New" SIMH''' was the first bigger fork and added a lot more simulated computer systems.

'''"OpenSIMH"''' forked from "New" SIMH because of insurmountable different opinions of both maintainers and contributors.</pre>

The generic SIMH page should concentrate on the commonalities; the differences should be explained in the three specific pages linked in the gereric page.

What do my fellow writers think? [[User:Vaxorcist|Vaxorcist]] ([[User talk:Vaxorcist|talk]]) 18:12, 2 April 2023 (CEST)

: Sounds good to me. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 19:14, 2 April 2023 (CEST)

== New content ==

Don't do a 'cut and paste' to move the content from [[SIMH/Draft]] to here; let me know, and I can merge the two pages. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 18:02, 3 April 2023 (CEST)

: O.k., I will [[User:Vaxorcist|Vaxorcist]] ([[User talk:Vaxorcist|talk]]) 18:23, 3 April 2023 (CEST)

== Renaming / Revising SIMH pages ==

I think it is time (or rather, long overdue) to rename the following pages:
* SIMH to "Classic" SIMH
* SIMH/Draft to SIMH
and revise both pages.
What do you think? [[User:Vaxorcist|Vaxorcist]] ([[User talk:Vaxorcist|talk]])

: Is the term "'Classic' SIMH" really in use to refer to the old one? Does that version get enough use to make it worth having a separate article for it (as opposed to just covering it in the same article as the current one)? Mind, I don't have a strong preference either way; I am just trying to work out what makes the most sense.
: I took a look at [[SIMH/Draft]], and the article here, and there is a lot of content in this article that isn't in the Draft one, so we'd need to do something a little more complicated than just do some moves. But let's work out the previous point first. (If we wind up editing the good ideas/content from Draft in to this one, or something, don't worry; I can merge the two histories into one once the editing process is complete.) [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 21:25, 2 September 2026 (UTC)

:: There are three variants of SIMH - whether that is desirable or not. And in my opinion, they differ sufficiently from one another to keep them separate.
::The term "Classic SIMH" has become established to refer to the original SIMH written by Bob Supnik. There's still development on this variant, although somewhat sluggish.

::The "New SIMH" is my own wording - the most important difference to the Classic SIMH is the introduction of asynchronous I/O, an improved clock and several other useful additions. Sometimes you can see that this version is called the "V4 SIMH", but I think that's not a good idea as some time sooner or later it might become V5. I was even tempted to call it "Closed SIMH", but I do not want to provoke anyone, even if I do not like what he's doing.

::"OpenSIMH" is an official name given by the founders of the newest SIMH version.

::All in all I think it needs clearly distinguishable names to avoid more confuision as there already is. Imagine a beginner stumbling into this chaos of three similar, but still very different in detail, versions!

::If I had one wish in "bit heaven", I would pray for the reunification of "New SIMH" and "OpenSIMH."

::There are probably good reasons to keep the "Classic SIMH" and a modernized SIMH apart, but noone needs a third one. What a waste of precious time, ideas and resources! Life is too short for such (some rude words here).

::And you're right, all the SIMH related pages need to be more or less revised or created:

::* SIMH/Draft, which shall become the "common" SIMH page
::* SIMH, which shall become the "Classic SIMH" (it is already, but needs an update)
::* New SIMH, which is probably the hardest to write about (at least for me)
::* OpenSIMH, which carries the spirit and recommandation of Bob Supnik

:: [[User:Vaxorcist|Vaxorcist]] ([[User talk:Vaxorcist|talk]])

::: After thinking about it for a while, I basically agree with you; the way to handle this is to move the current [[SIMH]] page (and history) to [[Classic SIMH]] (since, as you indicate, that name has been "established to refer to the original SIMH"); [[SIMH]] needs to be a new page, basically a disambiguation page, but including a ''short'' history of SIMH. After looking at [[SIMH/Draft]], I guess that will do for this, but it has more detailed content than I would have put there (e.g. the info on file formats); but I guess if those are the same for all the versions, it makes sense to put them there.
::: [[OpenSIMH]] you will have to create; it might start as a stub with just links to the online area/work. For 'New SIMH', I would recommend asking the New SIMH community what they think its formal name should be. Then, you will have to write it! [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 18:07, 6 September 2026 (UTC)

:::: I started with moving SIMH to SimH Classic (which is used on their own web page), but the automatically generated redirect is in the way now for moving SIMH/Draft to SIMH. So this time I do really need your help, don't I? Next steps will be to revise existing/add the missing page(s). [[User:Vaxorcist|Vaxorcist]] ([[User talk:Vaxorcist|talk]]) 07:41, 8 September 2026 (UTC)

SIMH

2026-09-08T07:34:52Z

Vaxorcist: /* SIMH Flavors */ another "SimH Classic" in the text

'''SIMH''' consists of simulators for a lot of different machines, and as such, is a very important emulator for anyone interested in computer history; in particular, that of [[Digital Equipment Corporation|DEC]] systems, as the PDPs and even some [[VAX]] models are well emulated by it.

It can even emulate network interfaces for some of the simulated computers, e.g. the [[PDP-10]], [[PDP-11]] and VAX, so the emulated systems can network directly onto the [[Internet]], if the emulated operating system supports it, like BSD or [[VMS]].

SIMH was primarily written by Bob Supnik of [[Zork]] porting fame, and is now widely contributed to by others as well.

== SIMH Flavors ==

For some time passed there are three flavors of SIMH now:

* [[SimH Classic]] ([http://simh.trailing-edge.com/ http://simh.trailing-edge.com/])
* [["New" SIMH]] ([https://github.com/simh/simh https://github.com/simh/simh])
* [[OpenSIMH]] ([https://opensimh.org/ https://opensimh.org/])

It is relatively hard for a beginner to decide which way to go. I will not give any specific advice, but some short descriptions:

'''SimH Classic''' is the oldest one, whereof the others were forked later on. It is Bob Supnik work mostly, except for some HP simulators. Development apparently stopped (or at least slowed down) in December 2022. The current version is SIMH V3.12-3.

'''"New" SIMH''' was the first bigger fork and added a lot more simulated computer systems.

'''"OpenSIMH"''' forked from "New" SIMH because of insurmountable different opinions of both maintainers and contributors.

== Usage ==

SIMH can either take in configuration parameters interactively, or you can store them in a file. If the file is the name of the emulator+.ini it will load them automatically (eg vax.exe loads vax.ini automatically). Once running, the CONTROL+E key will break the emulation and bring you back to the SIMH console where you can alter the running state.

Networking is covered in the [[Networking with SIMH]] guide.

[[Category: Emulators]]

== SIMH Media Handling ==

SIMH handles computer storage media in the form of data files called "images" for:

* [[Punched card]]s
* [[Paper tape]]s
* [[DECtape]]s
* [[Magnetic tape]]s
* [[Disk]]s

All of these image files are said to be interchangeable between the three SIMH flavors with one exception: Image files used with "New" SIMH may be unreadable with the other two flavors because of 512 byte of meta data appended to the standard SIMH images.

Sorry, Windows folks, the next two commands are for [[Linux]] only! -
If someone knows how to do the same in [[Windows]], please add it here.

You can visualize the appended metadata under Linux with (example image file trek7.rk7):

$ tail -c 512 trek7.rk7 | hexdump -C
00000000 73 69 6d 68 56 41 58 20 31 31 2f 37 35 30 00 00 |simhVAX 11/750..|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000040 00 00 00 00 52 4b 30 37 00 00 00 00 00 00 00 00 |....RK07........|
00000050 00 00 00 00 00 00 02 00 00 00 d2 1e 00 00 00 02 |................|
00000060 4d 6f 6e 20 41 70 72 20 20 33 20 30 39 3a 31 39 |Mon Apr 3 09:19|
00000070 3a 32 34 20 32 30 32 33 0a 00 00 00 00 02 00 00 |:24 2023........|
00000080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 fa 1e 03 18 |................|
00000200

In the metadata you can see:
* the simulated computer model: <code>simhVAX 11/750</code>
* the disk model: <code>RK07</code>
* the time stamp: <code>Mon Apr 3 09:19:24 2023</code>

The problem can be cured under Linux using (example image file trek7.rk7):
$ truncate -s -512 trek7.rk7
This truncates 512 bytes (the metadata) at the end of the image file.

Keep in mind that the <code>truncate</code> command truncates whatever file you specify, so look first if metadata is present.

'''Another possible pitfall:''' <br>If you leave out the <code>-</code> (minus) before the <code>512</code>, you will end up with a corrupted image of 512 bytes only!

'''Caution:''' <br>
'''Truncating does not work with SIMH disk images in [[VHD]] format!!!'''

[[Category: Emulators]]

SIMH

2026-09-08T07:33:00Z

Vaxorcist: /* SIMH Flavors */ "SimH Classic" now

'''SIMH''' consists of simulators for a lot of different machines, and as such, is a very important emulator for anyone interested in computer history; in particular, that of [[Digital Equipment Corporation|DEC]] systems, as the PDPs and even some [[VAX]] models are well emulated by it.

It can even emulate network interfaces for some of the simulated computers, e.g. the [[PDP-10]], [[PDP-11]] and VAX, so the emulated systems can network directly onto the [[Internet]], if the emulated operating system supports it, like BSD or [[VMS]].

SIMH was primarily written by Bob Supnik of [[Zork]] porting fame, and is now widely contributed to by others as well.

== SIMH Flavors ==

For some time passed there are three flavors of SIMH now:

* [[SimH Classic]] ([http://simh.trailing-edge.com/ http://simh.trailing-edge.com/])
* [["New" SIMH]] ([https://github.com/simh/simh https://github.com/simh/simh])
* [[OpenSIMH]] ([https://opensimh.org/ https://opensimh.org/])

It is relatively hard for a beginner to decide which way to go. I will not give any specific advice, but some short descriptions:

'''"Classic" SIMH''' is the oldest one, whereof the others were forked later on. It is Bob Supnik work mostly, except for some HP simulators. Development apparently stopped (or at least slowed down) in December 2022. The current version is SIMH V3.12-3.

'''"New" SIMH''' was the first bigger fork and added a lot more simulated computer systems.

'''"OpenSIMH"''' forked from "New" SIMH because of insurmountable different opinions of both maintainers and contributors.

== Usage ==

SIMH can either take in configuration parameters interactively, or you can store them in a file. If the file is the name of the emulator+.ini it will load them automatically (eg vax.exe loads vax.ini automatically). Once running, the CONTROL+E key will break the emulation and bring you back to the SIMH console where you can alter the running state.

Networking is covered in the [[Networking with SIMH]] guide.

[[Category: Emulators]]

== SIMH Media Handling ==

SIMH handles computer storage media in the form of data files called "images" for:

* [[Punched card]]s
* [[Paper tape]]s
* [[DECtape]]s
* [[Magnetic tape]]s
* [[Disk]]s

All of these image files are said to be interchangeable between the three SIMH flavors with one exception: Image files used with "New" SIMH may be unreadable with the other two flavors because of 512 byte of meta data appended to the standard SIMH images.

Sorry, Windows folks, the next two commands are for [[Linux]] only! -
If someone knows how to do the same in [[Windows]], please add it here.

You can visualize the appended metadata under Linux with (example image file trek7.rk7):

$ tail -c 512 trek7.rk7 | hexdump -C
00000000 73 69 6d 68 56 41 58 20 31 31 2f 37 35 30 00 00 |simhVAX 11/750..|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000040 00 00 00 00 52 4b 30 37 00 00 00 00 00 00 00 00 |....RK07........|
00000050 00 00 00 00 00 00 02 00 00 00 d2 1e 00 00 00 02 |................|
00000060 4d 6f 6e 20 41 70 72 20 20 33 20 30 39 3a 31 39 |Mon Apr 3 09:19|
00000070 3a 32 34 20 32 30 32 33 0a 00 00 00 00 02 00 00 |:24 2023........|
00000080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 fa 1e 03 18 |................|
00000200

In the metadata you can see:
* the simulated computer model: <code>simhVAX 11/750</code>
* the disk model: <code>RK07</code>
* the time stamp: <code>Mon Apr 3 09:19:24 2023</code>

The problem can be cured under Linux using (example image file trek7.rk7):
$ truncate -s -512 trek7.rk7
This truncates 512 bytes (the metadata) at the end of the image file.

Keep in mind that the <code>truncate</code> command truncates whatever file you specify, so look first if metadata is present.

'''Another possible pitfall:''' <br>If you leave out the <code>-</code> (minus) before the <code>512</code>, you will end up with a corrupted image of 512 bytes only!

'''Caution:''' <br>
'''Truncating does not work with SIMH disk images in [[VHD]] format!!!'''

[[Category: Emulators]]

Talk:SIMH

2026-09-08T07:28:06Z

Vaxorcist: Vaxorcist moved page Talk:SIMH to Talk:SimH Classic: Distinction between SimH variants

SimH Classic

2026-09-08T07:28:06Z

Vaxorcist: Vaxorcist moved page SIMH to SimH Classic: Distinction between SimH variants

'''SIMH''' consists of simulators for about 20 different machines, and as such, is a very important emulator for anyone interested in computer history; in particular, that of [[Digital Equipment Corporation|DEC]] systems, as the PDPs and even the [[VAX]] are well emulated by it.

It can even emulate network interfaces for the [[PDP-10]], [[PDP-11]] and VAX, so the emulated systems can network directly onto the [[Internet]], if the emulated operating system supports it, like BSD or [[VMS]].

SIMH was primarily written by Bob Supnik of [[Zork]] porting fame, and is now widely contributed to by others as well.

The current version is V3.12-2, released on April 25th, 2022. More up to date developments may be found on their GitHub [[source code]] repository.

== Emulated Systems ==

=== Altair 8800 ===
This is the Altair 8800 emulator which can run both AltairDOS and CP/M 2.2

=== Altair Z80 ===

SIMH emulates the [[Altair]] architecture with your choice of either a [[Z80]] or [[Intel 8080]] processor. It can run [[CP/M]].

=== Honeywell H316/H516 ===

Emulates the work horse behind the [[ARPANET]] IMPs. In 2013 the emulator was modified to bring up the original IMP code and connect them together (tunnelled over IP). Demo instructions are available in the latest source. The IMP side of the 1822 is there, but there is not much of a host side yet. I don't see anything in simh that would be able to plug in anyway. An Associated Computer Consultants (ACC) 1822 card for the pdp-11 would be a start.

=== HP2100 ===

I really don't know much about this machine, but I included a way to run the basic1 program I found online. It kind of reminds me of the ROMBASIC back 'in the day'... It's basic with line numbers so I know it's kind of old.. I really don't know much otherwise about this machine.

=== Interdata 8/32 ===

The Interdata 8/32 micro was the first non [[PDP-11]] to run UNIX. SIMH can run both v6 & v7 research editions for the Interdata.

=== Nova ===

SIMH can run [[RDOS]] 7.5 for the [[Nova]].

SIMH also includes [[Data General Eclipse]] support, but there is no available OS.

=== DEC PDP-1 ===

The original [[PDP-1]] is emulated although most of the software is expected to be toggled from the console, or loaded from paper tape. SIMH does not emulate the display needed for [[spacewar]].

=== DEC PDP-6 ===

There is a new [[PDP-6]] emulator by Richard Cornwell.

=== DEC PDP-8 ===

The [[PDP-8 family|PDP-8]] was the first [[minicomputer]]... [[OS/8]] runs under SIMH.

=== DEC PDP-10 ===

The [[PDP-10]] model [[KS10]] processor is emulated and will run all but the latest versions of the [[TOPS-10]] and [[TOPS-20]] operating systems.

Richard Cornwell contributed a new emulator that supports [[KA10]], [[KI10]], [[KL10]] model A and B, and [[KS10]]. It can run most versions of TOPS-10 and TOPS-20, as well as [[Incompatible Timesharing System|ITS]], [[WAITS]], and (soon) [[TENEX]].

=== DEC PDP-11 ===

The PDP-11 is emulated enough to run almost all PDP-11 operating systems including the early Unixes (v1, v4, v5, v6, v7 are known to run).

SIMH can be configured to provide simulations for the following PDP-11 models:
* PDP-11/03
* PDP-11/04
* PDP-11/05
* PDP-11/20
* PDP-11/23
* PDP-11/23+
* PDP-11/24
* PDP-11/34
* PDP-11/40
* PDP-11/44
* PDP-11/45
* PDP-11/53
* PDP-11/60
* PDP-11/70
* PDP-11/73
* PDP-11/73B
* PDP-11/83
* PDP-11/84
* PDP-11/93
* PDP-11/94

=== MicroVAX II ===

The SIMH '''microvax2''' simulator can run the [[MicroVAX II]] with as much as 16 MB of emulated [[RAM]].

Both [[VMS]], [[ULTRIX]], [[NetBSD]], [[OpenBSD]] and original [[BSD]] can run on this emulator.

With the following SIMH commands you can choose between three MicroVAX II models:

* Standard MicroVAX II: '''SET CPU MODEL=MicroVAX'''
* MicroVAX II with one Plane Graphics ([[VCB01 Video Controller|VCB01]]) = [[VAXstation II]]: '''SET CPU MODEL=VAXstation'''
* MicroVAX II with four/eight Plane Graphics ([[VCB02 Video Controller|VCB02]]) = [[VAXstation II/GPX]]: '''SET CPU MODEL=VAXstationGPX'''

=== VAX 11/780 ===

SIMH can also simulate the first model of the VAX, the [[VAX-11/780]], the name of the simulator is '''vax780'''.

This is appropriate for older operating systems like VMS release 1.x (see: [[Installing VMS V1.0 on SIMH]]) and the original [[Unix/32V]], [[3BSD]] and all 4BSD releases, e.g. [[4BSD]].

== Usage ==

SIMH can either take in configuration parameters interactively, or you can store them in a file. If the file is the name of the emulator+.ini it will load them automatically (eg vax.exe loads vax.ini automatically). The CONTROL+E key will break the emulation and bring you back to the SIMH console where you can alter the running state.

Networking is covered in the [[Networking with SIMH]] guide.

== Support ==

There is a mailing list here: https://groups.io/g/simh

There was an earlier mailing list here [http://mailman.trailing-edge.com/pipermail/simh/ http://mailman.trailing-edge.com/pipermail/simh/]. I would recommend searching the old archives, and you'll be amazed how much good information there is in there. The [https://github.com/open-simh/simh public source repository] is also a great source of information.

==See also==

* [[:Category:SIMH Tutorials|SIMH Tutorials]]
* [[SIMH Simple Sound System]]
* [[Mkdisttap.pl]] - make 'tapes'

==External links==

* [http://simh.trailing-edge.com/ Home page]
* [http://sourceforge.net/projects/simh/ SIMH on SourceForge]
* [https://github.com/open-simh/simh Open SIMH on GitHub]
* [https://github.com/simh/simh Mark Pizzolato's fork of SIMH on GitHub]

[[Category: Emulators]]

Installing Ultrix 4.5 on SIMH

2026-09-06T18:32:49Z

Vaxorcist: /* Running the Emulator */ Made "MOP" a link

This WORK-IN-PROGRESS guide will be a simple guide to installing [[ULTRIX]] 4.5 for VAX on [[SIMH]].

==Requirements==
The following is a list of things required for installation
*A recent version of the SIMH emulator
**Make sure the binary you're using includes [[Ethernet]] support
**I'm using a self-compiled version (git revision 0e8c0aea)
*An ISO image of ULTRIX 4.5 for [[VAX]]
**See the "Resources" section for a download link
**It's probably also possible to install it from tape, although I don't know if any installation tapes for ULTRIX 4.5 exist
*Optional stuff (might get added to the guide later):
**Starfish Ultrix Freeware CDs from [http://musall.de/mirrors/ultrix/freeware/ here]

==SimH configuration==
The machine I'm using to run ULTRIX has the following configuration
*[[DEC]] [[MicroVAX 3800/3900|MicroVAX 3800]]
*64mb memory
*[[DELQA]] network card (XQ0)
*Two [[RA90]] disk drives (with 1.2gb each) attached to an [[RQDX3 MFM Disk & Floppy QBUS Controller|RQDX3]] controller (RQ0 and RQ1)
*CD ROM drive attached to the same RQDX3 controller as unit 2 (RQ2)
*[[TK50]] tape attached as unit 0 on the first [[TQK50]] controller (TQ0)
*[[DZV11]] terminal multiplexer with 16 lines, attached to telnet port 1005 (DZ)
*[[LPT]] line printer attached to text file <code>printer_output.txt</code>

Here's my config file (I called it <code>simh.conf</code>)
<pre><nowiki>
;
; SimH 4.0 Configuration file for MicroVAX 3800
;
; Host System : DEC MicroVAX 3800
; Operating System : DEC Ultrix v4.5
; Memory : 64mb
; Network config : XQ: Ethernet, 08:00:2b:04:14:02
; Disks : RQ0: RA90, 1.2gb
; RQ1: RA90, 1.2gb
; CDROMs : RQ2: iso file
; Tape config : TQ0: TK50, 94mb
;

load -r ka655x.bin

; NVRAM
attach NVR nvram.bin

; CPU config
set CPU 64m
set CPU conhalt
set CPU idle=all

; configure console to 7-bit only
set TTO 7b
set TTI 7b

; Disk drives
set RQ0 ra90
attach RQ0 rq0-ra90.dsk
set RQ1 ra90
attach RQ1 rq1-ra90.dsk
set RQ2 CDROM
attach -r RQ2 ultrix-vax-os-v4.5.mode1.ufs.iso
; MD5 sum: 19df0753c27f195e9f1d2f139a3b4629 *ultrix-vax-os-v4.5.mode1.ufs.iso
set RQ3 dis

; Tape
set TQ tk50
;attach tq0 filename-to-tape-file
set TQ1 dis
set TQ2 dis
set TQ3 dis

; serial port, simulated by Telnet to port 1005
set DZ LINES=16
set DZ 8B
attach DZ 1005 NoBuffer

; printer
set LPT enable
attach LPT printer_output.txt

; Disable unused peripherals
set CR dis
set RL dis
set TS dis

; Network interface (08-00-2b is the DEC prefix, the 04-14-02 part is arbitrary)
set XQ MAC=08-00-2b-04-14-02
attach XQ0 eth0

; serial console (launch directly after booting CPU)
set console telnet=1001

; experimental
;set QVSS en

; boot the system
;boot CPU
</nowiki></pre>
Note that I'm using a telnet console (for easier copy/paste on Windows), which means that directly after running this config file (via <code>do simh.conf</code> from Simh) you will need to connect via telnet to localhost:1001 or the boot will abort. If you are on Linux, or just don't want that, remove the <code>set console telnet=1001</code> line.

Also note that you might need to attach XQ0 to a different ethernet device. Use "show ether" in SimH to list all available devices on your system and modify the <code>attach XQ0 eth0</code> line accordingly.

==Running the Emulator==
Either run <code>vax.exe simh.conf</code> from the Windows command line, or just double-click the VAX.EXE executable and type <code>do simh.conf</code>.

On the first launch it might take some time because SimH has to create the disk images (~2.5 gb total). It should look something like this
<pre><nowiki>
MicroVAX 3900 simulator V4.0-0 Beta git commit id: 0e8c0aea
NVR: buffering file in memory
RQ2: unit is read only
Listening on port 1005
WinPcap version 4.1.2 (packet.dll version 4.1.0.2001), based on libpcap version 1.0 branch 1_0_rel0b (20091008)
Eth: opened OS device \Device\NPF_{A41A1651-DD4D-4735-A4E0-88353165C2EC}
Listening on port 1001
sim>
</nowiki></pre>

Type the following to start the emulation (note: you can also uncomment that line from the end of the config file to have the emulation start right away)
sim> boot cpu
Waiting for console Telnet connection

Now would be a good time to connect your telnet session (I use a batch file for this), otherwise the boot process will timeout.

On your console, you should see something like this:
<pre><nowiki>
Connected to the MicroVAX 3900 simulator CON-TEL device

KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>
</nowiki></pre>

This is the VAX's boot prompt. Normally you just type
>>>boot <device>
where <device> is one of the following
*MUA<num>: TK tape device number <num> (1 to 4)
*DUA<num>: RQ disk device number <num> (1 to 4)

You can use <code>show device</code> to see the installed (and detected) devices you can boot from, and <code>show boot</code> to see which device will be the default if you just type <code>boot</code> (or <code>b</code> for short):
<pre><nowiki>
>>>show device
UQSSP Disk Controller 0 (772150)
-DUA0 (RA90)
-DUA1 (RA90)
-DUA2 (RRD40)

UQSSP Tape Controller 0 (774500)
-MUA0 (TK50)

Ethernet Adapter 0 (774440)
-XQA0 (08-00-2B-04-14-02)
>>>show boot
MUA0
</nowiki></pre>

Since we want to boot from CDROM, which is unit 2, we can use
>>>boot DUA2

Note: You can add flags to boot into single user mode, or to boot in interactive mode (so-called ''conversational boot'', where the system prompts you for a kernel file name to load). For details see the Guide to ULTRIX-32 System Startup and Shutdown, linked to in the ''References'' section. To use it, add the <code>/R5:<flags></code> option to the <code>boot</code> command, where flags is 0 (default multi-user), 1 (conversational multi-user), 2 (single-user) or 3 (conversational single-user). For example
>>>boot/r5:3 dua0

Note: You can also boot from ethernet (<code>boot XQA0</code>) but this requires a DEC-specific boot server in your network (the protocol is called ''[[MOP]]'' for ''Maintenance Operations Protocol''), which is beyond the scope of this document. I did get it to work a few years ago though, but it was a bit difficult to set up.

For a list and description of all commands available in the bootloader (hint: there are lots), see the ''KA655 CPU System Maintenance'' guide mentioned in the ''References'' section..

==Bootstrapping ULTRIX==
You will see the following output on the first boot.
<pre>
>>>boot dua2
(BOOT/R5:0 DUA2

2..
-DUA2
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 945424
data = 1290240
bss = 757940
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #2: Wed Oct 18 12:06:55 EDT 1995
real mem = 67043328
avail mem = 61517824
Buffer configuration adjusted to run with small system page table
using 123 buffers containing 1007616 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
WARNING: clock gained 47 days -- CHECK AND RESET THE DATE!

*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice:
</pre>
Now we want to do an ''ADVANCED Installation'', but when we try to, it will take a few seconds until the installation program dumps us to a prompt because it couldn't find a valid device to install from and to:
<pre>
Enter your choice: 2

*** SOFTWARE DISTRIBUTION DEVICE SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of software distribution devices and which installation media you should
load on it:

No valid device is found.
Contact a DIGITAL field service representative.

#
</pre>

The problem seems to be that the hardware SimH emulates is not fully supported by ULTRIX (or is misdetected -- I'm not entirely sure myself). The good thing is that the internet has the correct solution, which is to fix some lines in the installation shell script. The fact that the basic system that is running at this point doesn't have ''vi'', or even ''cat'', makes this a bit harder ;-)

The only option you have is ''ed'', the old UNIX editor. For a quick introduction, see [http://blog.sanctum.geek.nz/actually-using-ed/ here].

To load the file in the editor, use
# '''ed install.1'''
16763

You can see the entire file with
1,$l
but be warned, the output is quite long and it'll take some time to print it all out.

To fix it, use the following commands (the lines in '''bold''' is what you type, everything else is the response from ed)
# '''ed install.1'''
16763
'''173l'''
BTD=`btd`
'''173s/`btd`/ra2/'''
'''173l'''
BTD=ra2
'''193l'''
rz* )
'''193s/rz/ra/'''
'''193l'''
ra* )
'''w'''
16761
'''q'''
#

First, we list line 173, then we change it from <code>BTD=`btd`</code> to <code>BTD=ra2</code>, which happens to be the CDROM device and unit number we're installing from (if you changed that in your config, use the correct name here!)

Then we change line 193 from <code>rz* )</code> to <code>ra* )</code> since we're trying to install on an RA type disk which was apparently not supported in ULTRIX out of the box.

Note: These changes also work for Ultrix 4.3 and 4.4. If you would like to try 4.2, use 164 instead of 173 and 184 instead of 193.

After writing the file with <code>w</code> and quitting ed with <code>q</code>, we're back at the prompt, at which point we can use CTRL+D to retry the installation:

<pre>
# ^D
*** STANDALONE ULTRIX ENVIRONMENT ***

If you select the BASIC Installation option from the list that follows,
the installation software creates file systems on default partitions on
your system disk and loads the mandatory ULTRIX software subsets.

If you require additional installation choices, select the ADVANCED
Installation option.

Select one of the following options:

1) BASIC Installation
2) ADVANCED Installation
3) System management

Enter your choice: 2

*** SYSTEM DISK SELECTION ***

The 'Guide to Installing ULTRIX' explains the following table
of system disk drives. Select one of the devices below to contain the
root file system:

SYSTEM DISK TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk drive
is on line and write-enabled (if applicable to your disk drive), then
confirm your choice.

Use RA90, ra0, for your system disk? (y/n) []: y

The installation procedure now allocates the root file system on
partition 'a' of the system disk, ra0 RA90.

Making the root file system on ra0 RA90.

The installation procedure is now restoring the root file system to
partition 'a' of the system disk, ra0 RA90.

The installation procedure now checks the root file system on partition 'a'
of the system disk, ra0 RA90.
** /dev/rra0a
** Last Mounted on /mnt
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
226 files, 4547 used, 11004 free (20 frags, 1373 blocks, 1.0% fragmentation)

*** BOOTSTRAP COMMAND SEQUENCE ***

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 8007F799
>>>
</pre>
After this, you will be back at the VAX boot prompt (if you used <code>set CPU CONHALT</code> in your config) or at the SimH emulator prompt (if you used <code>set CPU SIMHALT</code>, which is the default). In the latter case you will have to do <code>boot cpu</code> again to get to the VAX boot prompt.

==First boot==
Now we can boot the installed system from harddisk for the first time.

If you want to, now would be a good time to take a backup copy of your disk files (or just create a btrfs snapshot or something if you have the possibility ;-)

Okay, then let's boot from DUA0
<pre>
>>>boot dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 1153664
data = 281088
bss = 1043548
Starting at 0x5219

ULTRIX V4.5 (Rev. 47) System #3: Wed Oct 18 11:49:00 EDT 1995
real mem = 67043328
avail mem = 62008320
Buffer configuration adjusted to run with small system page table
using 121 buffers containing 991232 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
</pre>
Here, it will seem to hang for a loooong time. A few minutes. Don't worry, it will eventually continue to boot. I guess it's probing for other devices which are not present.

You ''might'' be able to speed this up a bit by interrupting SimH (press CTRL+E in the SimH console window) and then using <code>set CPU noidle</code> followed by <code>go</code> to resume emulation.

Eventually, you will have to decide on a hostname. Note that if you want to play around with [[DECnet]] at some point, your hostname should be no longer than 6 characters.
<pre>
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)

*** SYSTEM NAME SPECIFICATION ***

Select the name of your system using alphanumeric characters.
The first character must be a letter. For example, tinker.

Enter your system name: yuki

You selected yuki as the name of your system.
Is this correct? (y/n) [y]: y
</pre>

Next up is the time configuration. Since Ultrix 4.5 is not Y2k compliant (AFAIK), I decided to set the clock back a whopping 20 years. Note that the timezone and daylight saving settings are for my location (Germany) and will probably vary for you.

<pre>
*** DATE AND TIME SPECIFICATION ***

The current date and time should be specified using the following
format:

yymmddhhmm

Use two digits for year (yy), month (mm), day (dd), hour (hh), and
minute (mm). Enter the time in 24-hour format. For example, 02:54
p.m. on Feb 2, 1993 would be entered as:

9302021454

Enter the date and time: 9512052336

*** TIME ZONE SELECTION ***

Select the time zone for your area, using the options listed in the
table below. You can also enter the number of hours (-12 to 12) in
time east of Greenwich.

Selection Time Zone
---------------------------------
e Eastern
c Central
m Mountain
p Pacific
g Greenwich
---------------------------------

Enter your choice: 1

Does your area alternate between Daylight Savings and Standard
time? (y/n) [y]: y

Select your geographic area for Daylight Savings Time, using the
options in the table below.

Selection Geographic Area
--------------------------------
u USA
a Australia
e Eastern Europe
c Central Europe
w Western Europe
--------------------------------

Enter your choice [u]: c

The current date and time is Tue Dec 5 23:36:46 EST 1995
</pre>

Next up is the root password. Note that Ultrix will not echo anything here, I added the asterisks just for this guide :)

<pre>
*** SPECIFY THE SUPERUSER PASSWORD ***
The Guide to Installing ULTRIX instructs you on how to enter
the superuser password.
Changing password for root
Enter new password: ******
Verify: ******
</pre>

Next up is the filesystem layout, which is a bit more involved than what you know from more modern systems like MS DOS ;-)

In ULTRIX, partitions are defined for each disk type in a file called <code>/etc/disktab</code>. Note that the partitions overlap, so you shouldn't use them all at the same time. The setup script actually takes care of that for you, but if you later create a new filesystem on the wrong partition you ''WILL'' lose data!

Normally, partition '''c''' is the whole disk, which is useful for add-on disk drives for example. Partitions '''a''' and '''b''' are always available and are traditionally used for the system and the swap-space respectively. The swap partition is also used for crashdumps if no separate crash-dump partition is created. The rest of the disk can be used either as a single partition (which is usually '''g''') or as 3 individual partitions ('''d''' to '''f'''). If the disk is larger than 1 gigabyte, you will get another partition, '''h''', after the g partition, probably because the filesystem cannot cope with partitions >1gig

In our case, we will have the following partitions on the first disk (RA0):
*Partition '''a''' of 32 mb for /root
*Partition '''b''' of 64 mb for swap+crashdump
*Partition '''c''' of 1.2 gig (whole-disk, not used on our setup)
*Partition '''d''' and '''e''' of 200 mb each (not used)
*Partition '''f''' of 400 mb (not used)
*Partition '''g''' of 800 mb (overlaps with d, e and f; will become /usr)
*Partition '''h''' of 256 mb (will become /usr/var)
This way we still have the whole second disk available for later use.

So here it goes:
<pre>
*** FILE SYSTEM DEFAULT OPTION ***

The following table shows the default file system layout on RA90, ra0:

partition bottom top size overlap default
a 0 32767 32768 c root
b 32768 159839 127072 c swap, dump
d 159840 580036 420197 c,g /usr

If you choose the defaults, the var area will be allocated to /usr/var.

Do you want to choose the default file system layout? (y/n): n
</pre>

No, we do not want to use the defaults...

First, we select disk 1, partition '''g''', for the /usr file system:
<pre>
*** /usr FILE SYSTEM ALLOCATION ***

You can allocate the /usr file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

/usr FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for /usr file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the /usr file system:

partition size (Kbytes) overlap
------------------------------------------------
d --- 210098 c,g
e --- 210098 c,g
f --- 420196 c,g
g --- 840393 c,d,e,f
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the /usr file system [d]: g

Making the new file system for /usr on /dev/rra0g RA90
</pre>

Next, we select disk 1, partition '''b''' for swap (only 1 swap partition) and for crashdumps:

<pre>
*** ALLOCATE THE SWAP1 SPACE ***

You can allocate the swap1 space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

SWAP1 SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for swap1 space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the swap1 space:

partition size (Kbytes) overlap
------------------------------------------------
b --- 63536 c
h --- 267763 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the swap1 space [b]: b

*** ALLOCATE THE SWAP2 SPACE ***

Do you want to allocate a second swap space? (y/n) [n]: n

*** ALLOCATE THE CRASH DUMP SPACE ***

You can allocate the crash dump space to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

CRASH DUMP SPACE ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for crash dump space? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the crash dump space:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
b --- 63536 c
------------------------------------------------

Type the letter of the partition on which you want
to allocate the crash dump space [b]: b
</pre>

Finally we select partiton '''h''' for the /var file system. This might not be large enough later on but then we can always migrate the data away if we need to...

<pre>
*** ALLOCATE THE var FILE SYSTEM ***

You can allocate the var file system to one of the disks listed in the
table below. See the Guide to Installing ULTRIX for an explanation of
this table:

var FILE SYSTEM ALLOCATION TABLE

Selection Device ULTRIX Device Controller Controller
Name Name Number Name Number
----------------------------------------------------------------------
1 RA90 ra0 0 RQDX3 0
2 RA90 ra1 1 RQDX3 0
----------------------------------------------------------------------

Enter your choice: 1

You selected RA90, device number 0. Make sure this disk is
on line and write-enabled (if applicable to this drive) and then
confirm your choice.

Use RA90, ra0 for var file system? (y/n) []: y

The disk ra0 you selected from the previous table has the following
partitions available, on which you can allocate the var file system:

partition size (Kbytes) overlap
------------------------------------------------
h --- 267763 c
g --- 840393 c,d,e,f
------------------------------------------------

Type the letter of the partition on which you want
to allocate the var file system [no default]: h

Making the new file system for var on /dev/rra0h RA90
</pre>

==Installing the distribution files==

Next up we have to decide what ''packages'' we want to install (yes, ULTRIX already had its own package format and corresponding installer called ''setld''. It is very basic, probably most similar to ''pkg_add'' on NetBSD). We simply install everything, since we have enough space :)

<pre>
This distribution media includes subsets for ULTRIX Worksystem
Software (UWS). A UWS license (on a workstation) or a UWS Server
License (on a timesharing machine or server) is required to install
these subsets.

Do you want to install ULTRIX Worksystem Software? y/n []: y

*** SUPPORTED SOFTWARE INSTALLATION ***

*** Select the DECwindows User Interface ***

1) DECwindows for OSF/Motif
2) X11/DECwindows (XUI)

Enter your choice [1]: 2

*** Enter Subset Selections ***

The following subsets are mandatory and will be installed automatically:
* Base System * Kernel Config Files
* TCP/IP Networking Utilities * Network File System Utilities
* Extended (Berkeley) Mailer * X11/DECwindows Servers
* X11/DECwindows User Environment * X11/DECwindows 75dpi Fonts

The subsets listed below are optional:
1) Printer Support Environment 2) RAND Mail Handler
3) Sys. Config. Mgmt. Program (SCAMP) 4) Communications Utilities
5) Unix-to-Unix Copy Facility 6) Maintenance Operations Protocol
7) Accounting Software 8) Kerberos Network Authentication
9) Enhanced Security Features 10) Prestoserve Utilities
11) System Exerciser Package 12) Bisynchronous Communications
13) Doc. Preparation for Ref. Pages 14) Doc. Preparation Extensions
15) Adobe Font Metric Files 16) Software Development Utilities
17) Source Code Control System 18) Internationalization Runtime Env.
19) Internationalization Dev. Env. 20) CDA Base System
21) CDA Software Dev Libraries 22) RPC Runtime Environment
23) RPC Development Environment 24) Pascal Development Package
25) VAX C/ULTRIX 26) Ref. Pages for Sys. Admin. & Users
27) Reference Pages for Programers 28) Programming Examples
29) Ultrix SPDS 30) X11/DECwindows 100dpi Fonts
31) VS35XX X11/DECwindows Fonts 32) Additional DECwindows Applications
33) DECwindows Mail Application 34) Worksystem Development Environment
35) X11/DECwindows System Management T 36) UWS Runtime Reference Pages
37) UWS Development Reference Pages

38) All mandatory and all optional subsets
39) Mandatory subsets only
40) Exit without installing subsets

Enter your choice(s): 38
Working....Wed Dec 6 00:14:12 EST 1995

You are installing the following subsets:
Base System Kernel Config Files
TCP/IP Networking Utilities Network File System Utilities
Extended (Berkeley) Mailer X11/DECwindows Servers
X11/DECwindows User Environment X11/DECwindows 75dpi Fonts
Printer Support Environment RAND Mail Handler
Sys. Config. Mgmt. Program (SCAMP) Communications Utilities
Unix-to-Unix Copy Facility Maintenance Operations Protocol
Accounting Software Kerberos Network Authentication
Enhanced Security Features Prestoserve Utilities
System Exerciser Package Bisynchronous Communications
Doc. Preparation for Ref. Pages Doc. Preparation Extensions
Adobe Font Metric Files Software Development Utilities
Source Code Control System Internationalization Runtime Env.
Internationalization Dev. Env. CDA Base System
CDA Software Dev Libraries RPC Runtime Environment
RPC Development Environment Pascal Development Package
VAX C/ULTRIX Ref. Pages for Sys. Admin. & Users
Reference Pages for Programers Programming Examples
Ultrix SPDS X11/DECwindows 100dpi Fonts
VS35XX X11/DECwindows Fonts Additional DECwindows Applications
DECwindows Mail Application Worksystem Development Environment
X11/DECwindows System Management To UWS Runtime Reference Pages
UWS Development Reference Pages

Is this correct? (y/n): y
</pre>

The installation will take a while (around 15-30 minutes for me), so feel free to let it run in the background for a while now. The installer will periodically print its status so you can see that it's still running...

<pre>
Base System (ULTBASE450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:14:43 EST 1995
Verifying

Kernel Config Files (ULTBIN450)
Copying from /mnt/VAX/BASE (disk)
Working....Wed Dec 6 00:15:28 EST 1995
Verifying

...
</pre>

At some point you will have to confirm installing the generic kernel and the X11 subsystem:

<pre>
...
UWS Runtime Reference Pages (UWSMAN450)
Copying from /mnt/VAX/BASE (disk)
Verifying

UWS Development Reference Pages (UWSMANPGMR450)
Copying from /mnt/VAX/BASE (disk)
Verifying

The installation software has successfully installed the software
subsets.
Installing Upgrade subsets
The following subsets will be installed:
* X11/DECwindows Servers Upgrade * Generic Kernel
Do you wish to continue? (y/n): y

X11/DECwindows Servers Upgrade (UWSSER451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

Generic Kernel (ULTGENVMUNIX451)
Copying from /mnt/VAX/BASE_UPGRADE (disk)
Verifying

The installation procedure has successfully installed the Upgrade
subsets
</pre>

That's it for the base installation, now we configure our kernel...

==Kernel configuration==
We have to select what features will be in the kernel. For anyone who has ever done a "make menuconfig" on Linux, this is ''slightly'' easier here ;-)
<pre>
*** CONFIGURATION FILE KERNEL OPTION SELECTION ***

Selection Kernel Option
---------------------------------------------------------------
1 Local Area Transport (LAT)
2 Bisynchronous Communication protocol (VAX only)
3 Computer Interconnect (CI) network
4 Diagnostic/Utilities Protocol (DUP)
5 ISO9660 File System Support (CDFS)
6 Ethernet Packet Filter
7 Enhanced Security Features
8 All of the above
9 None of the above
----------------------------------------------------------------

Enter the selection number for each kernel option you want.
For example, 1 3 :
</pre>

In our case, we don't need 2 (it is for 2780/3780 remote terminals), 3 (SimH doesn't emulate any cluster hardware) or 6 (it might cause problems with DECwindows/Motif). Everything else (<code>1 4 5 7</code>) is probably safe. This lets us play around with LAT (maybe connect an emulated Cisco router with LAT routing to it?) and DUP.

<pre>
Enter the selection number for each kernel option you want.
For example, 1 3 : 1 4 5 7

You specified the following kernel options:

Local Area Transport (LAT)
Diagnostic/Utilities Protocol (DUP)
ISO9660 File System Support (CDFS)
Enhanced Security Features

Is this correct? (y/n) [n]: y

*** SYSTEM CONFIGURATION PROCEDURE ***
The installation software found these devices in the floating
address space:

dz0 on uba0 at 0160100
dz1 on uba0 at 0160110
dz2 on uba0 at 0160120
dz3 on uba0 at 0160130

Configuration file complete.

Do you want to edit the configuration file? (y/n) [n]: n

*** PERFORMING SYSTEM CONFIGURATION ***

working ..... Wed Dec 6 02:29:10 EST 1995

*** DEVICE SPECIAL FILE CREATION ***
working ..... Wed Dec 6 02:29:53 EST 1995

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

Enter the following boot sequence at the console mode prompt
after the installation software halts the processor:

>>> b dua0

syncing disks... done

?06 HLT INST
PC = 800985B5
</pre>

Now you might want to take another backup of your disk images, since the ULTRIX installation is now basically complete.

==Adding the unsupported sets==
Now there are some more pieces of software in the CDROM, in a directory called ''unsupported''. We want to install these as well. First, let's boot our system again

<pre>
>>>b dua0
(BOOT/R5:0 DUA0

2..
-DUA0
1..0..

Ultrixboot - V4.5 Sun Sep 17 13:03:13 EDT 1995

Loading (a)vmunix ...

Sizes:
text = 747376
data = 125952
bss = 918192
Starting at 0x2c19

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
real mem = 67043328
avail mem = 56455168
using 1638 buffers containing 6712320 bytes of memory
KA655 processor with an FPU
CPU microcode rev = 6, processor firmware rev = 83
Q22 bus
uda0 at uba0
uq0 at uda0 csr 172150 vec 774, ipl 17
klesiu0 at uba0
uq16 at klesiu0 csr 174500 vec 770, ipl 17
qe0 at uba0 csr 174440 vec 764, ipl 17
qe0: DEC DELQA Ethernet Interface DEQNA-lock Mode, hardware address 08:00:2b:04:14:02
lp0 at uba0 csr 177514 vec 200, ipl 17
dz0 at uba0 csr 160100 vec 300, ipl 17
dz1 at uba0 csr 160110 vec 310, ipl 17
dz2 at uba0 csr 160120 vec 320, ipl 17
dz3 at uba0 csr 160130 vec 330, ipl 17
ra1 at uq0 slave 1 (RA90)
ra2 at uq0 slave 2 (RRD40)
ra0 at uq0 slave 0 (RA90)
tms0 at uq16 slave 0 (TK50)
Wed Dec 6 11:25:29 MET 1995
Automatic reboot in progress...
/dev/ra0a: 644 files, 6161 used, 9390 free (166 frags, 1153 blocks, 5.0% fragmentation)
/dev/rra0g: umounted cleanly
/dev/rra0h: umounted cleanly
Warning Creating new license database
Warning creating new history file
check quotas: done.
savecore: checking for dump...dump does not exist
local daemons: syslog sendmail.
Removing remnant Opser files
preserving editor files
clearing /tmp
standard daemons: update cron accounting network snmpd printer.
start errlog daemon - elcsd
Wed Dec 6 11:25:48 MET 1995

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:

ULTRIX V4.5 (Rev. 47) System #1: Wed Dec 6 02:29:50 EST 1995
UWS V4.5 (Rev. 6)

Digital Equipment Corporation
Nashua, New Hampshire

*** SOFTWARE INSTALLATION PROCEDURE COMPLETE ***

The following files were created during the installation procedure:

/vmunix - customized kernel
/genvmunix - generic kernel
/usr/adm/install.log - installation log file
/usr/adm/install.FS.log - file systems log file
/usr/adm/install.DEV.log - special device log file

#
</pre>

now, we mount the CDROM and use <code>setld</code> to install the unsupported packages. For simplicity's sake, we just (again) install everything.

<pre>
# mount -r /dev/ra2c /mnt
# cd /mnt/VAX/UNSUPPORTED
# ls
DXVUNDEMO450 ULXDOC450 ULXINGRES450 ULXRCS450 ULXUNMAN450
ULXAPL450 ULXEDIT450 ULXLEARN450 ULXSHELLS450 ULXUNMIT450
ULXBASE450 ULXF77450 ULXLISP450 ULXSPMS450 ULXVARIAN450
ULXBIB450 ULXGAMES450 ULXMAN450 ULXTERM450 instctrl
ULXCOURIER450 ULXHYPER450 ULXMOD2450 ULXTOOLS450
ULXCPM450 ULXICON450 ULXNEWS450 ULXUNEXAMP450
ULXDCMT450 ULXINET450 ULXNOTES450 ULXUNFONTS450
# setld -l .

*** Enter Subset Selections ***

The subsets listed below are optional:
1) Base Extension 2) GNU Emacs
3) TCP/IP Networking Util Extension 4) Additional Terminal Drivers
5) Document Preparation Software 6) Games and Diversions
7) Supplementary Documentation 8) Bibliographic Utilities
9) Remote Procedure Call Compiler 10) Aux. Command Line Interpreters
11) USENET News Interface Software 12) Notesfiles Package
13) Revision Control System 14) Misc. User-Contributed Utilities
15) Computer Aided System Tutor 16) Franz Lisp Development Package
17) Modula-2 Development Package 18) Raster Plotter Package
19) APL Development Package 20) CP/M 8in Diskette Utility
21) Hyperchannel Utilities 22) ICON (Language) Development Packag
23) University Ingres QUEL DBMS 24) Software Project Management System
25) Unsupported Fortran Utilities 26) Unsupported On-Line Documentation
27) Unsupported X11 Components 28) Unsupported DECwindows Examples
29) Unsupported MIT Fonts 30) Unsupported X11 Reference Pages
31) Unsupported OSF/Motif Demos

32) All mandatory and all optional subsets
33) Mandatory subsets only
34) Exit without installing subsets

Enter your choice(s): 32
Working....Wed Dec 6 11:29:48 MET 1995
Wed Dec 6 11:30:00 MET 1995

You are installing the following subsets:
Base Extension GNU Emacs
TCP/IP Networking Util Extension Additional Terminal Drivers
Document Preparation Software Games and Diversions
Supplementary Documentation Bibliographic Utilities
Remote Procedure Call Compiler Aux. Command Line Interpreters
USENET News Interface Software Notesfiles Package
Revision Control System Misc. User-Contributed Utilities
Computer Aided System Tutor Franz Lisp Development Package
Modula-2 Development Package Raster Plotter Package
APL Development Package CP/M 8in Diskette Utility
Hyperchannel Utilities ICON (Language) Development Package
University Ingres QUEL DBMS Software Project Management System
Unsupported Fortran Utilities Unsupported On-Line Documentation
Unsupported X11 Components Unsupported DECwindows Examples
Unsupported MIT Fonts Unsupported X11 Reference Pages
Unsupported OSF/Motif Demos

Is this correct? (y/n): y

Base Extension (ULXBASE450)
Copying from . (disk)
Verifying

GNU Emacs (ULXEDIT450)
Copying from . (disk)
Verifying

TCP/IP Networking Util Extension (ULXINET450)
Copying from . (disk)
Verifying
...
</pre>

Note that you could also quickly install only a single package by using for example
# setld -l . ULXINET450

After a few minutes, installation will be completed and we should unmount the CDROM
# cd /
# umount /mnt

==Network configuration==
To configure the network, you have to use a static IPv4 address and put that into the beginning of /etc/rc.local. Note that there is no <code>ifconfig -a</code> in ULTRIX, you have to use <code>netstat -i</code>

<pre>
# netstat -i
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
qe0* 1500 none none 0 0 0 0 0
lo0 1536 loop localhost 1 0 1 0 0
# ifconfig qe0 192.168.1.44 netmask 255.255.255.0 up
# route add default 192.168.1.1 1
add net default: gateway 192.168.1.1
# ping 192.168.1.1
192.168.1.1 is alive
</pre>
Note that it might actually take a while until packets are getting through. I don't know why but in my case it helped to ping ULTRIX from the outside first, e.g. from Windows, and then re-try the ping from the VM. Then it worked. I'm guessing this is some SimH/Windows issue with PCAP or something.

Then put these 2 commands at the start of <code>/etc/rc.local</code> (you'll see where). Note that you can use <code>vi</code> now!
<pre>
# @(#)rc.local 9.4 (ULTRIX) 9/21/95
/bin/hostname yuki
#/etc/ifconfig HDWR `/bin/hostname` broadcast NETNUM.0 netmask 255.0
/etc/ifconfig qe0 192.168.1.44 netmask 255.255.255.0
route add default 192.168.1.1 1
/etc/ifconfig lo0 localhost
#/etc/bscconfig dup0 bsc 1
#/etc/bscconfig dpv0 bsc 1
...
</pre>

Note that DNS lookups normally don't work out of the box. Create a basic <code>/etc/resolv.conf</code> file with the following content (or whatever is correct in your environment)
domain lan.local
nameserver 192.168.1.1

However, if you then try to do an nslookup query, you will get an error message
# nslookup www.google.com
*** Can't find server name for address 192.168.1.1: Not implemented
*** Default servers are not available
The problem is that ULTRIX sends so-called ''inverse queries'' (not to be confused with the well-known ''reverse lookups'', which are actually just regular forward lookups to a specific TLD) to map IP addresses to hostnames. Most DNS servers don't support these inverse queries anymore. Apparently, BIND8 still included an option "fake-iquery" which might be used to support these queries. Versions before BIND8 (4.x) supported IQUERY natively. I have yet to test both variants to see which (if any) of them work.

==Shutting down cleanly==
As you'd expect, you can use <code>shutdown</code> to shut the system down
<pre>
# shutdown -h now
Shutdown at 11:15 (in 0 minutes) [pid 1500]
#
System shutdown time has arrived
syncing disks... done

?06 HLT INST
PC = 80094CDD
>>>
</pre>

==Enabling outside access==
The SimH config above includes a 16-line serial multiplexer. If you connect via TELNET to port 1005, you are given the first free serial line of the emulated DZ device. However, serial login is disabled by default, so it has to be enabled first. That's what the <code>/etc/ttys</code> file is for. Edit the file and change the ''off'' to ''on'' in the lines for tty00 to tty07, as shown below
<pre>
# @(#)ttys 9.1 (ULTRIX) 4/26/94
#
#
#
# name getty type status comments
#
console "/etc/getty std.9600" vt100 on secure # console terminal
tty00 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty01 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty02 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty03 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty04 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty05 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty06 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
tty07 "/etc/getty std.9600" vt100 on nomodem # direct connect tty
ttyd0 "/etc/getty std.9600" vt100 off shared secure # modem line
</pre>

If you want to be able to login as root on these terminals, you can also add the <code>secure</code> flag as well. Also note that while it seems tempting to increase the line speed to 19200 or even higher, from my experience that will cause massive lags and emulation hangs in SimH, so do that on your own risk.

After editing the file and saving it, you have to reload init:
# kill -HUP 1

Now try logging in to port 1005 via telnet, and you should be greeted with this:
<pre>
Connected to the MicroVAX 3900 simulator DZ device, line 0

ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:
Requires secure terminal
</pre>

Note that SimH will print out the serial line to which you are connected, in this case line 0 which is /dev/tty00.

Also, if your inetd is running (which it should be, if you followed this guide), you will also already be able to login remotely using telnet.
<pre>
ULTRIX V4.5 (Rev. 47) (yuki)

login: root
Password:
Requires secure terminal
</pre>
To enable root access for all telnet sessions, you will have to edit the /etc/ttys file and change every line that starts with "ttyp" to include the secure flag:
ttyp0 none network
will become
ttyp0 none network secure
and so on...

==Resources==
Some of the resources I used for creating this guide:
*ULTRIX 4.5 installation ISO [http://musall.de/mirrors/ultrix/ultrix_os/vax/]
*ULTRIX-32 startup and shutdown guide [http://bitsavers.trailing-edge.com/pdf/dec/vax/ultrix-32/3.0/AA-ME91A-TE_ULTRIX-32_Guide_to_System_Shutdown_and_Startup.pdf]
*CERN guide to installing ULTRIX [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/wwwpdp.web.cern.ch/wwwpdp/as/file/doc/ultrix/ultrix.pdf]
*My old guide for installing ULTRIX [https://docs.google.com/document/d/1ULRhzE0R1twarB5hfJm85yqOdTeoFCGgyPr5AxYEIbE]
*DEC KA655 CPU System Maintenance [http://bitsavers.trailing-edge.com/pdf/dec/vax/655/EK-306A-MG-001_655Mnt_Mar89.pdf]
*Some notes and links to more ULTRIX information [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/docs.html]
*Ultrix Guide to Disk Maintenance [http://www.carelife.com/manuals/Ultrix_Guide_Disk_Maint.PDF]
*Some random notes about ULTRIX 4.0 (some also apply to 4.5) [http://apfelboymchen.net/gnu/UNIX/vax-ultrix.html]

[[Category:SIMH Tutorials]]
[[Category: ULTRIX]]

Infoserver series

2026-09-06T18:29:00Z

Vaxorcist: /* Host-Based InfoServer Alternative */ Made "MOP" a link

The '''InfoServer''' series of [[VAX]] computers has four members:

* Infoserver 100
* Infoserver 150
* Infoserver 150VXT
* Infoserver 1000

== Overview ==

An '''InfoServer''' is an [[Ethernet]]-based, high-performance, virtual disk [[server]]. It can serve physical disk media and sets of logical disk blocks to the network. Host systems running the appropriate client software can connect to virtual disks served by the InfoServer and use them as though they were locally attached devices.

The InfoServer is a virtual disk server. Unlike a file server, the InfoServer does not impose a file system on the virtual disks that it serves. This means the InfoServer can serve a disk with any type of on-disk file structure. The host client system interprets the on-disk structure itself, allowing each host system to use its own native file system. Multiple on-disk structures can be served and accessed on a single InfoServer at the same time.

An Infoserver is comparable to what today is a [[SAN]] server.

== Comparison of InfoServer Models ==

{| class="wikitable" style="margin:auto"
|+ Comparison of InfoServer Models
|-
! Model !! Boot Device !! CPU !! RAM !! SCSI Ports
|-
| InfoServer 100 || RZ23 || KA41 || 4MB (fix) || 2
|-
| InfoServer 150 || RZ23L || KA41 || 4MB (fix) || 2
|-
| InfoServer 150VXT || RZ24 || KA41 || 4MB (fix) || 2
|-
| InfoServer 1000 || Flash || KA? || 4MB (8MB optional) || 1
|}

There's a rumor that you can convert a [[MicroVAX 3100 series|MicroVAX 3100]] (or even a [[VAXstation 3100 series|VAXstation 3100]]) into an InfoServer by replacing the system [[read-only memory|ROMs]] with those of an InfoServer. You need two 27C1024 [[integrated circuit|ICs]], the ROM images, and a ROM programmer device. I can supply the ROM images for the InfoServer 150.

== Host-Based InfoServer Alternative ==

Beginning with [[OpenVMS]] Alpha V8.3 and OpenVMS I64 V8.2-1, OpenVMS itself contains host-based InfoServer support; the ability for OpenVMS itself to provide InfoServer Local Area Disk (LAD) and [[MOP]] services. The OpenVMS host-based InfoServer software also removes the 2 GB limit from previous InfoServer devices; hardware InfoServer devices are limited to serving disks of 2 GB or less.

{{semi-stub}}

== See also ==

* [[Installing and Using the SIMH InfoServer150VXT]]

== External links ==

* [http://www.vaxhaven.com/images/9/94/EK-DIS1K-UG-001.pdf InfoServer 100 System Operations Guide] (EK-DIS1K-UG-001)
* [http://www.bitsavers.org/pdf/dec/ethernet/infoserver/AA-PJXJC-TE_InfoServer_System_Operations_Guide_Oct94.pdf InfoServer System Operations Guide] (AA-PJXJC-TE)
* [http://www.bitsavers.org/pdf/dec/ethernet/infoserver/EK-INFLC-OM_InfoServer_1000_Installtion_and_Owners_Guide_Mar94.pdf InfoServer 1000 Installation and Owners Guide] (EK-INFLC-OM.B01)
* [http://www.vaxhaven.com/images/5/5f/EK-A0372-MG.B01.pdf MicroVAX 3100, VAXserver 3100, InfoServer 100 and InfoServer 150-150 VXT Maintenance Guide] (EK-A0372-MG.B01)
* [http://www.vaxhaven.com/images/b/b5/EK-INFSV-OM-001.pdf InfoServer 150 Installation and Owner's Guide] (EK-INFSV-OM-001)
* [http://www.bitsavers.org/pdf/dec/brochures/DEC-InfoServer1000-NetworkStorageServer.pdf InfoServer 1000 - Network SCSI Storage Server] (EC-F2305-29)

{{Nav VAX}}

[[Category: VAX Families]]
[[Category: VAX Minicomputers]]

Netbooting a VAXstation

2026-09-06T18:28:20Z

Vaxorcist: /* Requirements */ Made "MOP" a link

This page describes my struggles with trying to netboot a DEC VAXstation 4000/60 for installing NetBSD. I originally wrote this document in 2005, and it did work just fine back then. However, it might be difficult to get the required software nowadays, or changes in the Linux kernel could have an impact on the whole process. This is thus provided AS-IS.

Note that this might also work with [[SIMH]] but it is not tested.

==Requirements==
* Network connectivity for your VAX (normally this means you either need a transceiver for the AUI port or a hub/switch with a 10Base2 connector)
* A Linux machine for the boot-server parts (I used a physical machine with SuSE 9.3)
** This Linux server needs a network card in promiscuous mode (for a VM you might need to do a few config changes, e.g. on ESX)
** It also needs a [[MOP]] server, which is called ''mopd'' for Linux (it is a DEC specific boot protocol)
** For netbooting NetBSD (as was the original goal) you will also need a DHCP/BOOTP server, which is probably not required if you try to netboot an original DEC operating system like VMS or ULTRIX
** Also you need an NFS server (for the install packages and root filesystem) and the kernel from the NetBSD ftp server

Note that ''mopd'' does not work across routers so you need to have a flat network.

==Linux server==
First, your Linux box needs a network card in promiscuous mode. Use
lavie:/# ifconfig eth0 allmulti
to enable it. It should then look something like this
lavie:/# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:02:B3:98:9F:A1
inet addr:192.168.0.42 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: 2002:549c:e025:6:202:b3ff:fe98:9fa1/64 Scope:Global
inet6 addr: fec0::6:202:b3ff:fe98:9fa1/64 Scope:Site
inet6 addr: fe80::202:b3ff:fe98:9fa1/64 Scope:Link
UP BROADCAST RUNNING '''ALLMULTI''' MULTICAST MTU:1500 Metric:1
RX packets:870128 errors:0 dropped:0 overruns:0 frame:0
TX packets:189222 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1184340903 (1129.4 Mb) TX bytes:54007715 (51.5 Mb)
Base address:0x9000 Memory:fa040000-fa060000

===mopd===
Then you need the ''mopd'' MOP server. You can find it via google, for example [https://github.com/qu1j0t3/mopd here] is a GitHub repo which claims to be the latest release (2.5.3/2.5.4). If you use NetBSD as server, it supposedly ships with ''mopd'' on all supported platforms as noted [https://www.netbsd.org/docs/network/netboot/mop.html here]. Back in 2005 I found a prebuilt package on rpmfind.net, but it no longer exists.

You can run ''mopd'' as follows:
lavie:/ # mopd -d eth0
mopd: not running as daemon, -d given.
Just keep it running in the foreground. Of course substitute eth0 with your network interface where the VAXstation can be reached. Your syslog should now contain something like this:
Dec 25 02:32:11 lavie mopd[7854]: mopd 2.5.3 started.
Dec 25 02:32:11 lavie mopd[7854]: Initialized eth0
''mopd'' looks into <code>/tftpboot/mop/</code> by default, so you should make sure that this directory exists. We will populate it later.

===DHCP/BOOTP===
The third puzzle piece is the DHCP/BOOTP server where the NetBSD bootloader gets its configuration from. You should make sure to use a DHCP/BOOTP server which implements the BOOTP/TFTP option 17 (root path) correctly, in my case the CMU BOOTP (version bootp-DD2-4.3) did not do this correctly which made me use isc-dhcpd 3.0.2, which worked just fine. Remember this was 2005 so if you try a more recent version of either, your results may be totally different.

To configure it, create an /etc/dhcpd.conf with the following content:
subnet 192.168.0.0 netmask 255.255.255.0 {
}

host vs4k60 {
hardware ethernet 08:00:2b:xx:yy:zz;
fixed-address 192.168.0.67;
option domain-name-servers 192.168.0.1;
option domain-name "mydomain.com";
option root-path "/export/vax/root";
filename "netbsd";
}

This first tells DHCPD which subnet it's working on, and then it contains an entry which maps the VAXstation to a fixed IP address from that subnet. Important here are 2 things: First, of course replace the <code>xx:yy:zz</code> part with the MAC address of your VAXstation (which you can find out via <code>SHOW ETHER</code> from the PROM). Second, the root-path option specifies where the root filesystem will be exported. NetBSD will try to mount this when it boots (NetBSD has no initrd concept on VAX, and with 32mb RAM or so, it would be difficult to pull off anyway ;-)

The filename (in this case "netbsd") is unimportant.

===NFS server===
Create the directory <code>/export/vax/root</code> and export it via NFS to the IP address (or hostname) of your VAX
lavie:/# cat /etc/exports
/export vs4k60(rw,async)
If you use a hostname, like me, you have to create the corresponding entry in the <code>/etc/hosts</code> file of course.

==NetBSD installation files==

This guide was written for NetBSD 3.0 but it should (in theory) work the same for newer releases as well. First you will need to get this file: http://ftp.netbsd.org/pub/NetBSD-archive/NetBSD-1.5/vax/installation/netboot/boot.mop
Yes, it is from NetBSD 1.5, and yes, we will be installing a newer version. However, all newer versions don't include the ''boot.mop'' file anymore, just a file called ''boot'', which is not the same and which I couldn't get to work...

Copy this file into the following directory under exactly this name (case-sensitive):
/tftpboot/mop/MOPBOOT.SYS

Then, create a symbolic link to this file and name it like <code>aabbccddeeff.SYS</code>, where <code>aa:bb:cc:dd:ee:ff</code> is the MAC address of your VAXstation, with all letters lower-case except the .SYS at the end, which must be upper case. On my system it looks like this:
lavie:/# ls /tftpboot/mop/ -ls
total 72
0 drwxr-xr-x 2 root root 176 Dec 25 00:01 .
0 drwxr-xr-x 3 root root 136 Dec 25 01:28 ..
0 lrwxrwxrwx 1 root root 11 Dec 24 20:04 08002b30cc49.SYS -> MOPBOOT.SYS
72 -rw-r--r-- 1 root root 71168 Dec 25 00:01 MOPBOOT.SYS

Next you need the NetBSD install kernel image, which (for NetBSD 7.0) is available [http://ftp.netbsd.org/pub/NetBSD/NetBSD-7.0/vax/installation/netboot/install.ram.gz here]. It is usually called ''install.ram.gz''. Uncompress it and place it under
/export/vax/root/netbsd.vax

It should look something like this:
lavie:/# ls /export/vax/root/ -ls
total 7170
0 drwxrwxrwx 2 root root 184 Dec 25 02:43 .
0 drwxrwxrwx 3 root root 72 Dec 25 00:34 ..
2478 -rw-r--r-- 1 root root 2534976 Dec 25 01:42 netbsd.vax

The bootloader has hardcoded filenames that it tries to boot, and <code>netbsd.vax</code> is just the first one it tries.

Note: the bootloader will try other filenames if <code>netbsd.vax</code> is not found, among them for example <code>netbsd</code>, <code>netbsd.bak</code> and <code>netbsd.gz</code>. The last one seems handy to reduce boot time (the bootloader uncompresses the gz file on the fly), however on most VAXen it is probably faster to just load the uncompressed kernel from the server than uncompressing it on the VAX itself...

==Netbooting the VAXstation==
After making sure that mopd, dhcpd and nfsserver are running, boot your VAX from the PROM:
<pre>
>>> b esa0

-ESA0
>> NetBSD/vax boot [Nov 17 2000 07:23:42] > Press any key to abort autoboot 0
Trying BOOTP
Using IP address: 192.168.0.67
myip: (192.168.0.67)
root addr=192.168.0.42 path=/export/vax/root
2534184+69564]=0x27bd9c
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005
The NetBSD Foundation, Inc. All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.

NetBSD 3.0 (INSTALL) #0: Mon Dec 19 04:33:36 UTC 2005
builds@b4.netbsd.org:/home/builds/ab/netbsd-3-0-RELEASE/vax/200512182024Z-obj
/home/builds/ab/netbsd-3-0-RELEASE/src/sys/arch/vax/compile/INSTALL

VAXstation 4000/60
cpu0: KA46
cpu: turning on floating point chip
total memory = 32372 KB
avail memory = 28444 KB
mainbus0 (root)
vsbus0 at mainbus0
vsbus0: 32K entry DMA SGMAP at PA 0x3c0000 (VA 0x803c0000)
vsbus0: interrupt mask 0
le0 at vsbus0 csr 0x200e0000 vec 770 ipl 15 maskbit 1 buf 0x0-0xffff
le0: address 08:00:2b:30:cc:49
le0: 32 receive buffers, 8 transmit buffers
dz0 at vsbus0 csr 0x200a0000 vec 124 ipl 15 maskbit 4
dz0: 4 lines
lkkbd0 at dz0
wskbd0 at lkkbd0 (mux ignored)
asc0 at vsbus0 csr 0x200c0080 vec 774 ipl 15 maskbit 0
asc0: NCR53C94, 25MHz, SCSI ID 6
scsibus0 at asc0: 8 targets, 8 luns per target
md0: internal 1536 KB image area
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 2 lun 0: disk fixed
sd0: 4153 MB, 3421 cyl, 18 head, 138 sec, 512 bytes/sect x 8506782 sectors
sd0: sync (200.00ns offset 15), 8-bit (5.000MB/s) transfers, tagged queueing
sd1 at scsibus0 target 3 lun 0: disk fixed
sd1: 406 MB, 1476 cyl, 9 head, 62 sec, 512 bytes/sect x 832527 sectors
sd1: sync (200.00ns offset 15), 8-bit (5.000MB/s) transfers
boot device: le0
root on md0a dumps on md0b
root file system type: ffs
Clock has lost 13136 day(s) - CHECK AND RESET THE DATE.
</pre>
Congratulations on netbooting a VAX :)

==Troubleshooting==
On your mopd-console, you should see a lot of stuff flashing by soon after you typed <code>b esa0</code>. It should look like this:
<pre>
lavie:/# mopd -d eth0
mopd: not running as daemon, -d given.
MOP RC 802.3 8:0:2b:30:cc:49 > ab:0:0:2:0:0 len 45 code 07 SID
MOP RC 802.3 8:0:2b:30:cc:49 > ab:0:0:2:0:0 len 45 code 07 SID
MOP RC 8:0:2b:30:cc:49 > ab:0:0:2:0:0 len 37 code 07 SID
MOP DL 802.3 8:0:2b:30:cc:49 > ab:0:0:1:0:0 len 47 code 08 RPR
MOP DL 802.3 0:2:b3:98:9f:a1 > 8:0:2b:30:cc:49 len 9 code 03 ASV
MOP DL 802.3 8:0:2b:30:cc:49 > ab:0:0:1:0:0 len 47 code 08 RPR
MOP DL 802.3 0:2:b3:98:9f:a1 > 8:0:2b:30:cc:49 len 9 code 03 ASV
MOP DL 802.3 8:0:2b:30:cc:49 > 0:2:b3:98:9f:a1 len 47 code 08 RPR
Native Image (VAX)
Header Block Count: 1
Image Size: 00011400
Load Address: 00000000
Transfer Address: 00000000
MOP DL 802.3 0:2:b3:98:9f:a1 > 8:0:2b:30:cc:49 len 1498 code 02 MLD
MOP DL 802.3 8:0:2b:30:cc:49 > 0:2:b3:98:9f:a1 len 47 code 08 RPR
Native Image (VAX)
Header Block Count: 1
Image Size: 00011400
Load Address: 00000000
Transfer Address: 00000000
MOP DL 802.3 0:2:b3:98:9f:a1 > 8:0:2b:30:cc:49 len 1498 code 02 MLD
MOP DL 802.3 8:0:2b:30:cc:49 > 0:2:b3:98:9f:a1 len 11 code 0a RML
MOP DL 802.3 0:2:b3:98:9f:a1 > 8:0:2b:30:cc:49 len 1498 code 02 MLD
MOP DL 802.3 8:0:2b:30:cc:49 > 0:2:b3:98:9f:a1 len 11 code 0a RML
MOP DL 802.3 8:0:2b:30:cc:49 > 0:2:b3:98:9f:a1 len 11 code 0a RML
MOP DL 802.3 0:2:b3:98:9f:a1 > 8:0:2b:30:cc:49 len 1498 code 02 MLD
..................
</pre>

the syslog should look something like this:
Dec 25 03:17:24 lavie mopd[7961]: mopd 2.5.3 started.
Dec 25 03:17:24 lavie mopd[7961]: Initialized eth0
Dec 25 03:17:30 lavie mopd[7961]: 8:0:2b:30:cc:49 (2) Do you have 08002b30cc49? (Yes)
Dec 25 03:17:30 lavie mopd[7961]: 8:0:2b:30:cc:49 (2) Do you have 08002b30cc49? (Yes)
Dec 25 03:17:30 lavie mopd[7961]: 8:0:2b:30:cc:49 Send me 08002b30cc49
Dec 25 03:17:30 lavie mopd[7961]: 8:0:2b:30:cc:49 Send me 08002b30cc49
Dec 25 03:17:30 lavie mopd[7961]: hostname: [ipc] len: 3
Dec 25 03:17:30 lavie mopd[7961]: 8:0:2b:30:cc:49 Load completed

If you want to, you can manually specify which file to boot by typing <code>b/100 esa0</code> at the VAX console:
<pre>
>>> b/100 esa0

Bootfile: mopboot

-ESA0
>> NetBSD/vax boot [Nov 17 2000 07:23:42] > Press any key to abort autoboot 0
...
</pre>

You should also have the following entries from dhcpd in your syslog:
Dec 25 03:17:35 lavie dhcpd: DHCPDISCOVER from 08:00:2b:30:cc:49 via eth0
Dec 25 03:17:35 lavie dhcpd: DHCPOFFER on 192.168.0.67 to 08:00:2b:30:cc:49 via eth0
Dec 25 03:17:35 lavie dhcpd: DHCPREQUEST for 192.168.0.67 (192.168.0.42) from 08:00:2b:30:cc:49 via eth0
Dec 25 03:17:35 lavie dhcpd: DHCPACK on 192.168.0.67 to 08:00:2b:30:cc:49 via eth0
You should see all these 4 DHCP packets (DHCPDISCOVER, DHCPOFFER, DHCPREQUEST, DHCPACK), otherwise check your dhcpd configuration

The NFS server also prints one line in the syslog:
Dec 25 03:17:36 lavie rpc.mountd: authenticated mount request from vs4k60:1023 for /export/vax/root (/export)
If this says something like "permission denied", you probably forgot to add your VAX to /etc/hosts.

[[Category:Tutorials]]

Talk:SIMH

2026-09-06T15:06:59Z

Vaxorcist: /* Renaming / Revising SIMH pages */

== SIMH flavors ==
I think it is time to distinguish between the three flavors of SIMH, although they have a lot in common, but the differences grow steadily.

My proposal is a generic SIMH page which might have the following section after the introduction:

<pre>== SIMH Flavors ==

For some time passed there are three flavors of SIMH now:

* [[Classic" SIMH]] ([http://simh.trailing-edge.com/ http://simh.trailing-edge.com/])
* [["New" SIMH]] ([https://github.com/simh/simh https://github.com/simh/simh])
* [["OpenSIMH"]] ([https://opensimh.org/ https://opensimh.org/])
It is relatively hard for a beginner to decide which way to go. I will not give any specific advice, but some short descriptions:

'''"Classic" SIMH''' is the oldest one, whereof the others were forked later on. It is Bob Supnik work mostly, except for some HP simulators. Development apparently stopped (or at least slowed down) in December 2022. The current version is SIMH V3.12-3.

'''"New" SIMH''' was the first bigger fork and added a lot more simulated computer systems.

'''"OpenSIMH"''' forked from "New" SIMH because of insurmountable different opinions of both maintainers and contributors.</pre>

The generic SIMH page should concentrate on the commonalities; the differences should be explained in the three specific pages linked in the gereric page.

What do my fellow writers think? [[User:Vaxorcist|Vaxorcist]] ([[User talk:Vaxorcist|talk]]) 18:12, 2 April 2023 (CEST)

: Sounds good to me. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 19:14, 2 April 2023 (CEST)

== New content ==

Don't do a 'cut and paste' to move the content from [[SIMH/Draft]] to here; let me know, and I can merge the two pages. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 18:02, 3 April 2023 (CEST)

: O.k., I will [[User:Vaxorcist|Vaxorcist]] ([[User talk:Vaxorcist|talk]]) 18:23, 3 April 2023 (CEST)

== Renaming / Revising SIMH pages ==

I think it is time (or rather, long overdue) to rename the following pages:
* SIMH to "Classic" SIMH
* SIMH/Draft to SIMH
and revise both pages.
What do you think? [[User:Vaxorcist|Vaxorcist]] ([[User talk:Vaxorcist|talk]])

: Is the term "'Classic' SIMH" really in use to refer to the old one? Does that version get enough use to make it worth having a separate article for it (as opposed to just covering it in the same article as the current one)? Mind, I don't have a strong preference either way; I am just trying to work out what makes the most sense.
: I took a look at [[SIMH/Draft]], and the article here, and there is a lot of content in this article that isn't in the Draft one, so we'd need to do something a little more complicated than just do some moves. But let's work out the previous point first. (If we wind up editing the good ideas/content from Draft in to this one, or something, don't worry; I can merge the two histories into one once the editing process is complete.) [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 21:25, 2 September 2026 (UTC)

:: There are three variants of SIMH - whether that is desirable or not. And in my opinion, they differ sufficiently from one another to keep them separate.
::The term "Classic SIMH" has become established to refer to the original SIMH written by Bob Supnik. There's still development on this variant, although somewhat sluggish.

::The "New SIMH" is my own wording - the most important difference to the Classic SIMH is the introduction of asynchronous I/O, an improved clock and several other useful additions. Sometimes you can see that this version is called the "V4 SIMH", but I think that's not a good idea as some time sooner or later it might become V5. I was even tempted to call it "Closed SIMH", but I do not want to provoke anyone, even if I do not like what he's doing.

::"OpenSIMH" is an official name given by the founders of the newest SIMH version.

::All in all I think it needs clearly distinguishable names to avoid more confuision as there already is. Imagine a beginner stumbling into this chaos of three similar, but still very different in detail, versions!

::If I had one wish in "bit heaven", I would pray for the reunification of "New SIMH" and "OpenSIMH."

::There are probably good reasons to keep the "Classic SIMH" and a modernized SIMH apart, but noone needs a third one. What a waste of precious time, ideas and resources! Life is too short for such (some rude words here).

::And you're right, all the SIMH related pages need to be more or less revised or created:

::* SIMH/Draft, which shall become the "common" SIMH page
::* SIMH, which shall become the "Classic SIMH" (it is already, but needs an update)
::* New SIMH, which is probably the hardest to write about (at least for me)
::* OpenSIMH, which carries the spirit and recommandation of Bob Supnik
[[User:Vaxorcist|Vaxorcist]] ([[User talk:Vaxorcist|talk]])

Maintenance Operations Protocol

2026-09-06T10:02:29Z

Vaxorcist: New page: Maintenance Operation Protocol

The '''Maintenance Operation Protocol''' (usually abbreviated as "MOP") originated about 1976 as a part of the [[DECnet]] Phase II [[network]] [[protocol]] suite. It provides network services for management and maintenance.

== Naming Conventions ==

* A "host" is a [[computer]] that provides MOP services
* A "satellite" is a computer or network device that uses MOP services.

== Functions ==

MOP provides several functions:

* Down-Line loading (host to satellite) of memory contents, e.g. for booting diskless computers and network devices such as terminal servers
* Up-Line loading (satellite to host) of memory contents, e.g. for failure analysis
* Testing of network hardware and cabling
* Force satellite entry into the MOP mode, i.e. halt current satellite operation and put the satellite into MOP mode. This provides a means for the host to control an unattended satellite system.
* Remote Console

MOP works on the local network link only.

== Configuration ==

MOP is configured via the DECnet [[Network Control Program (DECnet)|Network Control Program]], (usually abbreviated as "NCP").
All configuration takes place on the host computer only.

Most NCP commands used for MOP configuration are identical for all versions of all DEC operating systems. The following examples are for DECnet [[VMS]] V4.0 and newer.

Activate MOP service on circuit <code>UNA-0</code> (= Ethernet device DEUNA or DELUA; replace with your network device type DECnet circuit-id):

$ '''MC NCP SET CIRCUIT UNA-O STATE OFF'''
$ '''MC NCP DEF CIRCUIT UNA-O SERVICE ENABLED'''
$ '''MC NCP SET CIRCUIT UNA-O SERVICE ENABLED STATE ON'''

This enables the host computer to answer any incoming MOP requests on network circuit <code>UNA-0</code>.

If the MOP request is a satellite download request (e.g. for booting), some parameters have to configured first, e.g.:

* Satellite DECnet address
* Satellite node name
* Load file
* ... and possibly others depending on the task to perform.

For details see the respective manuals.

== Debugging ==

For debugging purposes it is helpful to enable MOP related event logging (Examples for VMS V4.0 and later):

Enable [[OPCOM]] messages to the current terminal:
$ '''Reply/Enable'''

Enable DECnet logging to the OPCOM process:
$ '''MC NCP SET LOGGING CONSOLE STATE ON'''

Activate DECnet event 0.3 "Automatic circuit service":
$ '''MC NCP SET LOGGING CONSOLE EVENT 0.3'''

Activate DECnet event 0.7 "Aborted service request":
$ '''MC NCP SET LOGGING CONSOLE EVENT 0.7'''

== History ==

MOP underwent continuous development; the last known revision is 4.0.0, dating from 1992.
With the introduction of VMS V6.2 in 1995, MOP was decoupled from DECnet and integrated into the OpenVMS distribution with the new [[LANCP]] (LAN Control Program) command interface.

{| class="wikitable" style="text-align: center;
|+ MOP Revision History
|-
! Revision !! Date !! Reference
|-
| 1.1 || January 1976 || cited at: AA-D602A-TC Maintenance Operation Protocol, pdf page 37
|-
| 2.0 || March 1978 || [https://www.vaxhaven.com/images/9/9e/AA-D602A-TC.pdf AA-D602A-TC Maintenance Operation Protocol]
|-
| 2.1.0 || October 1980 || [https://www.vaxhaven.com/images/8/8b/AA-K178A-TK.pdf AA-K178A-TK DECnet Digital Network Architecture Phase III Maintenance Operation Protocol]
|-
| 3.0.0 || December 1983 || [http://decnet.ipv7.net/docs/dundas/aa-x436a-tk.pdf AA-X436A-TK DECnet Digital Network Architecture Phase IV Maintenance Operations Functional Specification]
|-
| 4.0.0 || June 1992 || [https://bitsavers.org/pdf/dec/decnet/EK-DNA11-FS-001_MOP_Functional_Specification_V4.0.0_Jun92.pdf EK-DNA11-FS-001 Maintenance Operation Protocol Functional Specification Version 4.0.0]
|}

== See also ==

[[DECnet]]

[[Category: DEC Networking]]
[[Category: DECnet]]

DECnet

2026-09-05T13:55:41Z

Vaxorcist: Corrected DECnet Phase I Release Date from 1975 to 1974

{{wp-orig}}

'''DECnet''' is a proprietary suite of network [[protocol]]s created by [[Digital Equipment Corporation|DEC]], originally released in 1974 in order to connect two [[PDP-11]] [[minicomputer]]s. It evolved into one of the first peer-to-peer network architectures, thus transforming DEC into a networking powerhouse in the 1980s.

Initially built with four layers, it later (1992) evolved into a seven layer [[Open Systems Interconnection|OSI]] compliant networking protocol, around the time when open systems ([[POSIX]] compliant, i.e. [[UNIX|Unix-like]]) were grabbing marketshare from the proprietary OSes, like VMS.

DECnet was built right into the DEC flagship operating system [[VMS|VAX/VMS]] since its inception. Digital also ported it to its own [[Ultrix]] variant of [[UNIX]], as well as [[Apple Macintosh]] computers and PCs running both DOS and Windows under the name '''[[DECnet-DOS]]''' (later renamed to '''[[DEC Pathworks]]''', transforming these systems into DECnet end-nodes in a network of [[VAX]] machines. More recently, an open-source version has been developed for the [[Linux]] OS: see [http://linux-decnet.sourceforge.net/ Linux-DECnet on Sourceforge].

==Brief overview of the evolution of DECnet==

DECnet refers to a specific set of hardware and software networking products which implement the '''DIGITAL Network Architecture''' (DNA). The DIGITAL Network Architecture is essentially a set of documents which define the network architecture in general, state the specifications for each layer of the architecture, and describe the [[protocol]]s which operate within each layer. Although [[packet sniffer|network protocol analyzer tools]] tend to categorize all protocols from DIGITAL as "DECnet", strictly speaking, non-routed DIGITAL protocols such as [[LAT]], [[SCS]], [[AMDS]], [[LAST/LAD]] are not DECnet protocols and are not part of the DIGITAL Network Architecture.

To trace the evolution of DECnet is to trace the development of DNA. The beginnings of DNA were in the early 1970s. DIGITAL published its first DNA specification at about the same time that [[IBM]] announced its [[Systems Network Architecture]] (SNA). Since that time, development of DNA has evolved through the following phases:

==='''Phase I''' (1974)===

Support limited to 2 PDP-11s running the [[RSX-11]] operating system only, with communication over point-to-point ([[DDCMP]]) links between nodes.

==='''Phase II''' (1976)===

Support for networks of up to 32 nodes with multiple, different implementations which could interoperate with each other. Implementations expanded to included [[RSTS/E]], [[TOPS-10]], [[TOPS-20]] and [[VMS]] (from VMS V1.0 / DECnet-VAX V1.0) with communications between processors still limited to point-to-point links only. With Phase II it is not yet possible to send packets to hosts via intermediate nodes, only to hosts that are directly connected to the sender. Introduction of file transfer (FAL), remote file access (DAP), task-to-task programming interfaces and network management features.

==='''Phase III''' (1980)===

Support for networks of up to 255 nodes over point-to point and multi-drop links for [[VMS]] (from VMS V3.0 / DECnet-VAX V3.0) and other DEC operating systems. Introduction of adaptive routing capability, downline loading (MOP), record access, a network management architecture, and gateways to other types of networks including IBM’s SNA and [[ITU-T|CCITT]] Recommendation [[X.25]].

<div style="float:right;margin:15px;margin-top:0px;padding:0px;border: 1px solid #aaa;">

{| border="0" cellspacing="2" cellpadding="2"
|+ '''DECnet Phase IV protocol suite'''
|----- align="left"
! Application
| DAP: Data Access Protocol<BR>
CTERM: Command Terminal
|----- align="left"
! Network Management
| NICE: Network Management protocol<br>
MOP: Maintenance Operation Protocol
|----- align="left"
! Session
| SCP: Session Control Protocol
|----- align="left"
! Transport
| NSP: Network Service Protocol
|----- align="left"
! Network
| DRP: DECnet Routing Protocol
|----- align="left"
! Data link
| DDCMP: Digital Data Communications Message Protocol<br>[[Computer Interconnect|CI]], [[Ethernet]], [[IBM token ring|Token ring]], [[HDLC]], [[Fiber distributed data interface|FDDI]], ...
|----- align="left"
! Physical
| [[Computer Interconnect|CI]], [[Ethernet]], [[IBM token ring|Token ring]], [[Fiber distributed data interface|FDDI]], ...
|}
</div>

==='''Phase IV''' (1982) and '''Phase IV+''' (1983)===

Phase IV was released initially to RSX-11 and VMS systems (from VMS V3.4 / DECnet-VAX V3.1), later TOPS-20, TOPS-10, ULTRIX, [[VAXELN]], and RSTS/E gained support. Support for networks of up to 255 nodes, datalink capabilities expanded beyond [[DDCMP]] to include [[Computer Interconnect|CI]] (VMS only) and [[Ethernet]] [[local area network]] support as the datalink of choice, expanded adaptive routing capability to include hierarchical routing (areas, level 1 and level 2 routers), [[VMScluster]] support (cluster alias) and host services (CTERM).

CTERM allowed a user on one computer to log into another computer remotely, performing the same function that [[Telnet]] does in the [[TCP/IP]] protocol stack. Digital also released a product called the PATHWORKS client, and more commonly known as the PATHWORKS 32 client, that implemented much of DECnet Phase IV for DOS, and 16 and 32 bit Microsoft Windows platforms (all the way through to Windows Server 2003).

Phase IV implemented an 8 layer architecture similar to the [[OSI model|OSI]] (7 layer) model especially at the lower levels ''(see diagram below)''. Since the OSI standards were not yet fully developed at the time, many of the Phase IV protocols remained proprietary.

The Ethernet implementation was unusual in that the software changed the physical address of the Ethernet interface on the network to AA-00-04-00-xx-yy where xx-yy reflected the DECnet network address of the host. This allowed router-less LAN operation because the LAN address could be deduced from the DECnet address. This precluded connecting two NICs from the same DECnet node onto the same LAN segment, however.

The initial implementations released were for VMS and RSX-11, later this expanded to virtually every [[operating system]] DIGITAL ever shipped with the notable exception of [[RT-11]]. DECnet stacks are found on Linux, SunOS and other platforms, and Cisco and other network vendors offer products that can cooperate with and operate within DECnet networks. Full DECnet Phase IV specifications are available.

At the same time that DECnet Phase IV was released, the company also released a proprietary protocol called [[Local Area Transport|LAT]] for serial terminal access via [[Terminal server]]s. LAT is entirely separate from DECnet, though many DECserver LAT terminal servers did use MOP for the server image download and related bootstrap processing.

Enhancements made to DECnet Phase IV eventually became known as DECnet Phase IV+, although systems running this protocol remained completely interoperable with DECnet Phase IV systems.

Phase IV+ (e.g. from VMS 4.0 / DECnet-VAX V4.0) added Support for networks of up to 64,449 nodes (63 areas of 1023 nodes).

==='''Phase V''' and '''Phase V+''' (1987)===

Support for very large (architecturally unlimited) networks, a new network management model, local or distributed name service, improved performance over Phase IV. Move from a proprietary network to an [[Open Systems Interconnection]] (OSI) by integration of ISO standards to provide multi-vendor connectivity and
compatibility with DNA Phase IV, the last two features resulted in a hybrid network architecture (DNA and OSI) with separate “towers” sharing an integrated transport layer. Transparent transport level links to [[TCP/IP]] were added via the [[Internet Engineering Task Force|IETF]] [[Request for Comments|RFC]] 1006 (OSI over IP) and RFC 1859 (NSP over IP) standards ''(see diagram below)''.

It was later renamed '''DECnet/OSI''' to emphasize its OSI interconnectibility, and subsequently '''DECnet-Plus''' as TCP/IP protocols were incorporated.

=== DECnet Phases Interoperability ===

Phase II, III, and IV nodes can all exist on a network. The following types of nodes can be configured as being adjacent to each other:
* Phase II/Phase II
* Phase II/Phase III
* Phase III/Phase III
* Phase III/Phase IV
* Phase IV/Phase IV
* Phase V/? (to be determined)

==DECnet Versions, Manuals and Software Product Descriptions==

===DECnet-VAX===
* DECnet-VAX V1.0
** [https://archive.org/details/bitsavers_decspd25.0_392688 AE-D624B-TE SPD 25.03.01 DECnet-VAX Version 1.pdf]

* DECnet-VAX V1.3
** AE-D624E-TE SPD 25.3.4 DECnet-VAX, Version 1.3

* DECnet-VAX V3.0
** [http://bitsavers.org/pdf/dec/vax/vms/3.0/AA-H802B-TE_DECnet-VAX_3.0_Users_Guide_198205.pdf AA-H802B-TE DECnet-VAX User's Guide]

* DECnet-VAX V3.1
** AA-H803C-TE DECnet-VAX System Manager's Guide

* DECnet-VAX V4.x
** [https://archive.org/details/stx_AA-Y512C-TE_VMS_4.4_VAX_VMS_Networking_Manual_Apr86 AA-Y512C-TE VAX/VMS Networking Manual]
** [https://archive.org/details/stx_AA-Z425C-TE_VMS_4.4_VAX_VMS_Network_Control_Program_Reference_Manual_Apr86 AA-Z425C-TE VAX/VMS Network Control Program Reference Manual]

* DECnet-VAX V5.x
** [http://bitsavers.org/pdf/dec/vax/vms/5.0/AA-LA50A-TE_VMS_5.0_Network_Control_Program_Manual_198804.pdf AA-LA50A-TE VMS Network Control Program Manual]
** [http://bitsavers.org/pdf/dec/vax/vms/5.0/AA-LA47A-TE_Guide_to_DECnet-VAX_Networking_5.0_198804.pdf AA-LA47A-TE Guide to DECnet-VAX Networking]
** [http://bitsavers.org/pdf/dec/vax/vms/5.0/AA-LA48A-TE_VMS_5.0_Networking_Manual_198804.pdf AA-LA48A-TE VMS Networking Manual]
** [http://bitsavers.org/pdf/dec/vax/vms/SPD/AE-D624Z-TE_DECnet-VAX_V5.1_SPD_25.03.25_Jan89.pdf AE-D624Z-TE DECnet-VAX Version 5.1 SPD 25.03.25]
** [http://bitsavers.org/pdf/dec/vax/vms/5.4/Release_Notes/AE-NJ32C-TE_DECnet-VAX_Version_5.4_SPD_25.03.28_Aug1990.pdf AE-NJ32C-TE DECnet-VAX Version 5.4 SPD 25.03.28]

* DECnet-VAX V6.0:
** [http://www.vaxhaven.com/images/0/09/AA-PV60A-TK.pdf AA-PV60A-TK DECnet for OpenVMS Networking Manual]
** [https://www.digiater.nl/openvms/doc/alpha-v8.3/83final/documentation/pdf/DECNET_OVMS_GD_Network.PDF AA-PV5ZA-TK DECnet for OpenVMS Guide to Networking]
** [https://www.digiater.nl/openvms/doc/alpha-v8.3/83final/documentation/pdf/DECNET_OVMS_NET_UTIL.PDF AA-PV61A-TK DECnet for OpenVMS Network Management Utilities]

* DECnet-VAX V8.4:
** [https://vmssoftware.com/docs/VSI_DECnet_IV_Network_Util_Ref.pdf DO-DNTNMU-01A VSI OpenVMS DECnet Network Management Utilities]

===DECnet-11M===
* DECnet-11M V2.0
** [https://usermanual.wiki/Document/1075057802DECnet11M.2303482373/view AE-3431F-TC DECnet-11M SPD 10.75.05]

* DECnet-11M V4.0 / DECnet-11M-PLUS V2.0
** AA-H224C-TC DECnet-RSX System Manager's Guide
** AA-X924A-TC DECnet-RSX System Manager's Minireference Guide
** AA-J517C-TC DECnet-RSX Release Notes

* DECnet-11M V4.2 / RSX-11M-PLUS V3.0
** [http://bitsavers.org/pdf/dec/decnet/decnetRSX/4.2_Sep85/AA-J517D-TC_DECnet-RSX_Release_Notes_Sep85.pdf AA-J517D-TC DECnet-RSX Release Notes]
** [http://bitsavers.org/pdf/dec/decnet/decnetRSX/4.2_Sep85/AA-EB30A-TC_DECnet-RSX_Guide_to_Network_Management_Utilities_Sep85.pdf AA-EB30A-TC DECnet-RSX Guide to Network Management Utilities]
** [http://bitsavers.org/pdf/dec/decnet/decnetRSX/4.2_Sep85/AA-EB29A-TC_DECnet-RSX_Network_Management_Concepts_and_Procedures_Sep85.pdf AA-EB29A-TC DECnet-RSX Network Management Concepts and Procedures]
** [http://bitsavers.org/pdf/dec/decnet/decnetRSX/4.2_Sep85/AA-M098C-TC_DECnet-RSX_Programmers_Reference_Manual_Sep85.pdf AA-M098C-TC DECnet-RSX Programmers Reference Manual]
** [http://bitsavers.org/pdf/dec/decnet/decnetRSX/4.2_Sep85/AA-H223D-TC_DECnet-RSX_Guide_to_User_Utilities_Sep85.pdf AA-H223D-TC DECnet-RSX Guide to User Utilities]
** [http://bitsavers.org/pdf/dec/decnet/decnetRSX/4.2_Sep85/AA-H225D-TC_DECnet-RSX_Network_Generation_and_Installation_Guide_Sep85.pdf AA-H225D-TC DECnet-RSX Network Generation and Installation Guide]

* DECnet-11M V4.3 / DECnet-11M-PLUS V4.0
** [http://bitsavers.org/pdf/dec/decnet/decnetRSX/4.3_Oct87/AA-EB28B-TC_DECnet-RSX_Network_Management_Concepts_and_Procedures_Oct87.pdf AA-EB28B-TC DECnet-RSX Network Management Concepts and Procedures]
** [http://bitsavers.org/pdf/dec/decnet/decnetRSX/4.3_Oct87/AA-H223E-TC_DECnet-RSX_Guide_to_User_Utilities_Oct87.pdf AA-H223E-TC DECnet-RSX Guide to User Utilities]
** [http://bitsavers.org/pdf/dec/decnet/decnetRSX/4.3_Oct87/AA-H225E-TC_DECnet-RSX_Network_Generation_and_Installation_Guide_Oct87.pdf AA-H225E-TC DECnet-RSX Network Generation and Installation Guide]
** [http://bitsavers.org/pdf/dec/decnet/decnetRSX/4.3_Oct87/AA-J517E-TC_DECnet-RSX_Release_Notes_Oct87.pdf AA-J517E-TC DECnet-RSX Release Notes]
** [http://bitsavers.org/pdf/dec/decnet/decnetRSX/4.3_Oct87/AA-M098D-TC_DECnet-RSX_Programmers_Reference_Manual_Oct87.pdf AA-M098D-TC DECnet-RSX Programmers Reference Manual]

* DECnet-11M V4.5 / DECnet-11M-PLUS V4.3
** [http://bitsavers.org/pdf/dec/decnet/decnetRSX/4.5_Oct89/AA-EB28C-TC_DECnet-RSX_V4.5_Network_Management_Concepts_and_Procedures_Oct89.pdf AA-EB28C-TC DECnet-RSX Network Management Concepts and Procedures]
** [http://bitsavers.org/pdf/dec/decnet/decnetRSX/4.5_Oct89/AA-EB30C-TC_DECnet-RSX_V4.5_Guide_to_Network_Management_Utilities_Oct89.pdf AA-EB30C-TC DECnet-RSX Guide to Network Management Utilities]
** [http://bitsavers.org/pdf/dec/decnet/decnetRSX/4.5_Oct89/AA-H223F-TC_DECnet-RSX_V4.5_Guide_to_User_Utilities_Oct89.pdf AA-H223F-TC DECnet-RSX Guide to User Utilities]
** [http://bitsavers.org/pdf/dec/decnet/decnetRSX/4.5_Oct89/AA-H225F-TC_DECnet-RSX_V4.5_Network_Generation_and_Installation_Guide_Oct89.pdf AA-H225F-TC DECnet-RSX Network Generation and Installation Guide]
** [http://bitsavers.org/pdf/dec/decnet/decnetRSX/4.5_Oct89/AA-J517F-TC_DECnet-RSX_V4.5_Supplemental_Information_and_Release_Notes_Oct89.pdf AA-J517F-TC DECnet-RSX Supplemental Information and Release Notes]
**[http://bitsavers.org/pdf/dec/decnet/decnetRSX/4.5_Oct89/AA-M098E-TC_DECnet-RSX_V4.5_Programmers_Reference_Manual_Oct89.pdf AA-M098E-TC DECnet-RSX Programmers Reference Manual]

* DECnet-11M V4.8 / DECnet-11M-PLUS V4.6
** [http://mim.update.uu.se/manuals/network/decnet6.pdf AA-J517K-TC DECnet-RSX Supplemental Information and Release Notes]
** [http://www.bitsavers.org/pdf/dec/pdp11/rsx11/SPD/AE-J513N-TC_DECnet-11M-PLUS_V4.6_SPD_10.66.12_Feb99.pdf AE-J513N-TC DECnet-11M-PLUS, Version 4.6 SPD 10.66.12]

===DECnet/E===
* DECnet/E V1.0
** [http://www.bitsavers.org/pdf/dec/spd/10.73.02_7808_DECnetE.pdf AE-D427B-TC DECnet/E, Version 1.0 SPD 10.73.02]

* DECnet/E V2.0
** [http://www.bitsavers.org/pdf/dec/pdp11/rsts/DECnetE/AA-H505B-TC_DECnet-E_V2.0_System_Managers_Guide_Jan82.pdf AA-H505B-TC DECnet/E System Manager's Guide]

===PRO/DECnet===
* PRO/DECnet V2.1

===DECnet-DOS===
* DECnet-DOS V1.1
** [http://bitsavers.org/pdf/dec/decnet/decnetDOS/DECnet-DOS_V1.1_Release_Note.txt DECnet-DOS Release Notes]
** [http://bitsavers.org/pdf/dec/decnet/decnetDOS/AA-GV32A-TV_DECnet-DOS_V1.1_Mini-Reference_Guide_Apr86.pdf AA-GV32A-TV DECnet-DOS Mini-Reference Guide]
** [http://bitsavers.org/pdf/dec/decnet/decnetDOS/AA-EB46B-TV_DECnet-DOS_Programmers_Reference_Manual_Apr86.pdf AA-EB46B-TV DECnet-DOS Programmer's Reference Manual]

* DECnet-DOS V3.0
** AA-PAFFA-TK DECnet-DOS Getting Started

===DECnet-ULTRIX===
* DECnet-ULTRIX V1.1
** DECnet Ultrix V1.1 Release Notes

* DECnet-ULTRIX V2.0
** AA-EE38C-TE ULTRIX-32 DECnet Network Management

* DECnet/ULTRIX V3.0
** AA-JD82D-TE DECnet-ULTRIX Release Notes
** BH-EA86G-TE DECnet/ULTRIX Version 3.0 and 3.0a SPD 26.83.06
** AA-EA87D-TE DECnet-ULTRIX Installation Guide
** AA-EA88C-TE DECnet-ULTRIX User's and Programmer's Guide

* DECnet-ULTRIX V4.0
** [https://archive.org/download/h42_DEC_DECnet_Ultrix/DEC_DECnet_Ultrix.pdf AA-EE38D-TE DECnet Ultrix Network Management]
** [https://ia800704.us.archive.org/26/items/h42_DEC_DECnet_Ultrix/DEC_DECnet_Ultrix.pdf AA-JD82E-TE DECnet-ULTRIX Release Notes]
** [https://ia902801.us.archive.org/9/items/bitsavers_decvaxultrAAPB62ATEDECnetUltrix4.0NCPCommandRefere_4966828/AA-PB62A-TE_DECnet_Ultrix_4.0_NCP_Command_Reference_May1990.pdf AA-PB62A-TE_DECnet-Ultrix NCP Command Reference]
** [http://www.bitsavers.org/pdf/dec/vax/ultrix-32/DECnet_Ultrix_4.0/SPD268308_DECnet_Ultrix_4.0_May1990.pdf AE-EA86J-TE DECnet-Ultrix Version 4.0 SPD 26.83.08]

* DECnet-ULTRIX V4.2
** DECnet-ULTRIX Release Notes V4.2

===DECnet-RT===
* DECnet-RT V1.0
** [http://www.bitsavers.org/pdf/dec/spd/10.72.01_7802_DECnet-RT.pdf DECnet-RT Version 1.0 SPD 10.72.01]

* DECnet-RT V1.1
** SPD10.72.4 DECnet-RT V1.1.pdf
** SPD10.72.5 DECnet-RT V1.1.pdf

* DECnet-RT V2.0
** SPD10.72.7 DECnet-RT V2.0.pdf
** SPD10.72.8 DECnet-RT V2.0.pdf

===DECnet/8===
* DECnet/8 V1.0
** 06.01.01_7705_DECNET8.pdf

===DECnet-10===
* DECnet-10 V2.0
** 08.60.01_7712_DECnet-10.pdf

===DECnet-20===
* DECnet-20 V1.0
** 23.02.00_7809_DECnet-20_V1.pdf

* DECnet-20 V2.0
** AA-5091B-TM_TOPS-20_DECnet-20_Programmers_Guide_Jan80.pdf

===DECnet-11D===
* DECnet-11D V2.0
** 10.70.05_7806_DECnet-11D.pdf

===DECnet-11S===
* DECnet-11S V2.0
** 10.74.05_7802_DECnet-11S.pdf

===DECnet-IAS===
* DECnet-IAS V2.0
** 10.71.03_7802_DECnet-IAS.pdf

==References==

* Carl Malamud, ''Analyzing DECnet/OSI Phase V''. Van Hostrand Reinhold, 1991. ISBN 0-442-00375-7.

* James Martin, Joe Leben, ''DECnet Phase V: An OSI Implementation''. Digital Press, 1992. ISBN 1-55580-769-0.

* DECnet-Plus manuals for OpenVMS are available at http://www.hp.com/go/openvms/doc/

* DECnet Phase IV OpenVMS manuals for DECnet Phase IV; these Phase IV manuals are archived on OpenVMS Freeware V5.0 distribution, at http://www.hp.com/go/openvms/freeware and other sites.

* DECnet Phase IV architecture manuals (including DDCMP, MOP, NICE, NSP, DAP, CTERM, routing); at http://ftp.digital.com/pub/DEC/DECnet/PhaseIV/ and other sites.

==See also==

* [[HECnet]], a hobbyist DECnet bridged over IP.

==Related articles and practical guides==

* [[DECnet Routing and DECnet Router]]
* [[DECnet on VMS]]
* [[DECnet on RSX-11M]]
* [[DECnet on RSTS/E]]
* [[Installing, Configuring, and Testing DECnet V1.3 on VMS V2.0]]

[[Category: Network Protocols]]
[[Category: DECnet]]

MOP

2026-09-05T07:09:43Z

Vaxorcist: New Redirect MOP => Maintenance Operations Protocol

#Redirect [[Maintenance Operations Protocol]]

[[Category: DEC Acronyms]]

Talk:SIMH

2026-09-02T19:29:10Z

Vaxorcist: /* Renaming / Revising SIMH pages */ new section

DECwriter III

2025-12-29T08:31:22Z

Vaxorcist: Correction: The LA100 is a printer terminal like the LA120, but in a desktop version according to: EB-24944-18 Micro_PDP-11 Handbook 1983-84

The '''DECwriter III''', also known as the '''LA120''', is the third in a series of printing terminals by [[Digital Equipment Corporation]], introduced in 1978.

There are two versions, one freestanding model, called the LA120, and one desktop model, designated LA100.

It was preceded by the [[DECwriter II]] in 1974.

It was succeeded by the [[DECwriter IV]] in 1982.

{{stub}}

{{Nav DEC Terminals}}

[[Category: DEC Printing Terminals]]

Remote Switching Control Bus

2025-12-14T19:06:21Z

Vaxorcist: "also known as DEC Power Bus" added

The '''Remote Switching Control Bus''' (also known as '''DEC Power Bus''') was a power control [[bus]] used across many [[Digital Equipment Corporation|DEC]] product lines to allow remote control of power. It contained three lines: a [[ground return]], a 'power on', and an 'emergency shutdown'. (Not all devices used the last, e.g. the illustrated example below.)

[[Image:PwrControlBusConn.jpg|150px|thumb|right|Cable connector]]

The bus was connected using 3-pin AMP MATE-N-LOK connectors: all units with a remote control input used a male shell (with female sockets); all the cables (normally 3-conductor, #22 gauge, but 2-conductor is seen, as on the right) had female shells (with male pins), on both ends.

The male shell (housing) was a 1-480304-0, and took 61173-1 sockets (i.e. female pins); the female shell was a 1-480305-0, and took 61174-1 male pins. (There are a large number of different pin options: 30-22, 24-18, and 20-14 gauge; tin and gold plated; and brass and phosphor-bronze material. The part numbers given are for tinned brass, 30-22 gauge.)

AMP has been bought by TE Connectivity, but these MATE-N-LOK connectors are still in production, and available from the usual suppliers.

[[Category: DEC Electrical]]

DEC acronyms

2025-12-05T18:41:45Z

Vaxorcist: UUT = Unit Under Test added

'''Acronyms''' from [[Digital Equipment Corporation]]. (Listings given in ''italics'' are not just DEC acronyms.)

{| class="wikitable"
|-
! Acronym
! Meaning
|-
| APT
| [[Automated Product Test]]
|-
| BR
| [[Bus request line|Bus Request]] ([[UNIBUS]])
|-
| CBOX
| Cache Box
|-
| CFS
| [[Common File System]] ([[PDP-10]]/[[TOPS-20]])
|-
| CI
| [[Computer Interconnect]]
|-
| CMI
| [[CPU/Memory Interconnect]]
|-
| CRD
| [[Customer Runnable Diagnostic]]
|-
| CSC
| [[Customer Support Center]]
|-
| CSS
| [[Computer Special Systems]]
|-
| DBN
| [[DSA Standard Disk Format#Diagnostic Block Numbers (DBNs)|Diagnostic Block Number]]
|-
| DCL
| [[Digital Command Language]]
|-
| DCS
| [[Digital Classified Software]]
|-
| DDC
| [[Digital Diagnostic Center]]
|-
| DRS
| [[Diagnostic Runtime Services]]
|-
| DSA
| [[Digital Storage Architecture]]
|-
| DSC
| [[Disk Save and Compress]]
|-
| DSDF
| [[DSA Standard Disk Format]]
|-
| DSR
| [[Digital Standard Runoff]]
|-
| DSSI
| [[Digital Storage Systems Interconnect]]
|-
| DUP
| [[Diagnostic and Utility Protocol]]
|-
| EBOX
| Execution Box
|-
| ECO
| ''[[Engineering Change Order]]''
|-
| FRU
| ''[[Field Replaceable Unit]]''
|-
| IBOX
| Instruction Box
|-
| GPX
| [[Graphics Processing Extension]]
|-
| GIDIS
| [[General Image Display Instruction Set]]
|-
| JBOX
| Junction Box
|-
| LAD
| Local Area Disk
|-
| LAST
| Local Area System Transport
|-
| LAT
| Local Area Transport
|-
| LAVC
| [[Local Area VAXcluster]]
|-
| LBN
| ''[[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Logical Block Number]]''
|-
| MDM
| [[MicroVAX Diagnostic Monitor]]
|-
| MBOX
| Memory Box
|-
| MCR
| [[Monitor Console Routine]]
|-
| MDS
| [[Maintenance Documentation Service]]
|-
| MSCP
| [[Mass Storage Control Protocol]]
|-
| ODS-2
| [[On-disk Structure 2]]
|-
| OTS
| [[Object Time System]]
|-
| PPD
| [[Systems Communication Architecture|Port/Port Driver Layer]]
|-
| PPL
| [[Periodic Payment License]]
|-
| RBN
| [[DSA Standard Disk Format#Replacement Block Numbers (RBNs)|Replacement Block Number]]
|-
| RCT
| [[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Replacement/Revectoring Control Table]]
|-
| RDC
| [[Digital Remote Diagnosis Center]]
|-
| RMS
| [[Record Managment Services]]
|-
| SBB
| [[System Building Block]]
|-
| SBI
| [[Synchronous Backplane Interconnect]]
|-
| SCA
| [[Systems Communication Architecture]]
|-
| SCS
| [[Systems Communication Architecture|Systems Communication Services]]
|-
| SDA
| [[System Dump Analyzer]]
|-
| SDB
| [[Standard Drive Bus]]
|-
| SDI
| [[Standard Disk Interconnect]]
|-
| SDL
| Structure Definition Language
|-
| STI
| [[Standard Tape Interconnect]]
|-
| UETP
| [[User Environment Test Package]]
|-
| UPI
| [[DEC Unique Product Identifier|Unique Product Identifier]]
|-
| UQSSP
| [[UNIBUS]] [[QBUS]] Storage Systems Port
|-
| UUT
| Unit Under Test
|-
| UWS
| [[ULTRIX Worksystem Software]]
|-
| VAXBI
| [[VAX Bus Interconnect]]
|-
| VBOX
| Vector Box
|-
| VDS / VAX/DS
| [[VAX Diagnostic Supervisor]]
|-
| VUP
| [[VAX Unit of Performance]]
|-
| VWS
| [[VAX Workstation Software]]
|-
| WCS
| [[Writable Control Store]]
|-
| XBN
| [[DSA Standard Disk Format#External Block Numbers (XBNs)|External Block Number]]
|-
| XMI
| [[Extended Memory Interconnect]]
|}

[[Category: Digital Equipment Corporation]]
[[Category:DEC Naming/Numbering Schemes]]
[[Category: DEC Acronyms]]

Batch processing

2025-11-23T11:23:22Z

Vaxorcist: Changed wording

'''Batch processing''' is the name for the usual manner in which early [[computer]]s (but not the very earliest) were used (although it continued to exist for a long period afterwards). [[Time-sharing]] had not yet been invented, so [[user]]s generally did not interact directly with 'their' computer in [[real-time]]; instead, they gathered up their [[program]] and its [[input]] data (together usually referred to as a [[job]]), and handed the whole thing as a unit over to the [[computer operator]], whose task it was to care for the machine, and 'run' all the jobs submitted to it by users. The submitted jobs formed a queue, and the operator would run them in order, one after the other - hence the name for this manner of using computers.

Some [[operating system]]s offered a mixed environment of:

* Interactive [[terminal]] sessions, and
* Batch processing of large / compute intensive jobs, either:
** submitted interactively at a user terminal, or
** through decks of [[punched card]]s at the [[card reader]].

This allowed the user terminal to be kept free for interactive work and otherwise unused computer capacity to be used for batch jobs at a lower priority.

Although in the very earliest days there were no operating systems, and submitted programs ran on the [[hardware|'bare metal']], [[subroutine package|subroutine libraries]] quickly appeared to do such things as perform [[input/output|I/O]] on behalf of the user; these evolved into [[batch operating system]]s, specialized in performing batch processing.

[[Category: OS Basics]]
[[Category: Computer Basics]]

Card reader

2025-11-23T11:21:05Z

Vaxorcist: New Page "Card reader"

A '''card reader''' is a device that reads [[punched cards]] and transmits their data to another device (e.g., a [[computer]]).

It either contains its own [[controller]] or is connected to an external controller, which may be a computer option, for example.

Citation from "[http://bitsavers.org/pdf/dec/unibus/DEC-11-HCRB-D_CR11_Mar72.pdf DEC-11-HCRB-D CR11 Card Reader System Manual]":

''"Most available card readers operate in a characteristic manner. The reader itself consists of an input hopper for loading a number of cards, a photoelectric read station for reading data from the card, an output hopper for stacking the cards after reading, a motorized mechanism for moving the cards, and control logic for generating command and status signals.''

''Operation begins when the controller issues a read command. When the card reader receives this command, it picks the first card from the hopper and feeds it into the read station. As the data holes or marks pass through the read station, they are sensed by a photoelectric device. At the same time, the reader generates a series of index or clock marks. These marks are transmitted to the controller simultaneously with the data bits read from the holes in the card. Thus, the controller receives 12 bits of parallel data on the 12 data output lines of the card reader connector.''

''The card reader furnishes alarm signals to warn of any error condition present in the reader. It also provides signals for certain housekeeping functions such as hopper empty, stacker full, and unit busy."''

== See also ==
[[CR11 Card Readers]]

{{semi-stub}}

[[Category: Device Basics]]

Batch processing

2025-11-21T15:22:01Z

Vaxorcist: "Mixed interactive/batch processing" added

'''Batch processing''' is the name for the usual manner in which early [[computer]]s (but not the very earliest) were used (although it continued to exist for a long period afterwards). [[Time-sharing]] had not yet been invented, so [[user]]s generally did not interact directly with 'their' computer in [[real-time]]; instead, they gathered up their [[program]] and its [[input]] data (together usually referred to as a [[job]]), and handed the whole thing as a unit over to the [[computer operator]], whose task it was to care for the machine, and 'run' all the jobs submitted to it by users. The submitted jobs formed a queue, and the operator would run them in order, one after the other - hence the name for this manner of using computers.

Some [[operating system]]s offered a mixed environment of:

* Interactive [[terminal]] sessions, and
* Batch processing of large / compute intensive jobs, either:
** submitted interactively at a user terminal, or
** through decks of [[punched card]]s at the [[card reader]].

This allowed the user terminal to be kept free for interactive work and unused computer capacity to be used for batch jobs at a lower priority.

Although in the very earliest days there were no operating systems, and submitted programs ran on the [[hardware|'bare metal']], [[subroutine package|subroutine libraries]] quickly appeared to do such things as perform [[input/output|I/O]] on behalf of the user; these evolved into [[batch operating system]]s, specialized in performing batch processing.

[[Category: OS Basics]]
[[Category: Computer Basics]]

VAX Diagnostic Supervisor

2025-11-18T21:10:46Z

Vaxorcist: /* Some useful VDS commands */ Cosmetics ...

VDS - '''VAX Diagnostic Supervisor''' (sometimes abbreviated to VAX/DS) is a set of diagnostic software programs for the [[DEC]] [[VAX]] computers and peripheral devices.

== Intro ==

'''''"At best, a computer is as good as its diagnostic tools!"'''''

That's what they must have thought at DEC when they developed their diagnostic software.

Here we will take a closer look at the VAX Diagnostic Supervisor and also a quick side look at the [[User Environment Test Package]] (UETP).

== Using VDS for simulated VAX Computers ==

You may ask: "What are the VAX diagnostics good for when run on a simulated VAX?"

Yes, many diagnostics do not run on a simulated VAX, but some work very well and are used e.g. for testing the various [[SIMH]] VAX simulators for correct execution of the VAX native mode instructions.

Furthermore you can explore how precise the simulation mimics the real hardware.

If you plan to test your real VAX, you can familiarize yourself with VDS and prepare your diagnosis in SIMH, and SIMH can assist you in preparing and creating a diagnostic kit on media appropriate for your VAX.

Automated testing script for a SIMH VAX-11/750:

SET CLOCK NOCALIBRATE=600K
ATTACH -RQ RQ0 VAX_MINIMUM_DIAGS.dsk
EXPECT "DS> " SEND "ATTACH UDA50 DW0 DUA 772150 154 5 10\r"; GO -Q
EXPECT "DS> " SEND "ATTACH RA81 DUA DUA0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH KA750 CMI KA0 yes yes yes 0 0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH DW750 CMI DW0 8\r"; GO -Q
EXPECT "DS> " SEND "SET LOAD DUA0:[SYSMAINT]\r"; GO -Q
EXPECT "DS> " SEND "SELECT KA0\r"; GO -Q
EXPECT "DS> " SEND "SET FLAGS TRACE\r"; GO -Q
EXPECT "DS> " SEND "RUN EVKAB\r"; GO -Q
BOOT -Q RQ0 /R5:10

== VDS History ==

VDS development began in parallel that to the first [[VAX]] model, the [[VAX-11/780]] in 1977.

VDS was provided soley for the '''''"big VAXen"''''' (i.e. not for the [[MicroVAX]] and [[VAXstation]] computers), with one remarkable exception, the [[MicroVAX I]], resp. [[VAXstation I]].
Each new VAX model received its CPU-specific VDS modules up to the [[VAX 9000]]; only the VAX models of the last two series, [[VAX 7000]] and [[VAX 10000]], were covered by other diagnostic methods.

== Program Levels ==

All VAX diagnostic programs are assigned to a '''level'''. Levels are numbered 1, 2R, 2, 3, 4, and 5. A program’s level indicates its run-time environment.

* '''Level 1''' diagnostic programs run under an operating system. They do not use the VAX/DS. (=> UETP)
* '''Level 2R''' diagnostic programs run under VAX/DS in user mode only.
* '''Level 2''' diagnostic programs run in both user mode and standalone mode, under the control of the VAX/DS.
* '''Level 3''' diagnostic programs run only in standalone mode, under the control of the VAX/DS.
* '''Level 4''' diagnostic programs run in standalone without VAX/DS.
* '''level 5''' diagnostic programs run in [[Writable Control Store|WCS]] or system console, not in VAX main memory. They do not use the VAX/DS.

Only the levels 2R, 2, and 3 are managed by VDS.

== Sections, Tests, Subtests, and Flags ==

All diagnostic programs that run under the VAX/DS are composed of one or more '''sections'''. Each section has a name, and it is possible to specify, by name, which section of the program to execute. A program section can have one of two functions, depending on its design:

* Test a certain major portion of the unit under test.
* Facilitate a certain mode of testing. For example, there might be a quick-verify section, used to give the device a quick (but not thorough) test.

In order to determine the number and names of the sections in a particular diagnostic program, use the <code>SHOW SECTIONS</code> command. However, every program contains a default section called <code>DEFAULT</code>, which will execute automatically if you do not specifically select a section. A section is selected with the <code>/SECTION</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Each section is composed of a set of '''tests'''; each test verifies either a particular function of the hardware or a particular subset of the component logic being tested. The VAX/DS allows you to specify which tests within a section to run. Each test may have some '''subtests'''. Tests are selected with the <code>/TEST</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Two sets of '''flags''' are provided to control certain aspects of a diagnostic program’s execution. These flags may be set or cleared before the diagnostic program is started.

One set of flags is called the '''VAX/DS control flags'''. The flags in this set are interpreted by the VAX/DS and their meanings are the same in all diagnostic programs. The VAX/DS control flags are set with the <code>SET FLAGS</code> command.

The other set of flags is referred to as the '''event flags'''. This set consists of 23 flags whose purposes are defined by the diagnostic programs. The user must read the documentation for specific diagnostic programs to determine if a definition has been assigned to any of the event flags. <code>SET EVENT FLAGS</code> command.

== Some useful VDS commands ==

* <code>'''SET LOAD disk:[directory]'''</code> Set diagnostic load path
* <code>'''LOAD''' Exxxx</code> Load diagnostic Exxxx (where "Exxxx" is replaced by the diagnostics name, e.g. EVKAA)
* <code>'''SET TRACE'''</code> Show progress
* <code>'''SHOW FLAGS'''</code> Show VDS flags
* <code>'''SHOW TESTS'''</code> Show the available tests of the loaded diagnostic
* <code>'''SHOW SECTIONS'''</code> Show the available sections of the loaded diagnostic
* <code>'''START/TEST='''first:last</code> Start a subset of the loaded diagnostics tests (where "first" is the test number to start with, and -optionally- "last" is the last one to execute)
* <code>'''START/SECTION='''section-name</code> Start a single section of the loaded diagnostic (where "section-name" is the name of the section to run)
* <code>'''START/PASSES='''count</code> Start the loaded diagnostic for "count" passes (where "count" is the number of passes to execute)
* <code>'''RUN''' exxxx'''/TEST='''first:last</code> Run a subset of the diagnostics tests; if "last" is not given, all tests from start up the the last one are run, to run a single test, enter "=n:n", where "n" is the test number
* <code>'''RUN''' exxxx'''/SECTION='''section-name</code> Run a single section of the diagnostic
* <code>'''RUN''' exxxx'''/PASSES='''count</code> Run the diagnostic for "count" passes

Use a pass count of 0 to run a program continuously. If you do this, the program will run until you type CTRL/C or a failure occurs with the <code>HALT</code> flag set.

== Diagnostic Program Documentation ==

Documentation provided for each diagnostic program includes:

* '''Help file'''
:: The help file is referenced with the HELP command. It contains any operating instructions that may be unique to the diagnostic program. The help file for diagnostic program EVXYZ is EVXYZ.HLP; the help file for the VAX/DS is EVSAA.HLP

* '''Documentation file'''
:: The documentation file provides a detailed description of a diagnostic program's function, run-time requirements, operating instructions, fault detection, and maintenance history, plus explanations of each test’s function and execution flow. The documentation file for diagnostic program EVXYZ is EVXYZ.DOC.

* '''Source Code listings'''
:: Source code listings of the diagnostic programs are available. All VAX/DS diagnostic programs are structured in a standard format. For example, the initialization code for every diagnostic program is always located in the same relative area within the listing. To fully understand the source code listings of a VAX/DS diagnostic program, refer to the VAX Diagnostic Design Guide.

The help file for a diagnostic program is shipped with the diagnostic program. The documentation file and source codelistings are available by ordering a [[Maintenance Documentation Service]] Option on microfiche.

== Diagnostic Scopes ==

There are two diagnostic scopes.

* A CPU-specific scope: '''CPU Cluster Testing'''
* A scope for the identical diagnostic programs for all types of VAX computers: '''Peripheral Diagnostics'''

=== CPU Cluster Testing ===

'''NOTE: The term "CPU cluster" used here means all components belonging to a CPU; there is no connection with the term [[VAXcluster|"VAXcluster" (alternatively: "VMScluster")]].'''

The VAX CPU cluster is tested by a set of programs, existing at several program levels, as follows:

* Level 5
** Console tests
** Processor tests
** Memory tests
* Level 4
** VAX instruction set test (hardcore for VDS)
** Cache and translation buffer tests (VAX-11/750 only)
* Level 3
** Memory tests (if no level 5 test possible)
** Channel adapter tests
** Cluster exerciser

'''NOTE: The term "Channel adapter" used here means bus adapter, e.g. for [[UNIBUS]] or [[MASSBUS]].'''

This set of programs implements the VAX diagnostic strategy by providing a set of building blocks by which a system may be tested, starting with the level 5 basic processor tests and ending with the level 3 cluster exerciser, which is a program meant to exercise all components of the cluster.

=== Peripheral Diagnostics ===

Thorough testing of a peripheral device requires the development of three different diagnostic programs. For each device type the following will typically (but not necessarily) exist:

* A level 3 logic test
* A level 3 function test
* A level 2R function test

This group of programs implements the diagnostic strategy by providing a facility for producing very accurate and detailed identifications of fault conditions via the level 3 programs and by also providing a method by which the device may be tested without bringing down the customer's operating system via the level 2R program.

The level 3 logic test will provide the greatest detail of error resolution, indicating which section of logic is failing. This program will be used by technicians to repair bad logic boards, and will provide very high test coverage. Some devices contain ROM-resident microprograms ("self-tests") that perform logic testing, making a level 3 logic test unnecessary.

The level 3 function test will provide a comprehensive test of all of the device’s functions. This program will be used to determine accurately whether or not a device is operating correctly. This is the definitive function test and provides very high test coverage. Level 3 function tests are usually required even if the device possesses self-testing capabilities, because self-tests generally are not capable of complete detection of function failures.

The level 2R program will typically consist of a subset of the level 3 function test. It will test as much of the device’s functionality as can be tested in the user (VMS) environment. The tests it contains are exact or approximate copies of tests existing in the level 3 program.

A typical sequence of use for these programs, when dealing with a system at a customer site, is as follows:

# The customer (or field service) suspects a fault existing in the device.
# The level 2R program is run to see if the error can be detected without stopping the operating system. If the error is found, go to step 4.
# If the level 2R program cannot identify the fault, the operating system is brought down and the level 3 function test is run.
# The fault is identified and the failing [[Field Replacable Unit|FRU]] is replaced. The operating system is then brought back up.
# The failing FRU is brought back to DIGITAL, where the level 3 logic test, the level 3 function test, or perhaps a module test station is used to identify the failing logic on the FRU. The FRU is repaired.

== VAX Diagnostic Coding Convention ==

VAX diagnostic program names consist of 5 letters and a two-digit version number, e.g.: ECKAL-3.4:

* E = VAX
* C = 11/750
* K = CPU
* A = Supervisor
* L = Unique identifier
* 3 = Major revision
* 4 = Minor Revision

See the following 1986 VAX Diagnostic Coding Convention Table for letter breakdown:

EPXYD-R.P

E = System

E = VAX

P = Processor

B = VAX 8200/8300
D = VAX 8600
S = VAX 11780
T = VAX 11785
C = VAX 11750
N = VAX 11730 and 11725
H = MicroVAX I
J = VAX 8820/8830/8840
V = More than one VAX Processor
X = VAX 6000
Z = VAX 8530/8550/8700/8800

X = Device Category

A = Application (CR, LP, A-D, Misc.)
C = Channel Adaptors (MBA, UBA)
D = Communication Devices (DMC, DZ11)
G = CI Adapter
K = CPU
L = Database Files
M = Magnetic Tape (TE, TU, DT)
P = Test Equipment
Q = QIO Device Driver
R = Rotating Memory (RP, RK, RM, RS, RX)
S = System Monitor (Supervisor, Tape Monitor)
T = Terminal (LA36, VT52)
U = Utilities (Script file, Copy, Update)
W = Workstations
X = System Exerciser (EXR/BUSINT)
Z = Media Packages
0-9 = Engineering File

Y = Device Type

Category Application
A = Line Printers, LP, LCP01
B = Card Readers, CR
L = LPA11-K
Category Channel
A = MBA
B = UBA, DWBUA
C = MA780
D = IEC11, IEU11-A, DR70
E = DT07
F = DEC DATAWAY
G = CI780
H = CI750/CI780 MICROCODE VERIFICATION (INTERNAL)
I = TEST BED ADAPTERS
J = NBI ADAPTER
K = CIBCI

Category Communications
A = DZ11,DZ32,DMZ32,DHU11,DMB32
B = DMC
C = Multiple Devices
D = DR11-C
E = DV11
F = DR780,DF11-W
G = DQS11
H = KMC11-B
I = KMS11-B
J = DM11-BA
K = DMS11-BA
L = DMF32 Combo
M = DMC11,DMR11,DMP11
N = DN11
O = CPI32
P = PCL11
R = DR11B,DR11-W,DRE11
S = DRS11/DSS
T = KCT32-A,FEPCM
U = DUP11
X = Multiple Devices
W = UNA
Y = DEBNT

Category Database Files
A = CRD DATABASE FILES
B = SYSTEM EXERCISER DATABASE FILES

Category Magnetic Tape
A = TE16/77, TS11, TU78, TS05
B = TU81,TU80

Category QIO Device Drivers
For this category, the fourth and fifth letters of the code are the device mnemonic.
For example, EVQDB is the QIO device driver for the DB, or RP disk series.

Category Test Equipment
A = CI780 Node Tester
B = NI Tester

Category Rotating Memory
A = Multiple devices
B = RP04/5/6
C = DCL/RP04/5/6
D = RM03/RM05/RM80
E = RK611,RK06,RK07
F = RL02
G = RM80
H = RP07
I = RX02
J = ML11
K = IDC
L = UDA50(RA60,RA80,RA81)
M = RC25
N = RUX50

Category System Monitor
A = Supervisor
B = Autosizer
C = DYDDM

Category Terminals
A = All Terminals
B = Terminal exerciser
C = VS11
D = 11C03-LH Fastek
G = VS70

Category Utility
A = Script File
B = Copy Command file
C = Updating file

Category Workstation
A = VS100

Category Exerciser
B = Exerciser Bus Interaction

D = Fifth character makes the code unique. A through Z and 1 through 9.

R = Revision (MAJOR)
P = Revision (MINOR)

== Distribution of Diagnostic Programs ==

Typically, a VAX computer came with all the necessary diagnostic programs on console media at no additional charge, e.g.:

* VAX-11/780: [[RX01/02 floppy drive|RX01 floppies]]
* VAX-11/750, VAX-11/730, and VAX-11/725: [[TU58 DECtape II|TU58 cartridges]]
* VAX 8600: [[RL01/02 disk drive|RL02 disk pack]]
* VAX 8200, VAX 8250, VAX 8300, and VAX 8350: [[RX50 dual-diskette drive|RX50 floppies]]

Additionally, you could buy larger collections of diagnostic programs on [[magnetic tape]] or [[Removable-pack disk|removable disk packs]].

Extended documentation was available on microfiche at an extra charge.

== VMS User Enviroment Test Package (UETP) ==

From the very beginning of VMS V1.0 there was the '''[[User Enviroment Test Package]]''' (UETP), see: [http://bitsavers.trailing-edge.com/pdf/dec/vax/vms/2.0/AA-D643B-TE_VAX-VMS_2.0_UETP_Users_Guide_198003.pdf VAX/VMS UETP User’s Guide AA-D643A-TE]

Quote from the first UETP manual:

"''The UETP is a collection of tests designed to demonstrate that the hardware and software components of a VAX/VMS system are in working order. DIGITAL software support representatives run the UETP on a newly installed VAX/VMS system as the formal sample procedure.''"

UETP is still used in the latest version of VMS (V9.2-2 for x86 as of this writing).

[https://docs.vmssoftware.com/vsi-openvms-system-manager-s-manual-volume-2-tuning-monitoring-and-complex-systems/#_6017UETP| See here] for the latest VMS UETP manual.

== ULTRIX System Exerciser Package ==

[[ULTRIX]] has got a very similar tool to verify proper hardware operation at the operating system level, the '''[[System Exerciser Package]]'''.

For the earliest reference found so far see the manual: [https://drive.google.com/file/d/1i3LoLAvTQC7dZl-T9X3SsQgg_6s_6TCY/view?usp=sharing ULTRIX-32 2.2 System Exercisers 1987 AA-KS95A-TE]

The MIPS variants of ULTRIX include the System Exerciser Package, too.

== Additional Diagnostic Tools ==

* On-board ROM-based diagnostics (RBDs) / Self-tests
* [[Diagnostic and Utility Protocol|DUP]] for [[Mass Storage Control Protocol|MSCP]] devices

== CPU-specific Supervisors ==

* '''EBSAA''' VAX 8200/8250/8300/8350 & VS8000 Diagnostic Supervisor
* '''ECSAA''' VAX-11/750 DIAGNOSTIC SUPERVISOR
* '''EDSAA''' VAX 8600/8650 Diagnostic Supervisor
* '''EHSAA''' MicroVAX I VDS
* '''EJSAA''' VAX 8820/8830/8840 Diagnostic Supervisor
* '''ELSAA''' VAX 6210/6220/6230/6240/6310/6320/6330/6340/6350/6360 Diagnostic Supervisor
* '''ENSAA''' VAX 725/730 Diagnostic Supervisor
* '''ESSAA''' VAX 780/785 Diagnostic Supervisor
* '''EXSAA''' VAX 6000 Diagnostic Supervisor
* '''EZSAA''' VAX 8530/8550/8700/8800/8820N Diagnostic Supervisor
* '''E?SAA''' VAX 9000 Diagnostic Supervisor

There is no supervisor for the series of VAX 7000 / VAX 10000 computers (see: [http://www.vaxhaven.com/images/4/4d/EK-7001A-TS-001.pdf VAX 7000 Advanced Troubleshooting EK-7001A-TS-001])

== Set of Diagnostics for a SV-BXTAA VAX-11/750 System ==

A SV-BXTAA VAX-11/750 System consists of:

* [[KA750 CPU|VAX-11/750 CPU]]
* [[MS750 Memory System|MS750 1MB memory]]
* [[DECwriter IV|LA38 printing console terminal]]
* [[RH750 Massbus Adapter]]
* [[RM02/03 disk drive|RM03 MASSBUS disk drive subsystem]]
* [[DZ11 asynchronous serial line interface|DZ11 terminal adapter]]
* [[TS11 Subsystem|TS11 magnetic tape unit]]

The diagnostics set for this system is made of:

* CPU-specific diagnostic main program
** '''ECSAA''' VAX 11750 DIAG SUPERVISOR

* VAX-common automatic sizing program which automatically determines the current system configuration
** '''EVSBA''' VAX AUTOSIZER DIAGNOSTIC

* Set of VAX-11/750 CPU diagnostics
** '''ECKAA''' VAX 11750 UDIAG MON
** '''ECKAB''' VAX 11750 MICRO DPM
** '''ECKAC''' VAX 11750 MICRO MIC
** '''ECKAD''' VAX FP750 MICRODIAG
** '''ECKAF''' VAX KC750 UDIAG
** '''ECKAL''' VAX 11750 CACHE/TB DIAG
** '''ECKAM''' VAX 11750 MEMORY DIAG
** '''ECKAX''' VAX 11750 CLUSTER EXER

* VAX-common instruction set diagnostic
** '''EVKAA''' VAX INSTRUCTION SET TEST

* VAX-11/750 bus diagnostics
** '''ECCAA''' VAX 11750 RH750 DIAG
** '''ECCBA''' VAX 11750 UBI/DW750 DIAG

* Set of VAX-common peripheral diagnostics
** '''EVTAA''' VAX TERMINAL DIAGNOSTIC
** '''EVTBA''' VAX TERMINAL EXERCISER
** '''EVDAA''' VAX DZ11 8 LINE ASYNC MUX
** '''EVMAA''' VAX TM03/TE16/TU45-77 Tape
** '''EVRDA''' VAX RM03/RM05/RM80 DISKLESS
** '''EVRDB''' VAX RM03/RM05 FUNCTIONAL TEST

== Booting the VAX Diagnostic Supervisor ==

The command to boot the VAX Diagnostic Supervisor on a SIMH VAX is:

BOOT RQ0 /R5:10

* <code>RQ0</code> is the device identifier for the MSCP disk, unit 0, where the diagnostics are stored; adjust this according to your requirements.
* <code>/R5:10</code> is the boot flag to boot the Diagnostic Supervisor located in directory <code>DUA0:[SYSMAINT]</code> or <code>DUA0:[SYS0.SYSMAINT]</code>.

For booting the VAX Diagnostic Supervisor on a real VAX refer chapter 2.1 of the "'''VAX DS Diagnostic Supervisor User's Guide'''" [[#ref_1|[1]]]

== Sample run of the VDS EVSBA AUTOSIZER ==

DS> '''LOAD EVSBA.EXE'''
DS> '''SET FLAGS QUICK'''
DS> '''START /SECTION:MANUAL'''

.. Program: EVSBA - AUTOSIZER LEVEL 3, revision 5.1, 3 tests,
at 18:18:28.19.

COMMAND? '''HELP'''

HELP

This is a manual section command. This program creates ATTACH
commands for all devices in the system.
(ATTACH,CHANGE,EXIT,HELP,LIST,READ,SIZE,WRITE) - These commands
control the sizer in manual and selftest mode.
To obtain further information type HELP followed by a topic.
For example;
HELP MANUAL

Additional information available:

ATTACH CHANGE DEFAULT DEVICE EVENT
EXIT HELP LIST MANUAL QUICK
READ SECTION SELFTEST SCRIPT SIZE
SUMMARY WRITE

COMMAND? '''SIZE'''
COMMAND? '''LIST'''
FILE IN MEMORY 'CONFIG.COM'
!! AUTOMATIC SIZING PROGRAM.
!! THIS IS A TOOL AND NOT A DIAGNOSTIC PROGRAM.
!! CONFIGURATION FILE FOR SYSTEM.
!! COMPUTER GENERATED CPU TYPE 2 MICROCODE REV LEVEL = 99
!! NUMERIC VALUES WITH A LEADING ZERO ARE ASSIGNED.
!! FILE VALID ONLY FOR STANDARD HARDWARE CONFIGURATION.
!! TIME IS 15-FEB-1984 18:18:56.85
!!
!! *** QUICK FLAG SET. NO CHECKS MADE FOR TERMINALS ON DZ11/DZ32'S ***
!!
!!
!! DEFINE PROCESSOR...
!!
DS> ATTACH KA750 HUB KA0 YES YES YES 027FF 0
!!
!! DEFINE MEMORY...
!!
DS> ATTACH MS750 MS0
!!
!! DEFINE UNIBUS ADAPTERS...
!!
DS> ATTACH DW750 HUB DW0
!!
DS> ATTACH LP11 DW0 LPA 777514 0200 04
DS> ATTACH LP25 LPA LPA0 !! *** PRINTER TYPE IS ESTIMATED ***
DS> ATTACH TS11 DW0 MSA0 772520 0224 05
DS> ATTACH UDA50 DW0 DUA 772150 0154 05 02
DS> ATTACH RA81 DUA DUA0
DS> ATTACH RA60 DUA DJA2
DS> ATTACH RX50 DUA DUA3
DS> ATTACH DZ11 DW0 TTA 760100 0300 05 EIA
DS> ATTACH DZ11 DW0 TTB 760110 0310 05 EIA
DS> ATTACH DZ11 DW0 TTC 760120 0320 05 EIA
DS> ATTACH DZ11 DW0 TTD 760130 0330 05 EIA
COMMAND? '''WRITE'''
CONFIGURATION FILE IS NORMALLY READ/WRITTEN TO THE SUPERVISOR CONSOLE MEDIA
VERIFY SUPERVISOR CONSOLE MEDIA LOADED.
VERIFIED? [(Yes), No] '''YES'''
COMMAND? '''EXIT'''
DS>

== See also ==

* [[Running VDS Diagnostics on the SIMH VAX-11/750]]

== External links ==

This page contains condensed information from several DEC manuals, among others:

* [http://bitsavers.org/pdf/dec/vax/diag/EP-EVNDX-25.0_Oct86.txt EVNDX25 VAX DIAGNOSTIC INDEX]
* [https://vt100.net/mirror/hcps/si75fin1.pdf EK-SI75F-IN-001 VAX-11-750 Installation Manual] pdf-page 60ff
* <div id="ref_1">[1] [http://bitsavers.org/pdf/dec/vax/diag/VAX_Diagnostic_Supervisor_Users_Guide_Apr89.pdf AA-FK66A-TE VAX DS Diagnostic Supervisor User's Guide] </div>
* [http://bitsavers.org/pdf/dec/vax/diag/EK-1VAXD-TM-001_VAX_Diagnostic_Design_Guide_Aug79.pdf EK-1VAXD-TM-003 VAX Diagnostic Design Guide]
* [http://bitsavers.org/pdf/dec/vax/diag/AA-FK67A-TE_VAX_Diagnostic_Design_Guide_Apr89.pdf AA-FK67A-TE VAX Diagnostic Design Guide]
* [http://www.bitsavers.org/pdf/dec/vax/vms/1.5/2b/AA-D643A-TE_VAX_VMS_UETP_Users_Guide_Aug78.pdf AA-D643A-TE VAX/VMS UETP User’s Guide]
* [http://www.trailing-edge.com/~shoppa/11780diags/ VAX-11/780 Diagnostic Help Files]
* [https://manx-docs.org/collections/antonio/dec/MDS-2000-01/cd1/VAX/7001ATS1.PDF EK-7001A-TS-001 VAX 7000 Advanced Troubleshooting]

[[Category: VAX]]
[[Category: VAX Software]]
[[Category: VAX Diagnostic Software]]
[[Category: SIMH Tutorials]]
[[Category: VMS Practical Guides]]

MicroVAX I

2025-11-17T08:49:29Z

Vaxorcist: /* Diagnostics */ Link to page "Using VDS Diagnostics on the MicroVAX I" added.

{{InfoboxVAX-Data
| name = MicroVAX I
| Announcement = October 1983
| FRS-date = late 1984
| Codename = Seahorse
| OS-support-VMS = [[MicroVMS]] V1.0 to VMS V5.0-2
| OS-support-ULTRIX = ULTRIX/VAX V1.0 to ULTRIX/VAX V2.4?
| Enclosure = [[BA23 Enclosure|BA23]]
| CPU-module = [[KD32 CPU|KD32-AA]]
| Num-proc = 1
| Translation-buffer = 512 entries [[#ref_1|[1]]]
| Cache = 8KB
| Compatibility-mode = No
| Console-processor = CPU
| Console-device = None
| Minimum-memory = 512KB
| Maximum-memory = 4MB
| BUS-Qbus = 1 @ 3.3MB/s
| LAN-support = optional
| [[VUP]]s = 0.36
}}
The '''MicroVAX I''' was the first of a number of [[MicroVAX]] models from [[Digital Equipment Corporation|DEC]]. It used the [[QBUS]] as its primary [[bus]] between the [[Central Processing Unit|CPU]] (the [[KD32 CPU]]) and [[main memory]], the only [[VAX]] to do so. It was said to be the slowest VAX ever (about 0.25 [[VAX Unit of Performance|VUPs]]), even slower than the [[VAX-11/730]] resp. [[VAX-11/725]].

The two [[printed circuit board|boards]] of the MicroVAX I CPU communicate over the [[CD interconnect]] of the [[QBUS backplanes#Backplane types|H9278 backplane]], and an [[over the top]] [[flat cable]].

With a [[VCB01 Video Controller|VCB01]] Monochrome Video Subsystem added, the MicroVAX I becomes a [[VAXstation I]].

==Boot ROM==

===Boot ROM Restrictions===

The MicroVAX I [[bootstrap]] [[ROM]] can only bootstrap a system disk attached to the '''first''' [[Mass Storage Control Protocol]] (MSCP) controller.
It cannot boot from a [[TK50]] tape drive at all, and booting from an [[Ethernet]] network adapter like an [[DEQNA]] or [[DELQA]] is restricted, i.e. it cannot become member of an [[Local Area VAXcluster|LAVC]].

All these limitations do not apply to its successor, the [[MicroVAX II]].

See the instructions from:
[https://www.it-bcsb.de/download/MicroVMS%20Installation%20and%20Operation%20Guide%20-%20AA-KM46A-TN.pdf AA-KM46A-TN MicroVMS 4.6 Installation and Operations], Chapter C.1 Creating a Console Diskette:

The console diskette will contain files used to bootstrap from a disk attached to the
'''second''' MSCP controller. Use the following steps to create a console diskette. This
example assumes that the first RC25 disk attached to the second MSCP controller
(DABO:) will be the new system disk:

# Log in to the system manager's account, '''SYSTEM'''.
# Check the first diskette drive to ensure that it is empty and inactive; the red diskette activity light should not be glowing. If there is a diskette in the drive, remove it following the instructions in Section 3.1.11.
# Label a scratch diskette '''CONSOLE DISKETTE'''. A scratch diskette is a new diskette or a diskette containing no information that you want to save.
# Enter the following command to invoke the command procedure that creates a console diskette for a MicroVAX I system: <br>
: <PRE>$ @SYS$UPDATE:VMBUVAX1
: What system disk do you want to be able to boot from? DABO</PRE>
: Ignore the informational messages displayed on your terminal screen. The procedure prompts you for the name of the diskette drive on which the intermediate media (console diskette) will be mounted. In this example, the media is mounted in diskette drive 1 (DUA1).
: <PRE>Where will the intermediate RX50 media be mounted? DUA1</PRE>
: Insert the diskette labeled '''CONSOLE DISKETTE''' into drive 1 and enter '''YES''' in response to the following prompt:
: <PRE>Are you ready? YES</PRE>
: When it has finished building the console diskette, the system displays the following message: <br>
: <PRE>The media on DUA1 may now be used to boot device DABO</PRE>
After you create the console diskette, write-protect it to prevent anyone from accidentally overwriting the contents. To write-protect a diskette, cover the square notch in the upper-right comer of the diskette with a silver tab. Note that in order to bootstrap the system, the console diskette must be in diskette drive 1.

You may want to add the following command to the end of '''SYS$MANAGER:SYSTARTUP.COM''' to mount the console diskette automatically every time you bootstrap the system. This prevents other users from removing the diskette thinking that the drive is not in use.

<PRE>$ MOUNT/SYSTEM/FOREIGN $FLOPPY1 INTERMEDIATE</PRE>

----
'''NOTE'''

The command procedure '''SYS$UPDATE:VMBUVAX1.COM''' and other files needed might not be on the system disk depending on the option used when the system was installed.

You can install the missing components using:
<PRE>$ @SYS$UPDATE:VMSINSTAL UTIL $TAPE1:</PRE>
The tape (resp. tape image) AQ-FP13D-BN_MICROVMS_4.6_87 must be loaded (resp. attached to) the [[TK50]] tape drive beforehand.

Answer all questions with '''N''':
<PRE>* Do you want to install the entire kit: N
* Do you want to install the MAIL utility: N
* Do you want to install the SEARCH utility: N
* Do you want to install the DIFF utility: N
* Do you want to install the DUMP utility: N
* Do you want to install the RUNOFF utility: N
* Do you want to install the PHONE utility: N
* Do you want to install the MicroVMS HELP library: N
* Do you want to install the Remote terminal support via SET HOST/DTE: N
* Do you want to install the Foreign Terminal Support: N
* Do you want to install the LAT-11 terminal server support (via Ethernet): N
* Do you want to install the Stand-alone backup on system disk support: N</PRE>
except for:
<PRE>* Do you want to install the MicroVAX-I bootstrap that works for any MSCP system device: Y</PRE>

You should now be able to set up the special boot diskette for booting from a disk attached to the second MSCP controller.

===Supported Boot Devices===
* All [[RQDX Series of MFM Disk & Floppy QBUS Controllers|RQDX]] supported devices
* [[MRV11-D]]

===Boot ROM Characteristics===
* Microverify is the name given to the diagnostics executed by the MicroVAX I boot ROM. There are three LEDs on the DAP module and a seven segment display on the patch panel which will isolate the problem (if any) to one of the two CPU modules.
* Floating Point Instructions in Microcode
* No TOY Clock

==Options==

There are a lot of MicroVAX I Options; some of them are not "officially supported", but work nevertheless.

===Memory Options===

The MicroVAX I uses standard Q-bus memories which are not as fast but are also less expensive and usable by both the MicroVAX I and other 16-bit processors (such as the MicroPDP-11).
There are 22 address lines on the Q-bus, limiting maximum memory to 4 MB.

* [[MSV11-P]] Parity Memory
* [[MSV11-Q]] Parity Memory
* [[MSV11-M]] Parity Memory: not supported and not yet tested, but supposed to work
* [[MSV11-J]] PMI ECC Memory: not supported, but working! (-JD and -JE variants '''''only'''''; the -JB and -JC '''will not work''')
* [[MSV11-R]] PMI Parity Memory: not supported and not yet tested, but supposed to work

===Mass Storage Options===

* [[RQDX1/RQDX2 MFM Disk & Floppy QBUS Controllers|RQDX1]]
* [[RQDX1/RQDX2 MFM Disk & Floppy QBUS Controllers|RQDX2]]
* [[RQDX3 MFM Disk & Floppy QBUS Controller|RQDX3]]
* [[RX50]]
* [[RD51]]
* [[RD52]]
* [[RD53]]
* [[RD54]]
* [[RD31]]
* [[RD32]]
* [[RQC25]] RC25 Disk System with Qbus Controller, made of:
** [[M7740]]
** [[RC25]]

The [[SIMH]] MicroVAX I supports the [[RLV12]] controller for [[RL01/02 disk drive|RL01 and RL02]] removable disks.

It is currently unknown/untested whether the 'real' MicroVAX I supports the RLV12 controller as well.

Anyway, booting from an RL01/RL02 is not supported by the MicroVAX I boot ROM.

===Communication Options===

* [[DLV11-J asynchronous serial line interface|DLVJ1]]
* [[DZV11]]
* [[DHV11]]
* [[DHQ11]]
* [[DZQ11 asynchronous serial line interface|DZQ11]] not supported, but working!
* [[DEQNA]]
* [[DELQA]]

===Video Options===

* [[VCB01 Video Controller|VCB01]] Monochrome Video Subsystem


==MicroVAX I Diagnostics==

MicroVAX I is the only MicroVAX model with "old-style" '''[[VAX Diagnostic Supervisor]]''' (VDS) diagnostics.

For details on MicroVAX I diagnosis, see: [[Using VDS Diagnostics on the MicroVAX I]]

==Sample MicroVAX I Boot Messages (MicroVMS V4.6)==

These messages are taken from my 'real' MicroVAX I:

<PRE>
MICROVERIFY STARTED

MICROVERIFY PASSED

00000000 03

>>>B DUA0
ATTEMPTING BOOTSTRAP

MicroVMS Version V4.6 6-Jul-1987 17:00

PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 28-MAR-2022 8:28

The MicroVMS system is now executing the system startup procedure.

The MicroVMS system is now executing the site-specific startup commands.

%RUN-S-PROC_ID, identification of created process is 00000015
%RUN-S-PROC_ID, identification of created process is 00000017
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
SYSTEM job terminated at 28-MAR-2022 08:30:57.94

MicroVMS V4.6

Username: SYSTEM

Welcome to MicroVMS V4.6

Last interactive login on Saturday, 3-DEC-2022 17:59
Last non-interactive login on Monday, 3-JUN-2013 15:41

Main Menu

1 - Exit to DCL
2 - Log out of the SYSTEM account
3 - Invoke the MAIL utility
4 - Invoke the PHONE utility
5 - Add a user account to the system
6 - Install optional software
7 - Add or Delete a MicroVMS component
8 - Create or Modify an Autologin Terminal
9 - Back up or Restore the user files on a disk
10 - Build a Standalone BACKUP kit
11 - Set the maximum number of interactive logins
12 - Configure the network
13 - Shut down or start up the network
14 - SHUT DOWN the system

Enter a number (? or ?# for HELP): 1

If you wish to use the menus again, type the following:
$ @SYS$MANAGER:MGRMENU

$
</PRE>

==See also==

* [[Installing and Configuring MicroVMS V4.0 on a MicroVAX I]]

==References==

<div id="ref_1">[1] MicroVAX Handbook. EB-25156-47</div>
<div id="ref_2">[2] Systems & Options Catalog. European Edition. Spring 1990.</div>

==Further reading==

* ''MicroVAX Handbook'', 1984 (EB-25156-47) - extensive coverage of hardware and software

==External links==

* [http://www.bitsavers.org/pdf/dec/vax/610/ MicroVAX I] - documentation at [[Bitsavers]]
** [http://www.bitsavers.org/pdf/dec/vax/610/EK-VS200-TM-PRE_VAXstation_I_Technical_Reference_Manual_Preliminary_198411.pdf VAXstation I Technical Reference Manual] (EK-VS200-TM-PRE)
* [https://manx-docs.org/collections/hcps/kd32aomcn1.pdf MicroVAX I Owner's Manual Release Notes] (EK-KD32A-OM-CN1)
* [http://www.bitsavers.org/pdf/dec/vax/handbook/Supermicrosystems_Handbook_1986.pdf Supermicrosystems Handbook] - the MicroVAX I is covered on pp. 2-4–2-5 (pp. 19-20 of the PDF) and elsewhere
* [http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/hardware/micronotes/numerical/micronote22.txt Differences between the MicroVAX I and the MicroVAX II CPUs] ([[MicroNote]] #022)
* [https://ai.eecs.umich.edu/people/conway/VLSI/VLSIDesMag/Articles/MicroVAX-DataPath.VDec83.pdf The MicroVAX I Data-path Chip]

{{Nav VAX}}

[[Category: MicroVAX Systems]]
[[Category: QBUS VAX Systems]]

MicroVAX I

2025-11-17T08:43:09Z

Vaxorcist: /* Boot ROM Restrictions */ "Bootstrap" link added

{{InfoboxVAX-Data
| name = MicroVAX I
| Announcement = October 1983
| FRS-date = late 1984
| Codename = Seahorse
| OS-support-VMS = [[MicroVMS]] V1.0 to VMS V5.0-2
| OS-support-ULTRIX = ULTRIX/VAX V1.0 to ULTRIX/VAX V2.4?
| Enclosure = [[BA23 Enclosure|BA23]]
| CPU-module = [[KD32 CPU|KD32-AA]]
| Num-proc = 1
| Translation-buffer = 512 entries [[#ref_1|[1]]]
| Cache = 8KB
| Compatibility-mode = No
| Console-processor = CPU
| Console-device = None
| Minimum-memory = 512KB
| Maximum-memory = 4MB
| BUS-Qbus = 1 @ 3.3MB/s
| LAN-support = optional
| [[VUP]]s = 0.36
}}
The '''MicroVAX I''' was the first of a number of [[MicroVAX]] models from [[Digital Equipment Corporation|DEC]]. It used the [[QBUS]] as its primary [[bus]] between the [[Central Processing Unit|CPU]] (the [[KD32 CPU]]) and [[main memory]], the only [[VAX]] to do so. It was said to be the slowest VAX ever (about 0.25 [[VAX Unit of Performance|VUPs]]), even slower than the [[VAX-11/730]] resp. [[VAX-11/725]].

The two [[printed circuit board|boards]] of the MicroVAX I CPU communicate over the [[CD interconnect]] of the [[QBUS backplanes#Backplane types|H9278 backplane]], and an [[over the top]] [[flat cable]].

With a [[VCB01 Video Controller|VCB01]] Monochrome Video Subsystem added, the MicroVAX I becomes a [[VAXstation I]].

==Boot ROM==

===Boot ROM Restrictions===

The MicroVAX I [[bootstrap]] [[ROM]] can only bootstrap a system disk attached to the '''first''' [[Mass Storage Control Protocol]] (MSCP) controller.
It cannot boot from a [[TK50]] tape drive at all, and booting from an [[Ethernet]] network adapter like an [[DEQNA]] or [[DELQA]] is restricted, i.e. it cannot become member of an [[Local Area VAXcluster|LAVC]].

All these limitations do not apply to its successor, the [[MicroVAX II]].

See the instructions from:
[https://www.it-bcsb.de/download/MicroVMS%20Installation%20and%20Operation%20Guide%20-%20AA-KM46A-TN.pdf AA-KM46A-TN MicroVMS 4.6 Installation and Operations], Chapter C.1 Creating a Console Diskette:

The console diskette will contain files used to bootstrap from a disk attached to the
'''second''' MSCP controller. Use the following steps to create a console diskette. This
example assumes that the first RC25 disk attached to the second MSCP controller
(DABO:) will be the new system disk:

# Log in to the system manager's account, '''SYSTEM'''.
# Check the first diskette drive to ensure that it is empty and inactive; the red diskette activity light should not be glowing. If there is a diskette in the drive, remove it following the instructions in Section 3.1.11.
# Label a scratch diskette '''CONSOLE DISKETTE'''. A scratch diskette is a new diskette or a diskette containing no information that you want to save.
# Enter the following command to invoke the command procedure that creates a console diskette for a MicroVAX I system: <br>
: <PRE>$ @SYS$UPDATE:VMBUVAX1
: What system disk do you want to be able to boot from? DABO</PRE>
: Ignore the informational messages displayed on your terminal screen. The procedure prompts you for the name of the diskette drive on which the intermediate media (console diskette) will be mounted. In this example, the media is mounted in diskette drive 1 (DUA1).
: <PRE>Where will the intermediate RX50 media be mounted? DUA1</PRE>
: Insert the diskette labeled '''CONSOLE DISKETTE''' into drive 1 and enter '''YES''' in response to the following prompt:
: <PRE>Are you ready? YES</PRE>
: When it has finished building the console diskette, the system displays the following message: <br>
: <PRE>The media on DUA1 may now be used to boot device DABO</PRE>
After you create the console diskette, write-protect it to prevent anyone from accidentally overwriting the contents. To write-protect a diskette, cover the square notch in the upper-right comer of the diskette with a silver tab. Note that in order to bootstrap the system, the console diskette must be in diskette drive 1.

You may want to add the following command to the end of '''SYS$MANAGER:SYSTARTUP.COM''' to mount the console diskette automatically every time you bootstrap the system. This prevents other users from removing the diskette thinking that the drive is not in use.

<PRE>$ MOUNT/SYSTEM/FOREIGN $FLOPPY1 INTERMEDIATE</PRE>

----
'''NOTE'''

The command procedure '''SYS$UPDATE:VMBUVAX1.COM''' and other files needed might not be on the system disk depending on the option used when the system was installed.

You can install the missing components using:
<PRE>$ @SYS$UPDATE:VMSINSTAL UTIL $TAPE1:</PRE>
The tape (resp. tape image) AQ-FP13D-BN_MICROVMS_4.6_87 must be loaded (resp. attached to) the [[TK50]] tape drive beforehand.

Answer all questions with '''N''':
<PRE>* Do you want to install the entire kit: N
* Do you want to install the MAIL utility: N
* Do you want to install the SEARCH utility: N
* Do you want to install the DIFF utility: N
* Do you want to install the DUMP utility: N
* Do you want to install the RUNOFF utility: N
* Do you want to install the PHONE utility: N
* Do you want to install the MicroVMS HELP library: N
* Do you want to install the Remote terminal support via SET HOST/DTE: N
* Do you want to install the Foreign Terminal Support: N
* Do you want to install the LAT-11 terminal server support (via Ethernet): N
* Do you want to install the Stand-alone backup on system disk support: N</PRE>
except for:
<PRE>* Do you want to install the MicroVAX-I bootstrap that works for any MSCP system device: Y</PRE>

You should now be able to set up the special boot diskette for booting from a disk attached to the second MSCP controller.

===Supported Boot Devices===
* All [[RQDX Series of MFM Disk & Floppy QBUS Controllers|RQDX]] supported devices
* [[MRV11-D]]

===Boot ROM Characteristics===
* Microverify is the name given to the diagnostics executed by the MicroVAX I boot ROM. There are three LEDs on the DAP module and a seven segment display on the patch panel which will isolate the problem (if any) to one of the two CPU modules.
* Floating Point Instructions in Microcode
* No TOY Clock

==Options==

There are a lot of MicroVAX I Options; some of them are not "officially supported", but work nevertheless.

===Memory Options===

The MicroVAX I uses standard Q-bus memories which are not as fast but are also less expensive and usable by both the MicroVAX I and other 16-bit processors (such as the MicroPDP-11).
There are 22 address lines on the Q-bus, limiting maximum memory to 4 MB.

* [[MSV11-P]] Parity Memory
* [[MSV11-Q]] Parity Memory
* [[MSV11-M]] Parity Memory: not supported and not yet tested, but supposed to work
* [[MSV11-J]] PMI ECC Memory: not supported, but working! (-JD and -JE variants '''''only'''''; the -JB and -JC '''will not work''')
* [[MSV11-R]] PMI Parity Memory: not supported and not yet tested, but supposed to work

===Mass Storage Options===

* [[RQDX1/RQDX2 MFM Disk & Floppy QBUS Controllers|RQDX1]]
* [[RQDX1/RQDX2 MFM Disk & Floppy QBUS Controllers|RQDX2]]
* [[RQDX3 MFM Disk & Floppy QBUS Controller|RQDX3]]
* [[RX50]]
* [[RD51]]
* [[RD52]]
* [[RD53]]
* [[RD54]]
* [[RD31]]
* [[RD32]]
* [[RQC25]] RC25 Disk System with Qbus Controller, made of:
** [[M7740]]
** [[RC25]]

The [[SIMH]] MicroVAX I supports the [[RLV12]] controller for [[RL01/02 disk drive|RL01 and RL02]] removable disks.

It is currently unknown/untested whether the 'real' MicroVAX I supports the RLV12 controller as well.

Anyway, booting from an RL01/RL02 is not supported by the MicroVAX I boot ROM.

===Communication Options===

* [[DLV11-J asynchronous serial line interface|DLVJ1]]
* [[DZV11]]
* [[DHV11]]
* [[DHQ11]]
* [[DZQ11 asynchronous serial line interface|DZQ11]] not supported, but working!
* [[DEQNA]]
* [[DELQA]]

===Video Options===

* [[VCB01 Video Controller|VCB01]] Monochrome Video Subsystem


==Diagnostics==

MicroVAX I is the only MicroVAX model with "old-style" '''[[VAX Diagnostic Supervisor]]''' (VDS) diagnostics.

<PRE>
ATTACH ...
</PRE>

==Sample MicroVAX I Boot Messages (MicroVMS V4.6)==

These messages are taken from my 'real' MicroVAX I:

<PRE>
MICROVERIFY STARTED

MICROVERIFY PASSED

00000000 03

>>>B DUA0
ATTEMPTING BOOTSTRAP

MicroVMS Version V4.6 6-Jul-1987 17:00

PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 28-MAR-2022 8:28

The MicroVMS system is now executing the system startup procedure.

The MicroVMS system is now executing the site-specific startup commands.

%RUN-S-PROC_ID, identification of created process is 00000015
%RUN-S-PROC_ID, identification of created process is 00000017
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
SYSTEM job terminated at 28-MAR-2022 08:30:57.94

MicroVMS V4.6

Username: SYSTEM

Welcome to MicroVMS V4.6

Last interactive login on Saturday, 3-DEC-2022 17:59
Last non-interactive login on Monday, 3-JUN-2013 15:41

Main Menu

1 - Exit to DCL
2 - Log out of the SYSTEM account
3 - Invoke the MAIL utility
4 - Invoke the PHONE utility
5 - Add a user account to the system
6 - Install optional software
7 - Add or Delete a MicroVMS component
8 - Create or Modify an Autologin Terminal
9 - Back up or Restore the user files on a disk
10 - Build a Standalone BACKUP kit
11 - Set the maximum number of interactive logins
12 - Configure the network
13 - Shut down or start up the network
14 - SHUT DOWN the system

Enter a number (? or ?# for HELP): 1

If you wish to use the menus again, type the following:
$ @SYS$MANAGER:MGRMENU

$
</PRE>

==See also==

* [[Installing and Configuring MicroVMS V4.0 on a MicroVAX I]]

==References==

<div id="ref_1">[1] MicroVAX Handbook. EB-25156-47</div>
<div id="ref_2">[2] Systems & Options Catalog. European Edition. Spring 1990.</div>

==Further reading==

* ''MicroVAX Handbook'', 1984 (EB-25156-47) - extensive coverage of hardware and software

==External links==

* [http://www.bitsavers.org/pdf/dec/vax/610/ MicroVAX I] - documentation at [[Bitsavers]]
** [http://www.bitsavers.org/pdf/dec/vax/610/EK-VS200-TM-PRE_VAXstation_I_Technical_Reference_Manual_Preliminary_198411.pdf VAXstation I Technical Reference Manual] (EK-VS200-TM-PRE)
* [https://manx-docs.org/collections/hcps/kd32aomcn1.pdf MicroVAX I Owner's Manual Release Notes] (EK-KD32A-OM-CN1)
* [http://www.bitsavers.org/pdf/dec/vax/handbook/Supermicrosystems_Handbook_1986.pdf Supermicrosystems Handbook] - the MicroVAX I is covered on pp. 2-4–2-5 (pp. 19-20 of the PDF) and elsewhere
* [http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/hardware/micronotes/numerical/micronote22.txt Differences between the MicroVAX I and the MicroVAX II CPUs] ([[MicroNote]] #022)
* [https://ai.eecs.umich.edu/people/conway/VLSI/VLSIDesMag/Articles/MicroVAX-DataPath.VDec83.pdf The MicroVAX I Data-path Chip]

{{Nav VAX}}

[[Category: MicroVAX Systems]]
[[Category: QBUS VAX Systems]]

MicroVAX I

2025-11-17T08:41:30Z

Vaxorcist: /* Boot ROM Restrictions */ Corrections about Boot ROM Restrictions

{{InfoboxVAX-Data
| name = MicroVAX I
| Announcement = October 1983
| FRS-date = late 1984
| Codename = Seahorse
| OS-support-VMS = [[MicroVMS]] V1.0 to VMS V5.0-2
| OS-support-ULTRIX = ULTRIX/VAX V1.0 to ULTRIX/VAX V2.4?
| Enclosure = [[BA23 Enclosure|BA23]]
| CPU-module = [[KD32 CPU|KD32-AA]]
| Num-proc = 1
| Translation-buffer = 512 entries [[#ref_1|[1]]]
| Cache = 8KB
| Compatibility-mode = No
| Console-processor = CPU
| Console-device = None
| Minimum-memory = 512KB
| Maximum-memory = 4MB
| BUS-Qbus = 1 @ 3.3MB/s
| LAN-support = optional
| [[VUP]]s = 0.36
}}
The '''MicroVAX I''' was the first of a number of [[MicroVAX]] models from [[Digital Equipment Corporation|DEC]]. It used the [[QBUS]] as its primary [[bus]] between the [[Central Processing Unit|CPU]] (the [[KD32 CPU]]) and [[main memory]], the only [[VAX]] to do so. It was said to be the slowest VAX ever (about 0.25 [[VAX Unit of Performance|VUPs]]), even slower than the [[VAX-11/730]] resp. [[VAX-11/725]].

The two [[printed circuit board|boards]] of the MicroVAX I CPU communicate over the [[CD interconnect]] of the [[QBUS backplanes#Backplane types|H9278 backplane]], and an [[over the top]] [[flat cable]].

With a [[VCB01 Video Controller|VCB01]] Monochrome Video Subsystem added, the MicroVAX I becomes a [[VAXstation I]].

==Boot ROM==

===Boot ROM Restrictions===

The MicroVAX I bootstrap [[ROM]] can only bootstrap a system disk attached to the '''first''' [[Mass Storage Control Protocol]] (MSCP) controller.
It cannot boot from a [[TK50]] tape drive at all, and booting from an [[Ethernet]] network adapter like an [[DEQNA]] or [[DELQA]] is restricted, i.e. it cannot become member of an [[Local Area VAXcluster|LAVC]].

All these limitations do not apply to its successor, the [[MicroVAX II]].

See the instructions from:
[https://www.it-bcsb.de/download/MicroVMS%20Installation%20and%20Operation%20Guide%20-%20AA-KM46A-TN.pdf AA-KM46A-TN MicroVMS 4.6 Installation and Operations], Chapter C.1 Creating a Console Diskette:

The console diskette will contain files used to bootstrap from a disk attached to the
'''second''' MSCP controller. Use the following steps to create a console diskette. This
example assumes that the first RC25 disk attached to the second MSCP controller
(DABO:) will be the new system disk:

# Log in to the system manager's account, '''SYSTEM'''.
# Check the first diskette drive to ensure that it is empty and inactive; the red diskette activity light should not be glowing. If there is a diskette in the drive, remove it following the instructions in Section 3.1.11.
# Label a scratch diskette '''CONSOLE DISKETTE'''. A scratch diskette is a new diskette or a diskette containing no information that you want to save.
# Enter the following command to invoke the command procedure that creates a console diskette for a MicroVAX I system: <br>
: <PRE>$ @SYS$UPDATE:VMBUVAX1
: What system disk do you want to be able to boot from? DABO</PRE>
: Ignore the informational messages displayed on your terminal screen. The procedure prompts you for the name of the diskette drive on which the intermediate media (console diskette) will be mounted. In this example, the media is mounted in diskette drive 1 (DUA1).
: <PRE>Where will the intermediate RX50 media be mounted? DUA1</PRE>
: Insert the diskette labeled '''CONSOLE DISKETTE''' into drive 1 and enter '''YES''' in response to the following prompt:
: <PRE>Are you ready? YES</PRE>
: When it has finished building the console diskette, the system displays the following message: <br>
: <PRE>The media on DUA1 may now be used to boot device DABO</PRE>
After you create the console diskette, write-protect it to prevent anyone from accidentally overwriting the contents. To write-protect a diskette, cover the square notch in the upper-right comer of the diskette with a silver tab. Note that in order to bootstrap the system, the console diskette must be in diskette drive 1.

You may want to add the following command to the end of '''SYS$MANAGER:SYSTARTUP.COM''' to mount the console diskette automatically every time you bootstrap the system. This prevents other users from removing the diskette thinking that the drive is not in use.

<PRE>$ MOUNT/SYSTEM/FOREIGN $FLOPPY1 INTERMEDIATE</PRE>

----
'''NOTE'''

The command procedure '''SYS$UPDATE:VMBUVAX1.COM''' and other files needed might not be on the system disk depending on the option used when the system was installed.

You can install the missing components using:
<PRE>$ @SYS$UPDATE:VMSINSTAL UTIL $TAPE1:</PRE>
The tape (resp. tape image) AQ-FP13D-BN_MICROVMS_4.6_87 must be loaded (resp. attached to) the [[TK50]] tape drive beforehand.

Answer all questions with '''N''':
<PRE>* Do you want to install the entire kit: N
* Do you want to install the MAIL utility: N
* Do you want to install the SEARCH utility: N
* Do you want to install the DIFF utility: N
* Do you want to install the DUMP utility: N
* Do you want to install the RUNOFF utility: N
* Do you want to install the PHONE utility: N
* Do you want to install the MicroVMS HELP library: N
* Do you want to install the Remote terminal support via SET HOST/DTE: N
* Do you want to install the Foreign Terminal Support: N
* Do you want to install the LAT-11 terminal server support (via Ethernet): N
* Do you want to install the Stand-alone backup on system disk support: N</PRE>
except for:
<PRE>* Do you want to install the MicroVAX-I bootstrap that works for any MSCP system device: Y</PRE>

You should now be able to set up the special boot diskette for booting from a disk attached to the second MSCP controller.

===Supported Boot Devices===
* All [[RQDX Series of MFM Disk & Floppy QBUS Controllers|RQDX]] supported devices
* [[MRV11-D]]

===Boot ROM Characteristics===
* Microverify is the name given to the diagnostics executed by the MicroVAX I boot ROM. There are three LEDs on the DAP module and a seven segment display on the patch panel which will isolate the problem (if any) to one of the two CPU modules.
* Floating Point Instructions in Microcode
* No TOY Clock

==Options==

There are a lot of MicroVAX I Options; some of them are not "officially supported", but work nevertheless.

===Memory Options===

The MicroVAX I uses standard Q-bus memories which are not as fast but are also less expensive and usable by both the MicroVAX I and other 16-bit processors (such as the MicroPDP-11).
There are 22 address lines on the Q-bus, limiting maximum memory to 4 MB.

* [[MSV11-P]] Parity Memory
* [[MSV11-Q]] Parity Memory
* [[MSV11-M]] Parity Memory: not supported and not yet tested, but supposed to work
* [[MSV11-J]] PMI ECC Memory: not supported, but working! (-JD and -JE variants '''''only'''''; the -JB and -JC '''will not work''')
* [[MSV11-R]] PMI Parity Memory: not supported and not yet tested, but supposed to work

===Mass Storage Options===

* [[RQDX1/RQDX2 MFM Disk & Floppy QBUS Controllers|RQDX1]]
* [[RQDX1/RQDX2 MFM Disk & Floppy QBUS Controllers|RQDX2]]
* [[RQDX3 MFM Disk & Floppy QBUS Controller|RQDX3]]
* [[RX50]]
* [[RD51]]
* [[RD52]]
* [[RD53]]
* [[RD54]]
* [[RD31]]
* [[RD32]]
* [[RQC25]] RC25 Disk System with Qbus Controller, made of:
** [[M7740]]
** [[RC25]]

The [[SIMH]] MicroVAX I supports the [[RLV12]] controller for [[RL01/02 disk drive|RL01 and RL02]] removable disks.

It is currently unknown/untested whether the 'real' MicroVAX I supports the RLV12 controller as well.

Anyway, booting from an RL01/RL02 is not supported by the MicroVAX I boot ROM.

===Communication Options===

* [[DLV11-J asynchronous serial line interface|DLVJ1]]
* [[DZV11]]
* [[DHV11]]
* [[DHQ11]]
* [[DZQ11 asynchronous serial line interface|DZQ11]] not supported, but working!
* [[DEQNA]]
* [[DELQA]]

===Video Options===

* [[VCB01 Video Controller|VCB01]] Monochrome Video Subsystem


==Diagnostics==

MicroVAX I is the only MicroVAX model with "old-style" '''[[VAX Diagnostic Supervisor]]''' (VDS) diagnostics.

<PRE>
ATTACH ...
</PRE>

==Sample MicroVAX I Boot Messages (MicroVMS V4.6)==

These messages are taken from my 'real' MicroVAX I:

<PRE>
MICROVERIFY STARTED

MICROVERIFY PASSED

00000000 03

>>>B DUA0
ATTEMPTING BOOTSTRAP

MicroVMS Version V4.6 6-Jul-1987 17:00

PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 28-MAR-2022 8:28

The MicroVMS system is now executing the system startup procedure.

The MicroVMS system is now executing the site-specific startup commands.

%RUN-S-PROC_ID, identification of created process is 00000015
%RUN-S-PROC_ID, identification of created process is 00000017
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
SYSTEM job terminated at 28-MAR-2022 08:30:57.94

MicroVMS V4.6

Username: SYSTEM

Welcome to MicroVMS V4.6

Last interactive login on Saturday, 3-DEC-2022 17:59
Last non-interactive login on Monday, 3-JUN-2013 15:41

Main Menu

1 - Exit to DCL
2 - Log out of the SYSTEM account
3 - Invoke the MAIL utility
4 - Invoke the PHONE utility
5 - Add a user account to the system
6 - Install optional software
7 - Add or Delete a MicroVMS component
8 - Create or Modify an Autologin Terminal
9 - Back up or Restore the user files on a disk
10 - Build a Standalone BACKUP kit
11 - Set the maximum number of interactive logins
12 - Configure the network
13 - Shut down or start up the network
14 - SHUT DOWN the system

Enter a number (? or ?# for HELP): 1

If you wish to use the menus again, type the following:
$ @SYS$MANAGER:MGRMENU

$
</PRE>

==See also==

* [[Installing and Configuring MicroVMS V4.0 on a MicroVAX I]]

==References==

<div id="ref_1">[1] MicroVAX Handbook. EB-25156-47</div>
<div id="ref_2">[2] Systems & Options Catalog. European Edition. Spring 1990.</div>

==Further reading==

* ''MicroVAX Handbook'', 1984 (EB-25156-47) - extensive coverage of hardware and software

==External links==

* [http://www.bitsavers.org/pdf/dec/vax/610/ MicroVAX I] - documentation at [[Bitsavers]]
** [http://www.bitsavers.org/pdf/dec/vax/610/EK-VS200-TM-PRE_VAXstation_I_Technical_Reference_Manual_Preliminary_198411.pdf VAXstation I Technical Reference Manual] (EK-VS200-TM-PRE)
* [https://manx-docs.org/collections/hcps/kd32aomcn1.pdf MicroVAX I Owner's Manual Release Notes] (EK-KD32A-OM-CN1)
* [http://www.bitsavers.org/pdf/dec/vax/handbook/Supermicrosystems_Handbook_1986.pdf Supermicrosystems Handbook] - the MicroVAX I is covered on pp. 2-4–2-5 (pp. 19-20 of the PDF) and elsewhere
* [http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/hardware/micronotes/numerical/micronote22.txt Differences between the MicroVAX I and the MicroVAX II CPUs] ([[MicroNote]] #022)
* [https://ai.eecs.umich.edu/people/conway/VLSI/VLSIDesMag/Articles/MicroVAX-DataPath.VDec83.pdf The MicroVAX I Data-path Chip]

{{Nav VAX}}

[[Category: MicroVAX Systems]]
[[Category: QBUS VAX Systems]]

VAX Diagnostic Supervisor

2025-11-16T22:19:26Z

Vaxorcist: /* CPU-specific Supervisors */ Fixed typo

VDS - '''VAX Diagnostic Supervisor''' (sometimes abbreviated to VAX/DS) is a set of diagnostic software programs for the [[DEC]] [[VAX]] computers and peripheral devices.

== Intro ==

'''''"At best, a computer is as good as its diagnostic tools!"'''''

That's what they must have thought at DEC when they developed their diagnostic software.

Here we will take a closer look at the VAX Diagnostic Supervisor and also a quick side look at the [[User Environment Test Package]] (UETP).

== Using VDS for simulated VAX Computers ==

You may ask: "What are the VAX diagnostics good for when run on a simulated VAX?"

Yes, many diagnostics do not run on a simulated VAX, but some work very well and are used e.g. for testing the various [[SIMH]] VAX simulators for correct execution of the VAX native mode instructions.

Furthermore you can explore how precise the simulation mimics the real hardware.

If you plan to test your real VAX, you can familiarize yourself with VDS and prepare your diagnosis in SIMH, and SIMH can assist you in preparing and creating a diagnostic kit on media appropriate for your VAX.

Automated testing script for a SIMH VAX-11/750:

SET CLOCK NOCALIBRATE=600K
ATTACH -RQ RQ0 VAX_MINIMUM_DIAGS.dsk
EXPECT "DS> " SEND "ATTACH UDA50 DW0 DUA 772150 154 5 10\r"; GO -Q
EXPECT "DS> " SEND "ATTACH RA81 DUA DUA0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH KA750 CMI KA0 yes yes yes 0 0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH DW750 CMI DW0 8\r"; GO -Q
EXPECT "DS> " SEND "SET LOAD DUA0:[SYSMAINT]\r"; GO -Q
EXPECT "DS> " SEND "SELECT KA0\r"; GO -Q
EXPECT "DS> " SEND "SET FLAGS TRACE\r"; GO -Q
EXPECT "DS> " SEND "RUN EVKAB\r"; GO -Q
BOOT -Q RQ0 /R5:10

== VDS History ==

VDS development began in parallel that to the first [[VAX]] model, the [[VAX-11/780]] in 1977.

VDS was provided soley for the '''''"big VAXen"''''' (i.e. not for the [[MicroVAX]] and [[VAXstation]] computers), with one remarkable exception, the [[MicroVAX I]], resp. [[VAXstation I]].
Each new VAX model received its CPU-specific VDS modules up to the [[VAX 9000]]; only the VAX models of the last two series, [[VAX 7000]] and [[VAX 10000]], were covered by other diagnostic methods.

== Program Levels ==

All VAX diagnostic programs are assigned to a '''level'''. Levels are numbered 1, 2R, 2, 3, 4, and 5. A program’s level indicates its run-time environment.

* '''Level 1''' diagnostic programs run under an operating system. They do not use the VAX/DS. (=> UETP)
* '''Level 2R''' diagnostic programs run under VAX/DS in user mode only.
* '''Level 2''' diagnostic programs run in both user mode and standalone mode, under the control of the VAX/DS.
* '''Level 3''' diagnostic programs run only in standalone mode, under the control of the VAX/DS.
* '''Level 4''' diagnostic programs run in standalone without VAX/DS.
* '''level 5''' diagnostic programs run in [[Writable Control Store|WCS]] or system console, not in VAX main memory. They do not use the VAX/DS.

Only the levels 2R, 2, and 3 are managed by VDS.

== Sections, Tests, Subtests, and Flags ==

All diagnostic programs that run under the VAX/DS are composed of one or more '''sections'''. Each section has a name, and it is possible to specify, by name, which section of the program to execute. A program section can have one of two functions, depending on its design:

* Test a certain major portion of the unit under test.
* Facilitate a certain mode of testing. For example, there might be a quick-verify section, used to give the device a quick (but not thorough) test.

In order to determine the number and names of the sections in a particular diagnostic program, use the <code>SHOW SECTIONS</code> command. However, every program contains a default section called <code>DEFAULT</code>, which will execute automatically if you do not specifically select a section. A section is selected with the <code>/SECTION</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Each section is composed of a set of '''tests'''; each test verifies either a particular function of the hardware or a particular subset of the component logic being tested. The VAX/DS allows you to specify which tests within a section to run. Each test may have some '''subtests'''. Tests are selected with the <code>/TEST</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Two sets of '''flags''' are provided to control certain aspects of a diagnostic program’s execution. These flags may be set or cleared before the diagnostic program is started.

One set of flags is called the '''VAX/DS control flags'''. The flags in this set are interpreted by the VAX/DS and their meanings are the same in all diagnostic programs. The VAX/DS control flags are set with the <code>SET FLAGS</code> command.

The other set of flags is referred to as the '''event flags'''. This set consists of 23 flags whose purposes are defined by the diagnostic programs. The user must read the documentation for specific diagnostic programs to determine if a definition has been assigned to any of the event flags. <code>SET EVENT FLAGS</code> command.

== Some useful VDS commands ==

* <code>'''SET LOAD disk:[directory]'''</code> Set diagnostic load path
* <code>'''LOAD''' Exxxx</code> Load diagnostic Exxxx (where "Exxxx" is replaced by the diagnostics name, e.g. EVKAA)
* <code>'''SET TRACE'''</code> Show progress
* <code>'''SHOW FLAGS'''</code> Show VDS flags
* <code>'''SHOW TESTS'''</code> Show the available tests of the loaded diagnostic
* <code>'''SHOW SECTIONS'''</code> Show the available sections of the loaded diagnostic
* <code>'''START/TEST='''first:last</code> Start a subset of the loaded diagnostics tests (where "first" is the test number to start with, and -optionally- "last" is the last one to execute)
* <code>'''START/SECTION='''section-name</code> Start a single section of the loaded diagnostic (where "section-name" is the name of the section to run)
* <code>'''START/PASSES='''count</code> Start the loaded diagnostic for "count" passes (where "count" is the number of passes to execute)
* <code>'''RUN''' exxxx'''/TEST='''first:last</code> Run a subset of the diagnostics tests; if "last" is not given, all tests from start up the the last one are run, to run a single test, enter "=n:n", where "n" is the test number
* <code>'''RUN''' exxxx'''/SECTION='''section-name</code> Run a single section of the diagnostic
* <code>'''RUN''' exxxx'''/PASSES='''count</code> Run the diagnostic for "count" passes

Use a pass count of 0 to run a program continuously. If you do this, the program will run until you type CTRL/C or a failure occurs with the HALT flag set.

== Diagnostic Program Documentation ==

Documentation provided for each diagnostic program includes:

* '''Help file'''
:: The help file is referenced with the HELP command. It contains any operating instructions that may be unique to the diagnostic program. The help file for diagnostic program EVXYZ is EVXYZ.HLP; the help file for the VAX/DS is EVSAA.HLP

* '''Documentation file'''
:: The documentation file provides a detailed description of a diagnostic program's function, run-time requirements, operating instructions, fault detection, and maintenance history, plus explanations of each test’s function and execution flow. The documentation file for diagnostic program EVXYZ is EVXYZ.DOC.

* '''Source Code listings'''
:: Source code listings of the diagnostic programs are available. All VAX/DS diagnostic programs are structured in a standard format. For example, the initialization code for every diagnostic program is always located in the same relative area within the listing. To fully understand the source code listings of a VAX/DS diagnostic program, refer to the VAX Diagnostic Design Guide.

The help file for a diagnostic program is shipped with the diagnostic program. The documentation file and source codelistings are available by ordering a [[Maintenance Documentation Service]] Option on microfiche.

== Diagnostic Scopes ==

There are two diagnostic scopes.

* A CPU-specific scope: '''CPU Cluster Testing'''
* A scope for the identical diagnostic programs for all types of VAX computers: '''Peripheral Diagnostics'''

=== CPU Cluster Testing ===

'''NOTE: The term "CPU cluster" used here means all components belonging to a CPU; there is no connection with the term [[VAXcluster|"VAXcluster" (alternatively: "VMScluster")]].'''

The VAX CPU cluster is tested by a set of programs, existing at several program levels, as follows:

* Level 5
** Console tests
** Processor tests
** Memory tests
* Level 4
** VAX instruction set test (hardcore for VDS)
** Cache and translation buffer tests (VAX-11/750 only)
* Level 3
** Memory tests (if no level 5 test possible)
** Channel adapter tests
** Cluster exerciser

'''NOTE: The term "Channel adapter" used here means bus adapter, e.g. for [[UNIBUS]] or [[MASSBUS]].'''

This set of programs implements the VAX diagnostic strategy by providing a set of building blocks by which a system may be tested, starting with the level 5 basic processor tests and ending with the level 3 cluster exerciser, which is a program meant to exercise all components of the cluster.

=== Peripheral Diagnostics ===

Thorough testing of a peripheral device requires the development of three different diagnostic programs. For each device type the following will typically (but not necessarily) exist:

* A level 3 logic test
* A level 3 function test
* A level 2R function test

This group of programs implements the diagnostic strategy by providing a facility for producing very accurate and detailed identifications of fault conditions via the level 3 programs and by also providing a method by which the device may be tested without bringing down the customer's operating system via the level 2R program.

The level 3 logic test will provide the greatest detail of error resolution, indicating which section of logic is failing. This program will be used by technicians to repair bad logic boards, and will provide very high test coverage. Some devices contain ROM-resident microprograms ("self-tests") that perform logic testing, making a level 3 logic test unnecessary.

The level 3 function test will provide a comprehensive test of all of the device’s functions. This program will be used to determine accurately whether or not a device is operating correctly. This is the definitive function test and provides very high test coverage. Level 3 function tests are usually required even if the device possesses self-testing capabilities, because self-tests generally are not capable of complete detection of function failures.

The level 2R program will typically consist of a subset of the level 3 function test. It will test as much of the device’s functionality as can be tested in the user (VMS) environment. The tests it contains are exact or approximate copies of tests existing in the level 3 program.

A typical sequence of use for these programs, when dealing with a system at a customer site, is as follows:

# The customer (or field service) suspects a fault existing in the device.
# The level 2R program is run to see if the error can be detected without stopping the operating system. If the error is found, go to step 4.
# If the level 2R program cannot identify the fault, the operating system is brought down and the level 3 function test is run.
# The fault is identified and the failing [[Field Replacable Unit|FRU]] is replaced. The operating system is then brought back up.
# The failing FRU is brought back to DIGITAL, where the level 3 logic test, the level 3 function test, or perhaps a module test station is used to identify the failing logic on the FRU. The FRU is repaired.

== VAX Diagnostic Coding Convention ==

VAX diagnostic program names consist of 5 letters and a two-digit version number, e.g.: ECKAL-3.4:

* E = VAX
* C = 11/750
* K = CPU
* A = Supervisor
* L = Unique identifier
* 3 = Major revision
* 4 = Minor Revision

See the following 1986 VAX Diagnostic Coding Convention Table for letter breakdown:

EPXYD-R.P

E = System

E = VAX

P = Processor

B = VAX 8200/8300
D = VAX 8600
S = VAX 11780
T = VAX 11785
C = VAX 11750
N = VAX 11730 and 11725
H = MicroVAX I
J = VAX 8820/8830/8840
V = More than one VAX Processor
X = VAX 6000
Z = VAX 8530/8550/8700/8800

X = Device Category

A = Application (CR, LP, A-D, Misc.)
C = Channel Adaptors (MBA, UBA)
D = Communication Devices (DMC, DZ11)
G = CI Adapter
K = CPU
L = Database Files
M = Magnetic Tape (TE, TU, DT)
P = Test Equipment
Q = QIO Device Driver
R = Rotating Memory (RP, RK, RM, RS, RX)
S = System Monitor (Supervisor, Tape Monitor)
T = Terminal (LA36, VT52)
U = Utilities (Script file, Copy, Update)
W = Workstations
X = System Exerciser (EXR/BUSINT)
Z = Media Packages
0-9 = Engineering File

Y = Device Type

Category Application
A = Line Printers, LP, LCP01
B = Card Readers, CR
L = LPA11-K
Category Channel
A = MBA
B = UBA, DWBUA
C = MA780
D = IEC11, IEU11-A, DR70
E = DT07
F = DEC DATAWAY
G = CI780
H = CI750/CI780 MICROCODE VERIFICATION (INTERNAL)
I = TEST BED ADAPTERS
J = NBI ADAPTER
K = CIBCI

Category Communications
A = DZ11,DZ32,DMZ32,DHU11,DMB32
B = DMC
C = Multiple Devices
D = DR11-C
E = DV11
F = DR780,DF11-W
G = DQS11
H = KMC11-B
I = KMS11-B
J = DM11-BA
K = DMS11-BA
L = DMF32 Combo
M = DMC11,DMR11,DMP11
N = DN11
O = CPI32
P = PCL11
R = DR11B,DR11-W,DRE11
S = DRS11/DSS
T = KCT32-A,FEPCM
U = DUP11
X = Multiple Devices
W = UNA
Y = DEBNT

Category Database Files
A = CRD DATABASE FILES
B = SYSTEM EXERCISER DATABASE FILES

Category Magnetic Tape
A = TE16/77, TS11, TU78, TS05
B = TU81,TU80

Category QIO Device Drivers
For this category, the fourth and fifth letters of the code are the device mnemonic.
For example, EVQDB is the QIO device driver for the DB, or RP disk series.

Category Test Equipment
A = CI780 Node Tester
B = NI Tester

Category Rotating Memory
A = Multiple devices
B = RP04/5/6
C = DCL/RP04/5/6
D = RM03/RM05/RM80
E = RK611,RK06,RK07
F = RL02
G = RM80
H = RP07
I = RX02
J = ML11
K = IDC
L = UDA50(RA60,RA80,RA81)
M = RC25
N = RUX50

Category System Monitor
A = Supervisor
B = Autosizer
C = DYDDM

Category Terminals
A = All Terminals
B = Terminal exerciser
C = VS11
D = 11C03-LH Fastek
G = VS70

Category Utility
A = Script File
B = Copy Command file
C = Updating file

Category Workstation
A = VS100

Category Exerciser
B = Exerciser Bus Interaction

D = Fifth character makes the code unique. A through Z and 1 through 9.

R = Revision (MAJOR)
P = Revision (MINOR)

== Distribution of Diagnostic Programs ==

Typically, a VAX computer came with all the necessary diagnostic programs on console media at no additional charge, e.g.:

* VAX-11/780: [[RX01/02 floppy drive|RX01 floppies]]
* VAX-11/750, VAX-11/730, and VAX-11/725: [[TU58 DECtape II|TU58 cartridges]]
* VAX 8600: [[RL01/02 disk drive|RL02 disk pack]]
* VAX 8200, VAX 8250, VAX 8300, and VAX 8350: [[RX50 dual-diskette drive|RX50 floppies]]

Additionally, you could buy larger collections of diagnostic programs on [[magnetic tape]] or [[Removable-pack disk|removable disk packs]].

Extended documentation was available on microfiche at an extra charge.

== VMS User Enviroment Test Package (UETP) ==

From the very beginning of VMS V1.0 there was the '''[[User Enviroment Test Package]]''' (UETP), see: [http://bitsavers.trailing-edge.com/pdf/dec/vax/vms/2.0/AA-D643B-TE_VAX-VMS_2.0_UETP_Users_Guide_198003.pdf VAX/VMS UETP User’s Guide AA-D643A-TE]

Quote from the first UETP manual:

"''The UETP is a collection of tests designed to demonstrate that the hardware and software components of a VAX/VMS system are in working order. DIGITAL software support representatives run the UETP on a newly installed VAX/VMS system as the formal sample procedure.''"

UETP is still used in the latest version of VMS (V9.2-2 for x86 as of this writing).

[https://docs.vmssoftware.com/vsi-openvms-system-manager-s-manual-volume-2-tuning-monitoring-and-complex-systems/#_6017UETP| See here] for the latest VMS UETP manual.

== ULTRIX System Exerciser Package ==

[[ULTRIX]] has got a very similar tool to verify proper hardware operation at the operating system level, the '''[[System Exerciser Package]]'''.

For the earliest reference found so far see the manual: [https://drive.google.com/file/d/1i3LoLAvTQC7dZl-T9X3SsQgg_6s_6TCY/view?usp=sharing ULTRIX-32 2.2 System Exercisers 1987 AA-KS95A-TE]

The MIPS variants of ULTRIX include the System Exerciser Package, too.

== Additional Diagnostic Tools ==

* On-board ROM-based diagnostics (RBDs) / Self-tests
* [[Diagnostic and Utility Protocol|DUP]] for [[Mass Storage Control Protocol|MSCP]] devices

== CPU-specific Supervisors ==

* '''EBSAA''' VAX 8200/8250/8300/8350 & VS8000 Diagnostic Supervisor
* '''ECSAA''' VAX-11/750 DIAGNOSTIC SUPERVISOR
* '''EDSAA''' VAX 8600/8650 Diagnostic Supervisor
* '''EHSAA''' MicroVAX I VDS
* '''EJSAA''' VAX 8820/8830/8840 Diagnostic Supervisor
* '''ELSAA''' VAX 6210/6220/6230/6240/6310/6320/6330/6340/6350/6360 Diagnostic Supervisor
* '''ENSAA''' VAX 725/730 Diagnostic Supervisor
* '''ESSAA''' VAX 780/785 Diagnostic Supervisor
* '''EXSAA''' VAX 6000 Diagnostic Supervisor
* '''EZSAA''' VAX 8530/8550/8700/8800/8820N Diagnostic Supervisor
* '''E?SAA''' VAX 9000 Diagnostic Supervisor

There is no supervisor for the series of VAX 7000 / VAX 10000 computers (see: [http://www.vaxhaven.com/images/4/4d/EK-7001A-TS-001.pdf VAX 7000 Advanced Troubleshooting EK-7001A-TS-001])

== Set of Diagnostics for a SV-BXTAA VAX-11/750 System ==

A SV-BXTAA VAX-11/750 System consists of:

* [[KA750 CPU|VAX-11/750 CPU]]
* [[MS750 Memory System|MS750 1MB memory]]
* [[DECwriter IV|LA38 printing console terminal]]
* [[RH750 Massbus Adapter]]
* [[RM02/03 disk drive|RM03 MASSBUS disk drive subsystem]]
* [[DZ11 asynchronous serial line interface|DZ11 terminal adapter]]
* [[TS11 Subsystem|TS11 magnetic tape unit]]

The diagnostics set for this system is made of:

* CPU-specific diagnostic main program
** '''ECSAA''' VAX 11750 DIAG SUPERVISOR

* VAX-common automatic sizing program which automatically determines the current system configuration
** '''EVSBA''' VAX AUTOSIZER DIAGNOSTIC

* Set of VAX-11/750 CPU diagnostics
** '''ECKAA''' VAX 11750 UDIAG MON
** '''ECKAB''' VAX 11750 MICRO DPM
** '''ECKAC''' VAX 11750 MICRO MIC
** '''ECKAD''' VAX FP750 MICRODIAG
** '''ECKAF''' VAX KC750 UDIAG
** '''ECKAL''' VAX 11750 CACHE/TB DIAG
** '''ECKAM''' VAX 11750 MEMORY DIAG
** '''ECKAX''' VAX 11750 CLUSTER EXER

* VAX-common instruction set diagnostic
** '''EVKAA''' VAX INSTRUCTION SET TEST

* VAX-11/750 bus diagnostics
** '''ECCAA''' VAX 11750 RH750 DIAG
** '''ECCBA''' VAX 11750 UBI/DW750 DIAG

* Set of VAX-common peripheral diagnostics
** '''EVTAA''' VAX TERMINAL DIAGNOSTIC
** '''EVTBA''' VAX TERMINAL EXERCISER
** '''EVDAA''' VAX DZ11 8 LINE ASYNC MUX
** '''EVMAA''' VAX TM03/TE16/TU45-77 Tape
** '''EVRDA''' VAX RM03/RM05/RM80 DISKLESS
** '''EVRDB''' VAX RM03/RM05 FUNCTIONAL TEST

== Booting the VAX Diagnostic Supervisor ==

The command to boot the VAX Diagnostic Supervisor on a SIMH VAX is:

BOOT RQ0 /R5:10

* <code>RQ0</code> is the device identifier for the MSCP disk, unit 0, where the diagnostics are stored; adjust this according to your requirements.
* <code>/R5:10</code> is the boot flag to boot the Diagnostic Supervisor located in directory <code>DUA0:[SYSMAINT]</code> or <code>DUA0:[SYS0.SYSMAINT]</code>.

For booting the VAX Diagnostic Supervisor on a real VAX refer chapter 2.1 of the "'''VAX DS Diagnostic Supervisor User's Guide'''" [[#ref_1|[1]]]

== Sample run of the VDS EVSBA AUTOSIZER ==

DS> '''LOAD EVSBA.EXE'''
DS> '''SET FLAGS QUICK'''
DS> '''START /SECTION:MANUAL'''

.. Program: EVSBA - AUTOSIZER LEVEL 3, revision 5.1, 3 tests,
at 18:18:28.19.

COMMAND? '''HELP'''

HELP

This is a manual section command. This program creates ATTACH
commands for all devices in the system.
(ATTACH,CHANGE,EXIT,HELP,LIST,READ,SIZE,WRITE) - These commands
control the sizer in manual and selftest mode.
To obtain further information type HELP followed by a topic.
For example;
HELP MANUAL

Additional information available:

ATTACH CHANGE DEFAULT DEVICE EVENT
EXIT HELP LIST MANUAL QUICK
READ SECTION SELFTEST SCRIPT SIZE
SUMMARY WRITE

COMMAND? '''SIZE'''
COMMAND? '''LIST'''
FILE IN MEMORY 'CONFIG.COM'
!! AUTOMATIC SIZING PROGRAM.
!! THIS IS A TOOL AND NOT A DIAGNOSTIC PROGRAM.
!! CONFIGURATION FILE FOR SYSTEM.
!! COMPUTER GENERATED CPU TYPE 2 MICROCODE REV LEVEL = 99
!! NUMERIC VALUES WITH A LEADING ZERO ARE ASSIGNED.
!! FILE VALID ONLY FOR STANDARD HARDWARE CONFIGURATION.
!! TIME IS 15-FEB-1984 18:18:56.85
!!
!! *** QUICK FLAG SET. NO CHECKS MADE FOR TERMINALS ON DZ11/DZ32'S ***
!!
!!
!! DEFINE PROCESSOR...
!!
DS> ATTACH KA750 HUB KA0 YES YES YES 027FF 0
!!
!! DEFINE MEMORY...
!!
DS> ATTACH MS750 MS0
!!
!! DEFINE UNIBUS ADAPTERS...
!!
DS> ATTACH DW750 HUB DW0
!!
DS> ATTACH LP11 DW0 LPA 777514 0200 04
DS> ATTACH LP25 LPA LPA0 !! *** PRINTER TYPE IS ESTIMATED ***
DS> ATTACH TS11 DW0 MSA0 772520 0224 05
DS> ATTACH UDA50 DW0 DUA 772150 0154 05 02
DS> ATTACH RA81 DUA DUA0
DS> ATTACH RA60 DUA DJA2
DS> ATTACH RX50 DUA DUA3
DS> ATTACH DZ11 DW0 TTA 760100 0300 05 EIA
DS> ATTACH DZ11 DW0 TTB 760110 0310 05 EIA
DS> ATTACH DZ11 DW0 TTC 760120 0320 05 EIA
DS> ATTACH DZ11 DW0 TTD 760130 0330 05 EIA
COMMAND? '''WRITE'''
CONFIGURATION FILE IS NORMALLY READ/WRITTEN TO THE SUPERVISOR CONSOLE MEDIA
VERIFY SUPERVISOR CONSOLE MEDIA LOADED.
VERIFIED? [(Yes), No] '''YES'''
COMMAND? '''EXIT'''
DS>

== See also ==

* [[Running VDS Diagnostics on the SIMH VAX-11/750]]

== External links ==

This page contains condensed information from several DEC manuals, among others:

* [http://bitsavers.org/pdf/dec/vax/diag/EP-EVNDX-25.0_Oct86.txt EVNDX25 VAX DIAGNOSTIC INDEX]
* [https://vt100.net/mirror/hcps/si75fin1.pdf EK-SI75F-IN-001 VAX-11-750 Installation Manual] pdf-page 60ff
* <div id="ref_1">[1] [http://bitsavers.org/pdf/dec/vax/diag/VAX_Diagnostic_Supervisor_Users_Guide_Apr89.pdf AA-FK66A-TE VAX DS Diagnostic Supervisor User's Guide] </div>
* [http://bitsavers.org/pdf/dec/vax/diag/EK-1VAXD-TM-001_VAX_Diagnostic_Design_Guide_Aug79.pdf EK-1VAXD-TM-003 VAX Diagnostic Design Guide]
* [http://bitsavers.org/pdf/dec/vax/diag/AA-FK67A-TE_VAX_Diagnostic_Design_Guide_Apr89.pdf AA-FK67A-TE VAX Diagnostic Design Guide]
* [http://www.bitsavers.org/pdf/dec/vax/vms/1.5/2b/AA-D643A-TE_VAX_VMS_UETP_Users_Guide_Aug78.pdf AA-D643A-TE VAX/VMS UETP User’s Guide]
* [http://www.trailing-edge.com/~shoppa/11780diags/ VAX-11/780 Diagnostic Help Files]
* [https://manx-docs.org/collections/antonio/dec/MDS-2000-01/cd1/VAX/7001ATS1.PDF EK-7001A-TS-001 VAX 7000 Advanced Troubleshooting]

[[Category: VAX]]
[[Category: VAX Software]]
[[Category: VAX Diagnostic Software]]
[[Category: SIMH Tutorials]]
[[Category: VMS Practical Guides]]

MicroVAX I

2025-11-16T22:15:32Z

Vaxorcist: "See also" added

{{InfoboxVAX-Data
| name = MicroVAX I
| Announcement = October 1983
| FRS-date = late 1984
| Codename = Seahorse
| OS-support-VMS = [[MicroVMS]] V1.0 to VMS V5.0-2
| OS-support-ULTRIX = ULTRIX/VAX V1.0 to ULTRIX/VAX V2.4?
| Enclosure = [[BA23 Enclosure|BA23]]
| CPU-module = [[KD32 CPU|KD32-AA]]
| Num-proc = 1
| Translation-buffer = 512 entries [[#ref_1|[1]]]
| Cache = 8KB
| Compatibility-mode = No
| Console-processor = CPU
| Console-device = None
| Minimum-memory = 512KB
| Maximum-memory = 4MB
| BUS-Qbus = 1 @ 3.3MB/s
| LAN-support = optional
| [[VUP]]s = 0.36
}}
The '''MicroVAX I''' was the first of a number of [[MicroVAX]] models from [[Digital Equipment Corporation|DEC]]. It used the [[QBUS]] as its primary [[bus]] between the [[Central Processing Unit|CPU]] (the [[KD32 CPU]]) and [[main memory]], the only [[VAX]] to do so. It was said to be the slowest VAX ever (about 0.25 [[VAX Unit of Performance|VUPs]]), even slower than the [[VAX-11/730]] resp. [[VAX-11/725]].

The two [[printed circuit board|boards]] of the MicroVAX I CPU communicate over the [[CD interconnect]] of the [[QBUS backplanes#Backplane types|H9278 backplane]], and an [[over the top]] [[flat cable]].

With a [[VCB01 Video Controller|VCB01]] Monochrome Video Subsystem added, the MicroVAX I becomes a [[VAXstation I]].

==Boot ROM==

===Boot ROM Restrictions===

The MicroVAX I bootstrap [[ROM]] can only bootstrap a system disk attached to the '''first''' [[Mass Storage Control Protocol]] (MSCP) controller.
It can neither boot from a [[TK50]] tape drive nor from an [[Ethernet]] network adapter like an [[DEQNA]] or [[DELQA]].

Since the MicroVAX I cannot boot from the network, it cannot become member of an [[Local Area VAXcluster|LAVC]].

All these limitations do not apply to its successor, the [[MicroVAX II]].

See the instructions from:
[https://www.it-bcsb.de/download/MicroVMS%20Installation%20and%20Operation%20Guide%20-%20AA-KM46A-TN.pdf AA-KM46A-TN MicroVMS 4.6 Installation and Operations], Chapter C.1 Creating a Console Diskette:

The console diskette will contain files used to bootstrap from a disk attached to the
'''second''' MSCP controller. Use the following steps to create a console diskette. This
example assumes that the first RC25 disk attached to the second MSCP controller
(DABO:) will be the new system disk:

# Log in to the system manager's account, '''SYSTEM'''.
# Check the first diskette drive to ensure that it is empty and inactive; the red diskette activity light should not be glowing. If there is a diskette in the drive, remove it following the instructions in Section 3.1.11.
# Label a scratch diskette '''CONSOLE DISKETTE'''. A scratch diskette is a new diskette or a diskette containing no information that you want to save.
# Enter the following command to invoke the command procedure that creates a console diskette for a MicroVAX I system: <br>
: <PRE>$ @SYS$UPDATE:VMBUVAX1
: What system disk do you want to be able to boot from? DABO</PRE>
: Ignore the informational messages displayed on your terminal screen. The procedure prompts you for the name of the diskette drive on which the intermediate media (console diskette) will be mounted. In this example, the media is mounted in diskette drive 1 (DUA1).
: <PRE>Where will the intermediate RX50 media be mounted? DUA1</PRE>
: Insert the diskette labeled '''CONSOLE DISKETTE''' into drive 1 and enter '''YES''' in response to the following prompt:
: <PRE>Are you ready? YES</PRE>
: When it has finished building the console diskette, the system displays the following message: <br>
: <PRE>The media on DUA1 may now be used to boot device DABO</PRE>
After you create the console diskette, write-protect it to prevent anyone from accidentally overwriting the contents. To write-protect a diskette, cover the square notch in the upper-right comer of the diskette with a silver tab. Note that in order to bootstrap the system, the console diskette must be in diskette drive 1.

You may want to add the following command to the end of '''SYS$MANAGER:SYSTARTUP.COM''' to mount the console diskette automatically every time you bootstrap the system. This prevents other users from removing the diskette thinking that the drive is not in use.

<PRE>$ MOUNT/SYSTEM/FOREIGN $FLOPPY1 INTERMEDIATE</PRE>

----
'''NOTE'''

The command procedure '''SYS$UPDATE:VMBUVAX1.COM''' and other files needed might not be on the system disk depending on the option used when the system was installed.

You can install the missing components using:
<PRE>$ @SYS$UPDATE:VMSINSTAL UTIL $TAPE1:</PRE>
The tape (resp. tape image) AQ-FP13D-BN_MICROVMS_4.6_87 must be loaded (resp. attached to) the [[TK50]] tape drive beforehand.

Answer all questions with '''N''':
<PRE>* Do you want to install the entire kit: N
* Do you want to install the MAIL utility: N
* Do you want to install the SEARCH utility: N
* Do you want to install the DIFF utility: N
* Do you want to install the DUMP utility: N
* Do you want to install the RUNOFF utility: N
* Do you want to install the PHONE utility: N
* Do you want to install the MicroVMS HELP library: N
* Do you want to install the Remote terminal support via SET HOST/DTE: N
* Do you want to install the Foreign Terminal Support: N
* Do you want to install the LAT-11 terminal server support (via Ethernet): N
* Do you want to install the Stand-alone backup on system disk support: N</PRE>
except for:
<PRE>* Do you want to install the MicroVAX-I bootstrap that works for any MSCP system device: Y</PRE>

You should now be able to set up the special boot diskette for booting from a disk attached to the second MSCP controller.

===Supported Boot Devices===
* All [[RQDX Series of MFM Disk & Floppy QBUS Controllers|RQDX]] supported devices
* [[MRV11-D]]

===Boot ROM Characteristics===
* Microverify is the name given to the diagnostics executed by the MicroVAX I boot ROM. There are three LEDs on the DAP module and a seven segment display on the patch panel which will isolate the problem (if any) to one of the two CPU modules.
* Floating Point Instructions in Microcode
* No TOY Clock

==Options==

There are a lot of MicroVAX I Options; some of them are not "officially supported", but work nevertheless.

===Memory Options===

The MicroVAX I uses standard Q-bus memories which are not as fast but are also less expensive and usable by both the MicroVAX I and other 16-bit processors (such as the MicroPDP-11).
There are 22 address lines on the Q-bus, limiting maximum memory to 4 MB.

* [[MSV11-P]] Parity Memory
* [[MSV11-Q]] Parity Memory
* [[MSV11-M]] Parity Memory: not supported and not yet tested, but supposed to work
* [[MSV11-J]] PMI ECC Memory: not supported, but working! (-JD and -JE variants '''''only'''''; the -JB and -JC '''will not work''')
* [[MSV11-R]] PMI Parity Memory: not supported and not yet tested, but supposed to work

===Mass Storage Options===

* [[RQDX1/RQDX2 MFM Disk & Floppy QBUS Controllers|RQDX1]]
* [[RQDX1/RQDX2 MFM Disk & Floppy QBUS Controllers|RQDX2]]
* [[RQDX3 MFM Disk & Floppy QBUS Controller|RQDX3]]
* [[RX50]]
* [[RD51]]
* [[RD52]]
* [[RD53]]
* [[RD54]]
* [[RD31]]
* [[RD32]]
* [[RQC25]] RC25 Disk System with Qbus Controller, made of:
** [[M7740]]
** [[RC25]]

The [[SIMH]] MicroVAX I supports the [[RLV12]] controller for [[RL01/02 disk drive|RL01 and RL02]] removable disks.

It is currently unknown/untested whether the 'real' MicroVAX I supports the RLV12 controller as well.

Anyway, booting from an RL01/RL02 is not supported by the MicroVAX I boot ROM.

===Communication Options===

* [[DLV11-J asynchronous serial line interface|DLVJ1]]
* [[DZV11]]
* [[DHV11]]
* [[DHQ11]]
* [[DZQ11 asynchronous serial line interface|DZQ11]] not supported, but working!
* [[DEQNA]]
* [[DELQA]]

===Video Options===

* [[VCB01 Video Controller|VCB01]] Monochrome Video Subsystem


==Diagnostics==

MicroVAX I is the only MicroVAX model with "old-style" '''[[VAX Diagnostic Supervisor]]''' (VDS) diagnostics.

<PRE>
ATTACH ...
</PRE>

==Sample MicroVAX I Boot Messages (MicroVMS V4.6)==

These messages are taken from my 'real' MicroVAX I:

<PRE>
MICROVERIFY STARTED

MICROVERIFY PASSED

00000000 03

>>>B DUA0
ATTEMPTING BOOTSTRAP

MicroVMS Version V4.6 6-Jul-1987 17:00

PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 28-MAR-2022 8:28

The MicroVMS system is now executing the system startup procedure.

The MicroVMS system is now executing the site-specific startup commands.

%RUN-S-PROC_ID, identification of created process is 00000015
%RUN-S-PROC_ID, identification of created process is 00000017
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
SYSTEM job terminated at 28-MAR-2022 08:30:57.94

MicroVMS V4.6

Username: SYSTEM

Welcome to MicroVMS V4.6

Last interactive login on Saturday, 3-DEC-2022 17:59
Last non-interactive login on Monday, 3-JUN-2013 15:41

Main Menu

1 - Exit to DCL
2 - Log out of the SYSTEM account
3 - Invoke the MAIL utility
4 - Invoke the PHONE utility
5 - Add a user account to the system
6 - Install optional software
7 - Add or Delete a MicroVMS component
8 - Create or Modify an Autologin Terminal
9 - Back up or Restore the user files on a disk
10 - Build a Standalone BACKUP kit
11 - Set the maximum number of interactive logins
12 - Configure the network
13 - Shut down or start up the network
14 - SHUT DOWN the system

Enter a number (? or ?# for HELP): 1

If you wish to use the menus again, type the following:
$ @SYS$MANAGER:MGRMENU

$
</PRE>

==See also==

* [[Installing and Configuring MicroVMS V4.0 on a MicroVAX I]]

==References==

<div id="ref_1">[1] MicroVAX Handbook. EB-25156-47</div>
<div id="ref_2">[2] Systems & Options Catalog. European Edition. Spring 1990.</div>

==Further reading==

* ''MicroVAX Handbook'', 1984 (EB-25156-47) - extensive coverage of hardware and software

==External links==

* [http://www.bitsavers.org/pdf/dec/vax/610/ MicroVAX I] - documentation at [[Bitsavers]]
** [http://www.bitsavers.org/pdf/dec/vax/610/EK-VS200-TM-PRE_VAXstation_I_Technical_Reference_Manual_Preliminary_198411.pdf VAXstation I Technical Reference Manual] (EK-VS200-TM-PRE)
* [https://manx-docs.org/collections/hcps/kd32aomcn1.pdf MicroVAX I Owner's Manual Release Notes] (EK-KD32A-OM-CN1)
* [http://www.bitsavers.org/pdf/dec/vax/handbook/Supermicrosystems_Handbook_1986.pdf Supermicrosystems Handbook] - the MicroVAX I is covered on pp. 2-4–2-5 (pp. 19-20 of the PDF) and elsewhere
* [http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/hardware/micronotes/numerical/micronote22.txt Differences between the MicroVAX I and the MicroVAX II CPUs] ([[MicroNote]] #022)
* [https://ai.eecs.umich.edu/people/conway/VLSI/VLSIDesMag/Articles/MicroVAX-DataPath.VDec83.pdf The MicroVAX I Data-path Chip]

{{Nav VAX}}

[[Category: MicroVAX Systems]]
[[Category: QBUS VAX Systems]]

Installing and Configuring MicroVMS V4.0 on a MicroVAX I

2025-11-16T15:48:51Z

Vaxorcist: /* Boot MicroVMS V4.0 Standalone Backup */ Revised instructions

The aim of this tutorial is to show how to install [[MicroVMS]] V4.0 on the [[SIMH]] [[DEC]] [[MicroVAX I]] [[simulator]].

If you are a lucky owner of a real MicroVAX I, you can use the following instructions as well. All you've got to do additionally is write the floppy images to [[RX50]] compatible floppies, see: [[Writing Floppy/Fixed Disk and Tape Images to Real Media using VMS]].

MicroVMS V4.0 and the MicroVAX I computer were the very beginning of the success story of the DEC series of [[MicroVAX]] computers in 1984.

A MicroVAX I as it is used in this tutorial cost in 1984:
16,985$ for the base computer
4,000$ for the additional 1MB memory,
900$ for the four serial lines
1,150$ for the network adapter
1,500$ for the MicroVMS Full System license
===============
24,535$ Total

== Preparations ==

Get the MicroVMS V4.0 installation floppy images from [http://bitsavers.org/bits/DEC/vax/vms/RX50/MicroVMS_4.0_RX50_Distkit.tgz here], unpack and use the <code>.dsk</code> files from the <code>dsk_files</code> directory.

Get some additional floppy images (DECnet MicroVMS V4.0) from [tbd].

I will use shortened floppy file names (cut down to the media ID) for brevity, e.g. <code>BL-B012B-BE.dsk</code> instead of <code>BL-B012B-BE MicroVMS V4.0 BIN RX50 SABACKUP 1of2.dsk</code>

=== SIMH microvax1 simulator ===

You can use the microvax1 simulator from [https://github.com/simh/simh simh] or from [https://github.com/open-simh/simh open-simh], as both are working by now.

=== microvax1.ini ===

; ================================================
; microvax1.ini
; ================================================
;
; [[KD32]] CPU
; 2 [[MSV11-Q|MSV11-QA]] = 2MB Memory (or 4 MSV11-PL)
; [[DZV11]] Four-Channel Asynchronous Serial Interface
; [[RQDX1]] Floppy/Fixed Disk Controller
; [[RX50]] 400KB 5.25" Dual Floppy Drive
; [[RD52]] 31MB 5.25" Fixed Disk
; [[DEQNA]] Ethernet Network Adapter

SET QUIET

SET CONSOLE LOG=uVMS_gen_installed_001.log

SET CPU IDLE=VMS

; Uncomment the next line if you want a more realistic MicroVAX I speed
;SET THROTTLE 300K

SET CPU 2M
SET RQ0 RD52
att rq0 uVMS040.R52
SET RQ1 RX50
att rq1 BL-B012B-BE.dsk
SET RQ2 RX50

SET RQ3 DISABLE

SET DZ ENABLE
SET DZ LINES=4
ATT DZ 6666

SET LPT DIS
SET RL DIS

SET XQ ENA
SET XQ TYPE=DEQNA

BOOT RQ0

== MicroVMS V4.0 Base Installation ==

=== Start the SIMH MicroVAX I Simulator ===

Windows:
run microvax1.exe

Linux:
./microvax1

Be aware that Linux is case sensitive!

=== Boot MicroVMS V4.0 Standalone Backup ===

sim> '''b rq1/r5:100'''
.2.
Bootfile:'''[SYS0.SYSEXE]SYSBOOT.EXE'''
.0.

MicroVMS Version V4.0 15-SEP-1984 22:29

PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) '''12-JUL-2023 8:36'''

Please remove the volume "SYSTEM_1" from the console device.

Insert the standalone application volume and enter "YES" when ready: '''[CTRL-e]'''
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''att rq1 BL-B013B-BE.dsk'''
sim> '''c'''
'''yes'''

Resuming load operation on volume "BACKUP", please stand by . . .

%BACKUP-I-IDENT, Stand-alone BACKUP V4.0; the date is 12-JUL-2023 08:36:18.97
$

=== Restore MicroVMS V4.0 BASE Saveset ===

''' The floppy BL-B013B-BE.dsk has to remain in drive 1 (rq1) while restoring!'''

$ '''[CTRL-e]'''
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''att rq2 BL-B001B-BE.dsk'''
sim> '''c'''
'''[ENTER]'''
$ '''backup/log/verify/init dua2:microvms/save dua0:'''

%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]SYSEXE.DIR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]ANALYZBAD.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]AUTHORIZE.EXE;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]CDU.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CHECKSUM.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CONVERT.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]COPY.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CREATE.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CREATEFDL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CVTNAF.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CVTUAF.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DCL.EXE;1
%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-S-COMPARED, compared DUA0:[000000]000000.DIR;1
%BACKUP-S-COMPARED, compared DUA0:[000000]BACKUP.SYS;1
%BACKUP-S-COMPARED, compared DUA0:[000000]CONTIN.SYS;1
%BACKUP-S-COMPARED, compared DUA0:[000000]CORIMG.SYS;1
%BACKUP-S-COMPARED, compared DUA0:[000000]SYS0.DIR;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSCBI.DIR;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSERR.DIR;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSEXE.DIR;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]ANALYZBAD.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]AUTHORIZE.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]BACKUP.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]BADBLOCK.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]CDU.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]CHECKSUM.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]CONVERT.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]COPY.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]CREATE.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]CREATEFDL.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]CVTNAF.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]CVTUAF.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DCL.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DELETE.EXE;1
%BACKUP-I-RESUME, resuming operation on volume 2
%BACKUP-I-READYREAD, mount volume 2 on _SABKUP$DUA2: for reading
Enter "YES" when ready: '''[CTRL-e]'''
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''att rq2 BL-B002B-BE.dsk'''
sim> '''c'''
'''yes'''

%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]DUDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DZDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]EDT.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]ERRFMT.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]F11BXQP.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]FPEMUL.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]INIT.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]LIBRARIAN.EXE;1
%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DELETE.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DIRECTORY.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DISMOUNT.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DLDRIVER.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DUDRIVER.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DZDRIVER.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]EDT.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]ERRFMT.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]F11BXQP.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]FPEMUL.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]INIT.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]INSTALL.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]JOBCTL.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]LIBRARIAN.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]LINK.EXE;1
%BACKUP-I-RESUME, resuming operation on volume 3
%BACKUP-I-READYREAD, mount volume 3 on _SABKUP$DUA2: for reading
Enter "YES" when ready: '''[CTRL-e]'''
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''att rq2 BL-B003B-BE.dsk'''
sim> '''c'''
'''yes'''

%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]LINK.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]LOGINOUT.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]MODPARAMS.DAT;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]PAGEFILE.SYS;1systemctl daemon-reload
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]PATCH.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]PUDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]RECLAIM.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]RIGHTSLIST.DAT;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]RMS.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]RUNDET.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SCSLOA.EXE;1
%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]LINK.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]LOGINOUT.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]MODPARAMS.DAT;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]NOTICE.TXT;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]OPCCRASH.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]OPCOM.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]PAGEFILE.SYS;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]PATCH.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]PUDRIVER.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]RECLAIM.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]RENAME.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]REPLY.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]RIGHTSLIST.DAT;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]RMS.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]RUNDET.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SCSLOA.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SET.EXE;1
%BACKUP-I-RESUME, resuming operation on volume 4
%BACKUP-I-READYREAD, mount volume 4 on _SABKUP$DUA2: for reading
Enter "YES" when ready: '''[CTRL-e]'''
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''att rq2 BL-B004B-BE.dsk'''
sim> '''c'''
'''yes'''

%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]SETSHOACL.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]SORTMERGE.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]STARTUP.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SUMSLP.EXE;1
%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SET.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SETP0.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SETSHOACL.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SHOW.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SHUTDOWN.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SMGMAPTRM.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SORTMERGE.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]STARTUP.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SUMSLP.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYS.EXE;2
%BACKUP-I-RESUME, resuming operation on volume 5
%BACKUP-I-READYREAD, mount volume 5 on _SABKUP$DUA2: for reading
Enter "YES" when ready: '''[CTRL-e]'''
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''att rq2 BL-B005B-BE.dsk'''
sim> '''c'''
'''yes'''

%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYS.EXE;2
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSALF.DAT;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]SYSLOAUV1.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOAWS1.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSUAF.DAT;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TERMTABLE.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TTDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TYPE.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]UNLOCK.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]UVSTARTUP.COM;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]VERIFY.EXE;1
%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYS.EXE;2
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSALF.DAT;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSBOOT.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSGEN.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSINIT.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOAUV1.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOAWS1.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSUAF.DAT;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]TERMTABLE.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]TTDRIVER.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]TYPE.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]UNLOCK.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]UVSTARTUP.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]VAXEMUL.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]VAXVMSSYS.PAR;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]VERIFY.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]VMOUNT.EXE;1
%BACKUP-I-RESUME, resuming operation on volume 6
%BACKUP-I-READYREAD, mount volume 6 on _SABKUP$DUA2: for reading
Enter "YES" when ready: '''[CTRL-e]'''
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''att rq2 BL-B006B-BE.dsk'''
sim> '''c'''
'''yes'''

%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]YFDRIVER.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSHLP.DIR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSHLP]EDTHELP.HLB;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSHLP]EXAMPLES.DIR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSHLP]HELPLIB.HLB;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSHLP]UAFHELP.HLB;1
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSLIB.DIR;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]BASRTL.EXE;1
%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]VMOUNT.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]VMSHELP.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]YFDRIVER.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSHLP.DIR;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSHLP]EDTHELP.HLB;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSHLP]EXAMPLES.DIR;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSHLP]HELPLIB.HLB;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSHLP]UAFHELP.HLB;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSLIB.DIR;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]BASRTL.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]BASRTL2.EXE;1
%BACKUP-I-RESUME, resuming operation on volume 7
%BACKUP-I-READYREAD, mount volume 7 on _SABKUP$DUA2: for reading
Enter "YES" when ready: '''[CTRL-e]'''
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''att rq2 BL-B007B-BE.dsk'''
sim> '''c'''
'''yes'''

%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]CONVSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]CRFSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]DBGSSISHR.EXE;1
%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]BASRTL2.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]CDDSHR.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]COBRTL.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]CONVSHR.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]CRFSHR.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]DBGSSISHR.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]DCLTABLES.EXE;1
%BACKUP-I-RESUME, resuming operation on volume 8
%BACKUP-I-READYREAD, mount volume 8 on _SABKUP$DUA2: for reading
Enter "YES" when ready: '''[CTRL-e]'''
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''att rq2 BL-B008B-BE.dsk'''
sim> '''c'''
'''yes'''

%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]EDTSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]ENCRYPSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]FDLSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]FORRTL.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-I-STARTVERIFY, starting verification pass
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]DCLTABLES.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]DCXSHR.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]DISMNTSHR.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]EDTSHR.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]ENCRYPSHR.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]FDLSHR.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]FORRTL.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]LBRSHR.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]LIBRTL.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]LIBRTL2.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]MOUNTSHR.EXE;1
%BACKUP-I-RESUME, resuming operation on volume 9
%BACKUP-I-READYREAD, mount volume 9 on _SABKUP$DUA2: for reading
Enter "YES" when ready: '''[CTRL-e]'''
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''att rq2 BL-B009B-BE.dsk'''
sim> '''c'''
'''yes'''

%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]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]SORTSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]STARLET.OLB;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]SUMSHR.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]TRACE.EXE;1
%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]MOUNTSHR.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]MTHRTL.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]PASRTL.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]PLIRTL.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]RPGRTL.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]SCRSHR.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]SECURESHR.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]SMGSHR.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]SORTSHR.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]STARLET.OLB;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]SUMSHR.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]TRACE.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]UVMTHRTL.EXE;1
%BACKUP-I-RESUME, resuming operation on volume 10
%BACKUP-I-READYREAD, mount volume 10 on _SABKUP$DUA2: for reading
Enter "YES" when ready: '''[CTRL-e]'''
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''att rq2 BL-B010B-BE.dsk'''
sim> '''c'''
'''yes'''

%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]UVMTHRTL.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]ADDUSER.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]ALFMAINT.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]EDTINI.EDT;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]LOGIN.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]SUCCESS.TXT;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]SYCONFIG.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]SYLOGIN.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.DAT;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]WELCOME.TXT;1
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSMSG.DIR;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]SHRIMGMSG.EXE;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]SYSMGTMSG.EXE;1
%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]UVMTHRTL.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]VMSRTL.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSMAINT.DIR;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSMGR.DIR;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMGR]ADDUSER.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMGR]ALFMAINT.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMGR]EDTINI.EDT;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMGR]LOGIN.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMGR]SUCCESS.TXT;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMGR]SYCONFIG.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMGR]SYLOGIN.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMGR]SYSHUTDWN.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMGR]SYSTARTUP.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMGR]VMSIMAGES.DAT;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMGR]WELCOME.TXT;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSMSG.DIR;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]CLIUTLMSG.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]DBGTBKMSG.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]FILMNTMSG.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]NETWRKMSG.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]PASMSG.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]PLIMSG.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]PRGDEVMSG.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]RPGMSG.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]SHRIMGMSG.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]SYSMGTMSG.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]SYSMSG.EXE;1
%BACKUP-I-RESUME, resuming operation on volume 11
%BACKUP-I-READYREAD, mount volume 11 on _SABKUP$DUA2: for reading
Enter "YES" when ready: '''[CTRL-e]'''
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''att rq2 BL-B011B-BE.dsk'''
sim> '''c'''
'''yes'''

%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]SYSMSG.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]AUTOGEN.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]BACKUSER.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]CVTNAF.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]CVTUAF.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]LIBDECOMP.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]REMOVE.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]RESTUSER.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]SPKITBLD.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]SWAPFILES.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]VMSINSTAL.COM;1
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]VMSKITBLD.DAT;1
%BACKUP-S-CREATED, created DUA0:[000000]SYSEXE.DIR;1
%BACKUP-S-CREATED, created DUA0:[000000]USER.DIR;1
%BACKUP-S-CREATED, created DUA0:[USER]EDTINI.EDT;1
%BACKUP-S-CREATED, created DUA0:[USER]LOGIN.COM;1
%BACKUP-S-CREATED, created DUA0:[000000]VOLSET.SYS;1
%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]SYSMSG.EXE;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSTEST.DIR;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSUPD.DIR;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]AUTOGEN.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]BACKUSER.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]CVTNAF.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]CVTUAF.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]LIBDECOMP.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]REMOVE.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]RESTUSER.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]SPKITBLD.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]SWAPFILES.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]VMSINSTAL.COM;1
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]VMSKITBLD.DAT;1
%BACKUP-S-COMPARED, compared DUA0:[000000]SYSEXE.DIR;1
%BACKUP-S-COMPARED, compared DUA0:[000000]USER.DIR;1
%BACKUP-S-COMPARED, compared DUA0:[USER]EDTINI.EDT;1
%BACKUP-S-COMPARED, compared DUA0:[USER]LOGIN.COM;1
%BACKUP-S-COMPARED, compared DUA0:[000000]VOLSET.SYS;1
%BACKUP-I-IDENT, Stand-alone BACKUP V4.0; the date is 12-JUL-2023 08:37:33.85
$ '''[CTRL-e]'''
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''exit'''
Goodbye
Log file closed

=== Apply Mandatory Update ===

sim> b rq0
.2..1..0.

MicroVMS Version V4.0 15-SEP-1984 22:29

PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) '''12-JUL-2023 8:40'''

The MicroVMS system is now executing the site-specific startup commands.

You have successfully installed and started
the MicroVMS base kit. The system is now
ready for you to login.

%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
SYSTEM job terminated at 12-JUL-2023 08:40:19.69

Welcome to MicroVMS V4.0

Username: '''SYSTEM'''

Welcome to MicroVMS V4.0

%SET-W-NOTSET, error modifying OPA0:
-SET-I-UNKTERM, unknown terminal type

$ '''[CTRL-e]'''
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''att rq1 BL-DZ13A-BE.dsk'''
sim> '''c'''

$ '''@sys$update:vmsinstal'''

VAX/VMS Software Product Installation Procedure V4.0

It is 12-JUL-2023 at 08:40.
Enter a question mark (?) at any time for help.

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

Enter the products to be processed from the first distribution volume set.
* Products: '''*'''

Please mount the first volume of the set on DUA1:
* Are you ready? '''yes'''

%MOUNT-I-MOUNTED, VMSMUP04001 mounted on _DUA1:

The following products will be processed:

VMSMUP V4.0

Beginning installation of VMSMUP V4.0 at 08:41

%VMSINSTAL-I-RESTORE, Restoring product saveset A...

This is the mandatory update for MicroVMS V4.0

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]: '''3'''

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

%MOUNT-I-WRITELOCK, volume is write locked
%MOUNT-I-MOUNTED, VMSMUP04001 mounted on _DUA1:
%BACKUP-S-CREATED, created VMI$ROOT:[SYSUPD.VMSMUP040]DCL.VUP;1
%BACKUP-S-CREATED, created VMI$ROOT:[SYSUPD.VMSMUP040]F11BXQP.VUP;2
%BACKUP-S-CREATED, created VMI$ROOT:[SYSUPD.VMSMUP040]JOBCTL.VUP;1
%BACKUP-S-CREATED, created VMI$ROOT:[SYSUPD.VMSMUP040]SYS.VUP;1
%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-S-COMPARED, compared VMI$ROOT:[SYSUPD.VMSMUP040]DCL.VUP;1
%BACKUP-S-COMPARED, compared VMI$ROOT:[SYSUPD.VMSMUP040]F11BXQP.VUP;2
%BACKUP-S-COMPARED, compared VMI$ROOT:[SYSUPD.VMSMUP040]JOBCTL.VUP;1
%BACKUP-S-COMPARED, compared VMI$ROOT:[SYSUPD.VMSMUP040]SYS.VUP;1
%BACKUP-S-CREATED, created VMI$ROOT:[SYSUPD.VMSMUP040]NETACP.VUP;4
%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-S-COMPARED, compared VMI$ROOT:[SYSUPD.VMSMUP040]NETACP.VUP;4
%BACKUP-S-CREATED, created SYS$SYSROOT:[SYSUPD]UPDKIT040.TXT;1
%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-S-COMPARED, compared SYS$SYSROOT:[SYSUPD]UPDKIT040.TXT;1

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

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

3) 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.VMSMUP040]JOBCTL.EXE;1

4) NETACP (patch image)
%VMSINSTAL-W-NOFILE, File VMI$ROOT:[SYSEXE]NETACP.EXE does not exist.

5) 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.VMSMUP040]SYS.EXE;1

%VMSMUP-E-ERRORS, Of the 5 fixes listed above, the following 1 should be reviewed:
4
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

Installation of VMSMUP V4.0 completed at 08:41

%VMSINSTAL-I-REBOOT, This product requires that the system be rebooted.

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 = 1
%SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped.

SHUTDOWN message on SALONE from user SYSTEM at _SALONE$OPA0: 08:41:29
SALONE will shut down in 0 minutes; back up soon. Please log off node SALONE.
Reboot after VMSMUP V4.0 installation.

1 terminal has been notified on SALONE.

%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.

SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM

Infinite loop, PC: 80008D7E (BRB 80008D7E)
sim> '''exit'''

=== Boot Finished Base Installation ===

'''b rq0'''
.2..1..0.

MicroVMS Version V4.0 15-SEP-1984 22:29

PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) '''12-JUL-2023 8:44'''

The MicroVMS system is now executing the site-specific startup commands.

%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
SYSTEM job terminated at 12-JUL-2023 08:44:11.84

Welcome to MicroVMS V4.0

Username: '''SYSTEM'''

Welcome to MicroVMS V4.0

Last interactive login on Wednesday, 12-JUL-2023 08:40

%SET-W-NOTSET, error modifying OPA0:
-SET-I-UNKTERM, unknown terminal type

$ '''show sys'''

VAX/VMS V4.0 on node 12-JUL-2023 08:44:31.93 Uptime 0 00:01:41
Pid Process Name State Pri I/O CPU Page flts Ph.Mem
00000010 NULL COM 0 0 0 00:01:39.59 0 0
00000011 SWAPPER HIB 16 017-NOV-1858 00:0 0 0
00000014 JOB_CONTROL HIB 8 17 0 00:00:00.01 83 185
00000015 SYSTEM CUR 4 82 0 00:00:00.07 537 151

$ '''sh dev'''

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
SALONE$DUA0: Mounted 0 MICROVMS 46618 19 1
SALONE$DUA1: Online 0
SALONE$DUA2: Online 0

Device Device Error
Name Status Count
OPA0: Online 0
TTA0: Online 0
TTA1: Online 0
TTA2: Online 0
TTA3: Online 0

Device Device Error
Name Status Count
PUA0: Online 1

$ '''sh mem'''

System Memory Resources on 12-JUL-2023 08:44:48.72

Physical Memory Usage (pages): Total Free In Use Modified
Main Memory (2.00Mb) 4096 2589 1398 109

Slot Usage (slots): Total Free Resident Swapped
Process Entry Slots 12 8 4 0
Balance Set Slots 10 8 2 0

Fixed-Size Pool Areas (packets): Total Free In Use Size
Small Packet (SRP) List 60 12 48 96
I/O Request Packet (IRP) List 44 9 35 208
Large Packet (LRP) List 8 4 4 656

Dynamic Memory Usage (bytes): Total Free In Use Largest
Nonpaged Dynamic Memory 119808 45856 73952 42608
Paged Dynamic Memory 69632 4784 64848 4128

Paging File Usage (pages): Free In Use Total
DISK$MICROVMS:[SYS0.SYSEXE]PAGEFILE.SYS 4216 384 4600

Of the physical pages in use, 962 pages are permanently allocated to VMS.

$ '''shutdown'''

SHUTDOWN -- Perform an Orderly System Shutdown

%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 = 1
%SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped.

SHUTDOWN message on SALONE from user SYSTEM at _SALONE$OPA0: 08:45:19
SALONE will shut down in 0 minutes; back up LATER. Please log off node SALONE.
SHUTDOWN

1 terminal has been notified on SALONE.

%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.

SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM

Infinite loop, PC: 80008D7E (BRB 80008D7E)
sim> '''exit'''
Goodbye

== Optional System Software ==

=== Choose Optional System Software ===

There are four sets of optional system software. Each set contains some utilities, whereof you can choose:

* '''UTIL''' Set (floppies BL-B014B-BE to BL-B017B-BE):
** MAIL utility
** SEARCH utility
** DIFF utility
** DUMP utility
** RUNOFF utility
** PHONE utility
** MicroVMS HELP library
** Remote terminal support via SET HOST/DTE
** Drivers for network communication devices
** LAT-11 terminal server support (via Ethernet)
** Stand-alone backup on system disk support

* '''USER''' Set (floppy BL-B018B-BE):
** File Access Control List utilities
** Disk Quota utility
** Print and Batch Queue utilities
** Input Queue Symbiont (Card Reader)
** Accounting Log Report Generator utility

* '''PROG''' Set (floppies BL-B20B-BE to BL-B025B-BE):
** Debugger utility
** Image Dump utility
** RMS Analyze and FDL Editor utilities
** Message utility
** Object and Shareable Image libraries
** Macro libraries
** Macro assembler
** SDL intermediary form of STARLET.MLB
** FORTRAN require files

* '''SYSP''' Set (floppies BL-B026B-BE to BL-B031B-BE):
** Error Log Report Generator utility
** Files-11 ODS1 ACP and EXCHANGE utility
** Magtape ACP
** Monitor utility
** Analyze Object File utility
** Delta debugger
** System Dump Analyzer utility
** System Symbol Table file
** Misc Symbol Table files
** System map
** Connect-to-Interrupt Driver

I recommend to install:

* '''UTIL''' Set:
** '''MAIL''' utility
** '''SEARCH''' utility
** '''PHONE''' utility
** MicroVMS '''HELP''' library
** Remote terminal support via '''SET HOST/DTE'''
** '''Drivers for network communication''' devices
** '''Stand-alone backup''' on system disk support

* '''USER''' Set:
** '''Disk Quota''' utility
** '''Print and Batch Queue''' utilities

* '''SYSP''' Set:
** '''Monitor''' utility

Choose whatever you want, but consider: disk space is limited!

=== Install Optional System Software ===

== DECnet Networking Software ==

=== Install DECnet ===

The MicroVMS V4.0 DECnet installation needs two steps:

* Install Drivers for network communication devices from the UTIL optional system software set
* Install DECnet software <br>(non-standard procedure, as the DECnet for MicroVMS V4.0 kit is not available as of now; DECnet license key is included)

sim> b rq0
.2..1..0.

MicroVMS Version V4.0 15-SEP-1984 22:29

PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 12-JUL-2023 9:00

%SYSGEN-W-OPENIN, error opening SYS$SYSROOT:[SYSEXE]XQDRIVER.EXE; as input
%SYSGEN-E-FNF, file not found

The MicroVMS system is now executing the site-specific startup commands.

%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
SYSTEM job terminated at 12-JUL-2023 09:00:29.70

Welcome to MicroVMS V4.0

Username: SYSTEM

Welcome to MicroVMS V4.0

Last interactive login on Wednesday, 12-JUL-2023 08:44

%SET-W-NOTSET, error modifying OPA0:
-SET-I-UNKTERM, unknown terminal type

$ ['''STRG + e''']
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''att rq1 BL-B014B-BE.dsk'''
sim> '''c'''

$ '''@sys$update:vmsinstal'''

VAX/VMS Software Product Installation Procedure V4.0

It is 12-JUL-2023 at 09:00.
Enter a question mark (?) at any time for help.

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

Enter the products to be processed from the first distribution volume set.
* Products: '''*'''

Please mount the first volume of the set on DUA1:.
* Are you ready? '''yes'''

%MOUNT-I-MOUNTED, UTIL01 mounted on _DUA1:

The following products will be processed:

UTIL V4.0

Beginning installation of UTIL V4.0 at 09:01

%VMSINSTAL-I-RESTORE, Restoring product saveset A...
* Do you want to install the entire kit: '''no'''
* Do you want to install the MAIL utility: '''no'''
* Do you want to install the SEARCH utility: '''no'''
* Do you want to install the DIFF utility: '''no'''
* Do you want to install the DUMP utility: '''no'''
* Do you want to install the RUNOFF utility: '''no'''
* Do you want to install the PHONE utility: '''no'''
* Do you want to install the MicroVMS HELP library: '''no'''
* Do you want to install the Remote terminal support via SET HOST/DTE: '''no'''
* Do you want to install the Drivers for network communication devices: '''yes'''
* Do you want to install the LAT-11 terminal server support (via Ethernet): '''no'''
* Do you want to install the Stand-alone backup on system disk support: '''no'''

%VMSINSTAL-I-RESTORE, Restoring product saveset J...
Please mount the next distribution volume on DUA1:.
(If no more volumes, answer NO.)
* Are you ready? ['''STRG + e''']
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''att rq1 BL-B015B-BE.dsk'''
sim> '''c'''
'''yes'''

%MOUNT-I-MOUNTED, UTIL02 mounted on _DUA1:
Please mount the next distribution volume on DUA1:.
(If no more volumes, answer NO.)
* Are you ready? ['''STRG + e''']
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''att rq1 BL-B016B-BE.dsk'''
sim> '''c'''
'''yes'''

%MOUNT-I-MOUNTED, UTIL03 mounted on _DUA1:
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

Installation of UTIL V4.0 completed at 09:01

Enter the products to be processed from the next distribution volume set.
* Products: ['''STRG + y''']
*INTERRUPT*

%VMSINSTAL-F-CTRLY, Installation cancelled via CTRL/Y.
%VMSINSTAL-F-UNEXPECTED, Installation terminated due to unexpected event.

VMSINSTAL procedure done at 09:01

$ '''dir sys$system:x*.*'''

Directory SYS$SYSROOT:[SYSEXE]

XDDRIVER.EXE;1 XQDRIVER.EXE;1

Total of 2 files.

$ ['''STRG + e''']
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''att rq1 DECNET040-1of2.rx5'''
sim> '''c'''

$ '''mou/for dua1:'''

%MOUNT-I-MOUNTED, NET040 mounted on _DUA1:

$ '''backup/log/verify dua1:<000000>decnet040.bck/sav sys$sysdevice:<*>'''

%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]NCP.EXE;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]NETACP.EXE;2
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]NETDRIVER.EXE;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]NETSERVER.EXE;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]NICONFIG.EXE;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]EVL.EXE;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]NDDRIVER.EXE;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]RTPAD.EXE;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]REMACP.EXE;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]RTTDRIVER.EXE;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]CTDRIVER.EXE;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]FAL.EXE;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]FAL.COM;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]PHONE.EXE;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]PHONE.COM;1
%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]NCP.EXE;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]NETACP.EXE;2
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]NETDRIVER.EXE;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]NETSERVER.EXE;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]NICONFIG.EXE;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]EVL.EXE;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]NDDRIVER.EXE;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]RTPAD.EXE;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]REMACP.EXE;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]RTTDRIVER.EXE;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]CTDRIVER.EXE;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]FAL.EXE;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]FAL.COM;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]PHONE.EXE;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]PHONE.COM;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]MAIL.EXE;1
%BACKUP-I-RESUME, resuming operation on volume 2
%BACKUP-I-READYREAD, mount volume 2 on _SALONE$DUA1: for reading
Enter "YES" when ready: ['''STRG + e''']
Simulation stopped, PC: 80008B1F (BRB 80008B1F)
sim> '''att rq1 DECNET040-2of2.rx5'''
sim> '''c'''
'''yes'''

%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]MAIL.EXE;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]MAIL.COM;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]MIRROR.EXE;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]MIRROR.COM;1
%BACKUP-E-OPENOUT, error opening SYS$SYSDEVICE:[SYS0.SYSEXE]EVL.EXE;1 as output
-RMS-E-FEX, file already exists, not superseded
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]EVL.COM;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]DTR.COM;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]NML.EXE;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSEXE]NML.COM;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSMGR]LOADNET.COM;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSMGR]NETCONFIG.COM;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSMGR]STARTNET.COM;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSMGR]RTTLOAD.COM;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSLIB]NMLSHR.EXE;1
%BACKUP-S-CREATED, created SYS$SYSDEVICE:[SYS0.SYSHLP]NCPHELP.HLB;1
%BACKUP-I-STARTVERIFY, starting verification pass
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]MAIL.EXE;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]MAIL.COM;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]MIRROR.EXE;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]MIRROR.COM;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]EVL.EXE;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]EVL.COM;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]DTR.COM;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]NML.EXE;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSEXE]NML.COM;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSMGR]LOADNET.COM;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSMGR]NETCONFIG.COM;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSMGR]STARTNET.COM;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSMGR]RTTLOAD.COM;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSLIB]NMLSHR.EXE;1
%BACKUP-S-COMPARED, compared SYS$SYSDEVICE:[SYS0.SYSHLP]NCPHELP.HLB;1

$

=== Configure DECnet ===

$ '''@netconfig'''

DECnet-VAX network configuration procedure

This procedure will help you define the parameters needed to get DECnet
running on this machine. You will be shown the changes before they are
executed, in case you wish to perform them manually.

What do you want your DECnet node name to be? [SALONE]: '''salone'''

What do you want your DECnet address to be? : '''1.42'''

Do you want to operate as a router? [NO (nonrouting)]: '''no'''

Do you want a default DECnet account? [YES]: '''yes'''

Here are the commands necessary to setup your system.

--------------------------------------------------------------------------
$ RUN SYS$SYSTEM:NCP
PURGE EXECUTOR ALL
PURGE KNOWN LINES ALL
PURGE KNOWN CIRCUITS ALL
PURGE KNOWN LOGGING ALL
PURGE KNOWN OBJECTS ALL
PURGE MODULE CONFIGURATOR KNOWN CIRCUITS ALL
$ DEFINE/USER SYS$OUTPUT NL:
$ DEFINE/USER SYS$ERROR NL:
$ RUN SYS$SYSTEM:NCP ! Remove existing entry, if any
PURGE NODE 1.42 ALL
PURGE NODE SALONE ALL
$ RUN SYS$SYSTEM:NCP
DEFINE EXECUTOR ADDRESS 1.42 STATE ON
DEFINE EXECUTOR NAME SALONE
DEFINE EXECUTOR MAXIMUM ADDRESS 255
DEFINE EXECUTOR TYPE NONROUTING IV
DEFINE EXECUTOR NONPRIVILEGED USER DECNET
DEFINE EXECUTOR NONPRIVILEGED PASSWORD DECNET
$ DEFINE/USER SYSUAF SYS$SYSTEM:SYSUAF.DAT
$ RUN SYS$SYSTEM:AUTHORIZE
ADD DECNET /OWNER="DECNET DEFAULT" -
/PASSWORD=DECNET -
Press RETURN to continue

/UIC=[376,376] /ACCOUNT=DECNET -
/DEVICE=SYS$SYSDEVICE: /DIRECTORY=[DECNET] -
/PRIVILEGE=(TMPMBX,NETMBX) -
/FLAGS=(CAPTIVE) /LGICMD=NL: -
/NOBATCH /NOINTERACTIVE
$ CREATE/DIRECTORY SYS$SYSDEVICE:[DECNET] /OWNER=[376,376]
$ RUN SYS$SYSTEM:NCP
DEFINE LINE QNA-0 STATE ON
DEFINE CIRCUIT QNA-0 STATE ON COST 4
DEFINE LOGGING MONITOR STATE ON
DEFINE LOGGING MONITOR EVENTS 0.0-9
DEFINE LOGGING MONITOR EVENTS 2.0-1
DEFINE LOGGING MONITOR EVENTS 4.2-13,15-16,18-19
DEFINE LOGGING MONITOR EVENTS 5.0-18
DEFINE LOGGING MONITOR EVENTS 128.0-4
--------------------------------------------------------------------------

Do you want to go ahead and do it? [YES]: '''yes'''

%UAF-I-ADDMSG, user record successfully added
%UAF-I-RDBADDMSGU, identifier DECNET value: [000376,000376] added to RIGHTSLIST.DAT
%UAF-I-DONEMSG, system authorization file modified
%UAF-I-RDBDONEMSG, rights database modified
%NCP-I-NMLRSP, listener response - Success
Logging sink type = monitor
%NML-I-RECADDED, Database entry added

The changes have been made.

If you have not already installed the DECnet-VAX license, then do so now.

After the license has been installed, you should invoke the procedure
SYS$MANAGER:STARTNET.COM to startup DECnet-VAX with these changes.

(If the license is already installed) Do you want DECnet started? [YES]: '''yes'''

%RUN-S-PROC_ID, identification of created process is 00000016
%RUN-S-PROC_ID, identification of created process is 00000018

$ '''set host 0'''

Welcome to MicroVMS V4.0

Username: '''SYSTEM'''

Welcome to MicroVMS V4.0

Last interactive login on Wednesday, 12-JUL-2023 09:00
%SET-W-NOTSET, error modifying RTA1:
-SET-I-UNKTERM, unknown terminal type

$ '''sh us'''

VAX/VMS Interactive Users
12-JUL-2023 09:05:13.23
Total number of interactive users = 2

Username Process Name PID Terminal
SYSTEM SYSTEM 00000015 OPA0:
SYSTEM _RTA1: 00000019 RTA1:

$ '''sh sys'''

VAX/VMS V4.0 on node SALONE 12-JUL-2023 09:05:15.84 Uptime 0 00:05:25
Pid Process Name State Pri I/O CPU Page flts Ph.Mem
00000010 NULL COM 0 0 0 00:05:16.35 0 0
00000011 SWAPPER HIB 16 0 0 00:00:00.01 0 0
00000014 JOB_CONTROL HIB 8 18 0 00:00:00.01 83 185
00000015 SYSTEM HIB 5 4045 0 00:00:06.99 16981 302
00000016 NETACP HIB 10 15 0 00:00:00.02 235 137
00000017 EVL HIB 4 43 0 00:00:00.03 326 29 N
00000018 REMACP HIB 9 1117-NOV-1858 00:0 69 37
00000019 _RTA1: CUR 4 94 0 00:00:00.07 669 152

$ '''set host 0'''

Welcome to MicroVMS V4.0

Username: '''SYSTEM'''

Welcome to MicroVMS V4.0

Last interactive login on Wednesday, 12-JUL-2023 09:05

%SET-W-NOTSET, error modifying RTA2:
-SET-I-UNKTERM, unknown terminal type

$ '''mc ncp sho kno link'''

Known Link Volatile Summary as of 12-JUL-2023 09:05:38

Link Node PID Process Remote link Remote user

1 1.42 (SALONE) 00000015 SYSTEM 2 CTERM
2 1.42 (SALONE) 00000018 REMACP 1 SYSTEM
3 1.42 (SALONE) 00000019 _RTA1: 4 CTERM
4 1.42 (SALONE) 00000018 REMACP 3 SYSTEM

$ '''sh us'''

VAX/VMS Interactive Users
12-JUL-2023 09:05:50.75
Total number of interactive users = 3

Username Process Name PID Terminal
SYSTEM SYSTEM 00000015 OPA0:
SYSTEM _RTA1: 00000019 RTA1:
SYSTEM _RTA2: 0000001A RTA2:

$ '''lo'''

SYSTEM logged out at 12-JUL-2023 09:05:53.13
%REM-S-END, control returned to node _SALONE::

$ '''lo'''
$ '''sh net'''

VAX/VMS Network status for local node 1.42 SALONE on 12-JUL-2023 09:06:01.79

$ '''sh us'''

VAX/VMS Interactive Users
12-JUL-2023 09:06:14.98
Total number of interactive users = 2

Username Process Name PID Terminal
SYSTEM SYSTEM 00000015 OPA0:
SYSTEM _RTA1: 00000019 RTA1:

$ '''lo'''

SYSTEM logged out at 12-JUL-2023 09:06:16.56
%REM-S-END, control returned to node _SALONE::

$ '''lo'''

SYSTEM logged out at 12-JUL-2023 09:06:54.75

Welcome to MicroVMS V4.0

Username: '''SYSTEM'''

Welcome to MicroVMS V4.0

Last interactive login on Wednesday, 12-JUL-2023 09:05

%SET-W-NOTSET, error modifying OPA0:
-SET-I-UNKTERM, unknown terminal type

$ '''shutdown'''

SHUTDOWN -- Perform an Orderly System Shutdown

%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 = 1
%SHUTDOWN-I-SHUTNET, The DECnet network will now be shut down.
%SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped.

SHUTDOWN message on SALONE from user SYSTEM at _SALONE$OPA0: 09:07:01
SALONE will shut down in 0 minutes; back up LATER. Please log off node SALONE.
SHUTDOWN

1 terminal has been notified on SALONE.

%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.

SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM

Infinite loop, PC: 80008D7E (BRB 80008D7E)
sim> exit
Goodbye

== Recommended Reading ==

* xxx

[[Category: SIMH Tutorials]]
[[Category: VMS Practical Guides]]

Talk:UI750 Unibus Interface

2025-11-15T15:18:06Z

Vaxorcist: Discussion about capitalization of UNIBUS

Is it correct that it is "Unibus" here in the page title instead of "[[UNIBUS]]"? [[User:Vaxorcist|Vaxorcist]] ([[User talk:Vaxorcist|talk]])

VAX Diagnostic Supervisor

2025-11-12T21:14:21Z

Vaxorcist: /* Some useful VDS commands */ "RUN/TEST=" command clarified

VDS - '''VAX Diagnostic Supervisor''' (sometimes abbreviated to VAX/DS) is a set of diagnostic software programs for the [[DEC]] [[VAX]] computers and peripheral devices.

== Intro ==

'''''"At best, a computer is as good as its diagnostic tools!"'''''

That's what they must have thought at DEC when they developed their diagnostic software.

Here we will take a closer look at the VAX Diagnostic Supervisor and also a quick side look at the [[User Environment Test Package]] (UETP).

== Using VDS for simulated VAX Computers ==

You may ask: "What are the VAX diagnostics good for when run on a simulated VAX?"

Yes, many diagnostics do not run on a simulated VAX, but some work very well and are used e.g. for testing the various [[SIMH]] VAX simulators for correct execution of the VAX native mode instructions.

Furthermore you can explore how precise the simulation mimics the real hardware.

If you plan to test your real VAX, you can familiarize yourself with VDS and prepare your diagnosis in SIMH, and SIMH can assist you in preparing and creating a diagnostic kit on media appropriate for your VAX.

Automated testing script for a SIMH VAX-11/750:

SET CLOCK NOCALIBRATE=600K
ATTACH -RQ RQ0 VAX_MINIMUM_DIAGS.dsk
EXPECT "DS> " SEND "ATTACH UDA50 DW0 DUA 772150 154 5 10\r"; GO -Q
EXPECT "DS> " SEND "ATTACH RA81 DUA DUA0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH KA750 CMI KA0 yes yes yes 0 0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH DW750 CMI DW0 8\r"; GO -Q
EXPECT "DS> " SEND "SET LOAD DUA0:[SYSMAINT]\r"; GO -Q
EXPECT "DS> " SEND "SELECT KA0\r"; GO -Q
EXPECT "DS> " SEND "SET FLAGS TRACE\r"; GO -Q
EXPECT "DS> " SEND "RUN EVKAB\r"; GO -Q
BOOT -Q RQ0 /R5:10

== VDS History ==

VDS development began in parallel that to the first [[VAX]] model, the [[VAX-11/780]] in 1977.

VDS was provided soley for the '''''"big VAXen"''''' (i.e. not for the [[MicroVAX]] and [[VAXstation]] computers), with one remarkable exception, the [[MicroVAX I]], resp. [[VAXstation I]].
Each new VAX model received its CPU-specific VDS modules up to the [[VAX 9000]]; only the VAX models of the last two series, [[VAX 7000]] and [[VAX 10000]], were covered by other diagnostic methods.

== Program Levels ==

All VAX diagnostic programs are assigned to a '''level'''. Levels are numbered 1, 2R, 2, 3, 4, and 5. A program’s level indicates its run-time environment.

* '''Level 1''' diagnostic programs run under an operating system. They do not use the VAX/DS. (=> UETP)
* '''Level 2R''' diagnostic programs run under VAX/DS in user mode only.
* '''Level 2''' diagnostic programs run in both user mode and standalone mode, under the control of the VAX/DS.
* '''Level 3''' diagnostic programs run only in standalone mode, under the control of the VAX/DS.
* '''Level 4''' diagnostic programs run in standalone without VAX/DS.
* '''level 5''' diagnostic programs run in [[Writable Control Store|WCS]] or system console, not in VAX main memory. They do not use the VAX/DS.

Only the levels 2R, 2, and 3 are managed by VDS.

== Sections, Tests, Subtests, and Flags ==

All diagnostic programs that run under the VAX/DS are composed of one or more '''sections'''. Each section has a name, and it is possible to specify, by name, which section of the program to execute. A program section can have one of two functions, depending on its design:

* Test a certain major portion of the unit under test.
* Facilitate a certain mode of testing. For example, there might be a quick-verify section, used to give the device a quick (but not thorough) test.

In order to determine the number and names of the sections in a particular diagnostic program, use the <code>SHOW SECTIONS</code> command. However, every program contains a default section called <code>DEFAULT</code>, which will execute automatically if you do not specifically select a section. A section is selected with the <code>/SECTION</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Each section is composed of a set of '''tests'''; each test verifies either a particular function of the hardware or a particular subset of the component logic being tested. The VAX/DS allows you to specify which tests within a section to run. Each test may have some '''subtests'''. Tests are selected with the <code>/TEST</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Two sets of '''flags''' are provided to control certain aspects of a diagnostic program’s execution. These flags may be set or cleared before the diagnostic program is started.

One set of flags is called the '''VAX/DS control flags'''. The flags in this set are interpreted by the VAX/DS and their meanings are the same in all diagnostic programs. The VAX/DS control flags are set with the <code>SET FLAGS</code> command.

The other set of flags is referred to as the '''event flags'''. This set consists of 23 flags whose purposes are defined by the diagnostic programs. The user must read the documentation for specific diagnostic programs to determine if a definition has been assigned to any of the event flags. <code>SET EVENT FLAGS</code> command.

== Some useful VDS commands ==

* <code>'''SET LOAD disk:[directory]'''</code> Set diagnostic load path
* <code>'''LOAD''' Exxxx</code> Load diagnostic Exxxx (where "Exxxx" is replaced by the diagnostics name, e.g. EVKAA)
* <code>'''SET TRACE'''</code> Show progress
* <code>'''SHOW FLAGS'''</code> Show VDS flags
* <code>'''SHOW TESTS'''</code> Show the available tests of the loaded diagnostic
* <code>'''SHOW SECTIONS'''</code> Show the available sections of the loaded diagnostic
* <code>'''START/TEST='''first:last</code> Start a subset of the loaded diagnostics tests (where "first" is the test number to start with, and -optionally- "last" is the last one to execute)
* <code>'''START/SECTION='''section-name</code> Start a single section of the loaded diagnostic (where "section-name" is the name of the section to run)
* <code>'''START/PASSES='''count</code> Start the loaded diagnostic for "count" passes (where "count" is the number of passes to execute)
* <code>'''RUN''' exxxx'''/TEST='''first:last</code> Run a subset of the diagnostics tests; if "last" is not given, all tests from start up the the last one are run, to run a single test, enter "=n:n", where "n" is the test number
* <code>'''RUN''' exxxx'''/SECTION='''section-name</code> Run a single section of the diagnostic
* <code>'''RUN''' exxxx'''/PASSES='''count</code> Run the diagnostic for "count" passes

Use a pass count of 0 to run a program continuously. If you do this, the program will run until you type CTRL/C or a failure occurs with the HALT flag set.

== Diagnostic Program Documentation ==

Documentation provided for each diagnostic program includes:

* '''Help file'''
:: The help file is referenced with the HELP command. It contains any operating instructions that may be unique to the diagnostic program. The help file for diagnostic program EVXYZ is EVXYZ.HLP; the help file for the VAX/DS is EVSAA.HLP

* '''Documentation file'''
:: The documentation file provides a detailed description of a diagnostic program's function, run-time requirements, operating instructions, fault detection, and maintenance history, plus explanations of each test’s function and execution flow. The documentation file for diagnostic program EVXYZ is EVXYZ.DOC.

* '''Source Code listings'''
:: Source code listings of the diagnostic programs are available. All VAX/DS diagnostic programs are structured in a standard format. For example, the initialization code for every diagnostic program is always located in the same relative area within the listing. To fully understand the source code listings of a VAX/DS diagnostic program, refer to the VAX Diagnostic Design Guide.

The help file for a diagnostic program is shipped with the diagnostic program. The documentation file and source codelistings are available by ordering a [[Maintenance Documentation Service]] Option on microfiche.

== Diagnostic Scopes ==

There are two diagnostic scopes.

* A CPU-specific scope: '''CPU Cluster Testing'''
* A scope for the identical diagnostic programs for all types of VAX computers: '''Peripheral Diagnostics'''

=== CPU Cluster Testing ===

'''NOTE: The term "CPU cluster" used here means all components belonging to a CPU; there is no connection with the term [[VAXcluster|"VAXcluster" (alternatively: "VMScluster")]].'''

The VAX CPU cluster is tested by a set of programs, existing at several program levels, as follows:

* Level 5
** Console tests
** Processor tests
** Memory tests
* Level 4
** VAX instruction set test (hardcore for VDS)
** Cache and translation buffer tests (VAX-11/750 only)
* Level 3
** Memory tests (if no level 5 test possible)
** Channel adapter tests
** Cluster exerciser

'''NOTE: The term "Channel adapter" used here means bus adapter, e.g. for [[UNIBUS]] or [[MASSBUS]].'''

This set of programs implements the VAX diagnostic strategy by providing a set of building blocks by which a system may be tested, starting with the level 5 basic processor tests and ending with the level 3 cluster exerciser, which is a program meant to exercise all components of the cluster.

=== Peripheral Diagnostics ===

Thorough testing of a peripheral device requires the development of three different diagnostic programs. For each device type the following will typically (but not necessarily) exist:

* A level 3 logic test
* A level 3 function test
* A level 2R function test

This group of programs implements the diagnostic strategy by providing a facility for producing very accurate and detailed identifications of fault conditions via the level 3 programs and by also providing a method by which the device may be tested without bringing down the customer's operating system via the level 2R program.

The level 3 logic test will provide the greatest detail of error resolution, indicating which section of logic is failing. This program will be used by technicians to repair bad logic boards, and will provide very high test coverage. Some devices contain ROM-resident microprograms ("self-tests") that perform logic testing, making a level 3 logic test unnecessary.

The level 3 function test will provide a comprehensive test of all of the device’s functions. This program will be used to determine accurately whether or not a device is operating correctly. This is the definitive function test and provides very high test coverage. Level 3 function tests are usually required even if the device possesses self-testing capabilities, because self-tests generally are not capable of complete detection of function failures.

The level 2R program will typically consist of a subset of the level 3 function test. It will test as much of the device’s functionality as can be tested in the user (VMS) environment. The tests it contains are exact or approximate copies of tests existing in the level 3 program.

A typical sequence of use for these programs, when dealing with a system at a customer site, is as follows:

# The customer (or field service) suspects a fault existing in the device.
# The level 2R program is run to see if the error can be detected without stopping the operating system. If the error is found, go to step 4.
# If the level 2R program cannot identify the fault, the operating system is brought down and the level 3 function test is run.
# The fault is identified and the failing [[Field Replacable Unit|FRU]] is replaced. The operating system is then brought back up.
# The failing FRU is brought back to DIGITAL, where the level 3 logic test, the level 3 function test, or perhaps a module test station is used to identify the failing logic on the FRU. The FRU is repaired.

== VAX Diagnostic Coding Convention ==

VAX diagnostic program names consist of 5 letters and a two-digit version number, e.g.: ECKAL-3.4:

* E = VAX
* C = 11/750
* K = CPU
* A = Supervisor
* L = Unique identifier
* 3 = Major revision
* 4 = Minor Revision

See the following 1986 VAX Diagnostic Coding Convention Table for letter breakdown:

EPXYD-R.P

E = System

E = VAX

P = Processor

B = VAX 8200/8300
D = VAX 8600
S = VAX 11780
T = VAX 11785
C = VAX 11750
N = VAX 11730 and 11725
H = MicroVAX I
J = VAX 8820/8830/8840
V = More than one VAX Processor
X = VAX 6000
Z = VAX 8530/8550/8700/8800

X = Device Category

A = Application (CR, LP, A-D, Misc.)
C = Channel Adaptors (MBA, UBA)
D = Communication Devices (DMC, DZ11)
G = CI Adapter
K = CPU
L = Database Files
M = Magnetic Tape (TE, TU, DT)
P = Test Equipment
Q = QIO Device Driver
R = Rotating Memory (RP, RK, RM, RS, RX)
S = System Monitor (Supervisor, Tape Monitor)
T = Terminal (LA36, VT52)
U = Utilities (Script file, Copy, Update)
W = Workstations
X = System Exerciser (EXR/BUSINT)
Z = Media Packages
0-9 = Engineering File

Y = Device Type

Category Application
A = Line Printers, LP, LCP01
B = Card Readers, CR
L = LPA11-K
Category Channel
A = MBA
B = UBA, DWBUA
C = MA780
D = IEC11, IEU11-A, DR70
E = DT07
F = DEC DATAWAY
G = CI780
H = CI750/CI780 MICROCODE VERIFICATION (INTERNAL)
I = TEST BED ADAPTERS
J = NBI ADAPTER
K = CIBCI

Category Communications
A = DZ11,DZ32,DMZ32,DHU11,DMB32
B = DMC
C = Multiple Devices
D = DR11-C
E = DV11
F = DR780,DF11-W
G = DQS11
H = KMC11-B
I = KMS11-B
J = DM11-BA
K = DMS11-BA
L = DMF32 Combo
M = DMC11,DMR11,DMP11
N = DN11
O = CPI32
P = PCL11
R = DR11B,DR11-W,DRE11
S = DRS11/DSS
T = KCT32-A,FEPCM
U = DUP11
X = Multiple Devices
W = UNA
Y = DEBNT

Category Database Files
A = CRD DATABASE FILES
B = SYSTEM EXERCISER DATABASE FILES

Category Magnetic Tape
A = TE16/77, TS11, TU78, TS05
B = TU81,TU80

Category QIO Device Drivers
For this category, the fourth and fifth letters of the code are the device mnemonic.
For example, EVQDB is the QIO device driver for the DB, or RP disk series.

Category Test Equipment
A = CI780 Node Tester
B = NI Tester

Category Rotating Memory
A = Multiple devices
B = RP04/5/6
C = DCL/RP04/5/6
D = RM03/RM05/RM80
E = RK611,RK06,RK07
F = RL02
G = RM80
H = RP07
I = RX02
J = ML11
K = IDC
L = UDA50(RA60,RA80,RA81)
M = RC25
N = RUX50

Category System Monitor
A = Supervisor
B = Autosizer
C = DYDDM

Category Terminals
A = All Terminals
B = Terminal exerciser
C = VS11
D = 11C03-LH Fastek
G = VS70

Category Utility
A = Script File
B = Copy Command file
C = Updating file

Category Workstation
A = VS100

Category Exerciser
B = Exerciser Bus Interaction

D = Fifth character makes the code unique. A through Z and 1 through 9.

R = Revision (MAJOR)
P = Revision (MINOR)

== Distribution of Diagnostic Programs ==

Typically, a VAX computer came with all the necessary diagnostic programs on console media at no additional charge, e.g.:

* VAX-11/780: [[RX01/02 floppy drive|RX01 floppies]]
* VAX-11/750, VAX-11/730, and VAX-11/725: [[TU58 DECtape II|TU58 cartridges]]
* VAX 8600: [[RL01/02 disk drive|RL02 disk pack]]
* VAX 8200, VAX 8250, VAX 8300, and VAX 8350: [[RX50 dual-diskette drive|RX50 floppies]]

Additionally, you could buy larger collections of diagnostic programs on [[magnetic tape]] or [[Removable-pack disk|removable disk packs]].

Extended documentation was available on microfiche at an extra charge.

== VMS User Enviroment Test Package (UETP) ==

From the very beginning of VMS V1.0 there was the '''[[User Enviroment Test Package]]''' (UETP), see: [http://bitsavers.trailing-edge.com/pdf/dec/vax/vms/2.0/AA-D643B-TE_VAX-VMS_2.0_UETP_Users_Guide_198003.pdf VAX/VMS UETP User’s Guide AA-D643A-TE]

Quote from the first UETP manual:

"''The UETP is a collection of tests designed to demonstrate that the hardware and software components of a VAX/VMS system are in working order. DIGITAL software support representatives run the UETP on a newly installed VAX/VMS system as the formal sample procedure.''"

UETP is still used in the latest version of VMS (V9.2-2 for x86 as of this writing).

[https://docs.vmssoftware.com/vsi-openvms-system-manager-s-manual-volume-2-tuning-monitoring-and-complex-systems/#_6017UETP| See here] for the latest VMS UETP manual.

== ULTRIX System Exerciser Package ==

[[ULTRIX]] has got a very similar tool to verify proper hardware operation at the operating system level, the '''[[System Exerciser Package]]'''.

For the earliest reference found so far see the manual: [https://drive.google.com/file/d/1i3LoLAvTQC7dZl-T9X3SsQgg_6s_6TCY/view?usp=sharing ULTRIX-32 2.2 System Exercisers 1987 AA-KS95A-TE]

The MIPS variants of ULTRIX include the System Exerciser Package, too.

== Additional Diagnostic Tools ==

* On-board ROM-based diagnostics (RBDs) / Self-tests
* [[Diagnostic and Utility Protocol|DUP]] for [[Mass Storage Control Protocol|MSCP]] devices

== CPU-specific Supervisors ==

* '''EBSAA''' VAX 8200/8250/8300/8350 & VS8000 Diagnostic Supervisor
* '''ECSAA''' VAX-11/750 DIAGNOSTIC SUPERVISOR
* '''EDSAA''' VAX 8600/8650 Diagnostic Supervisor
* '''EHSAA''' MicroVAX I VDS
* '''EJSAA''' VAX 8820/8830/8840 Diagnostic Supervisor
* '''ELSAA''' VAX 6210/6220/6230/6240/6310/6320/6330/6340/6350/6360 Diagnostic Supervisor
* '''ENSAA''' VAX 725/730 Diagnostic Supervisor
* '''ESSAA''' VAX 780/785 Diagnostic Supervisor
* '''EXSAA''' VAX 6000 Diagnostic Supervisor
* '''EZSAA''' VAX 8530/8550/8700/8800/8820N Diagnostic Supervisor
* '''E?SAA''' VAX9000 Diagnostic Supervisor

There is no supervisor for the series of VAX 7000 / VAX 10000 computers (see: [http://www.vaxhaven.com/images/4/4d/EK-7001A-TS-001.pdf VAX 7000 Advanced Troubleshooting EK-7001A-TS-001])

== Set of Diagnostics for a SV-BXTAA VAX-11/750 System ==

A SV-BXTAA VAX-11/750 System consists of:

* [[KA750 CPU|VAX-11/750 CPU]]
* [[MS750 Memory System|MS750 1MB memory]]
* [[DECwriter IV|LA38 printing console terminal]]
* [[RH750 Massbus Adapter]]
* [[RM02/03 disk drive|RM03 MASSBUS disk drive subsystem]]
* [[DZ11 asynchronous serial line interface|DZ11 terminal adapter]]
* [[TS11 Subsystem|TS11 magnetic tape unit]]

The diagnostics set for this system is made of:

* CPU-specific diagnostic main program
** '''ECSAA''' VAX 11750 DIAG SUPERVISOR

* VAX-common automatic sizing program which automatically determines the current system configuration
** '''EVSBA''' VAX AUTOSIZER DIAGNOSTIC

* Set of VAX-11/750 CPU diagnostics
** '''ECKAA''' VAX 11750 UDIAG MON
** '''ECKAB''' VAX 11750 MICRO DPM
** '''ECKAC''' VAX 11750 MICRO MIC
** '''ECKAD''' VAX FP750 MICRODIAG
** '''ECKAF''' VAX KC750 UDIAG
** '''ECKAL''' VAX 11750 CACHE/TB DIAG
** '''ECKAM''' VAX 11750 MEMORY DIAG
** '''ECKAX''' VAX 11750 CLUSTER EXER

* VAX-common instruction set diagnostic
** '''EVKAA''' VAX INSTRUCTION SET TEST

* VAX-11/750 bus diagnostics
** '''ECCAA''' VAX 11750 RH750 DIAG
** '''ECCBA''' VAX 11750 UBI/DW750 DIAG

* Set of VAX-common peripheral diagnostics
** '''EVTAA''' VAX TERMINAL DIAGNOSTIC
** '''EVTBA''' VAX TERMINAL EXERCISER
** '''EVDAA''' VAX DZ11 8 LINE ASYNC MUX
** '''EVMAA''' VAX TM03/TE16/TU45-77 Tape
** '''EVRDA''' VAX RM03/RM05/RM80 DISKLESS
** '''EVRDB''' VAX RM03/RM05 FUNCTIONAL TEST

== Booting the VAX Diagnostic Supervisor ==

The command to boot the VAX Diagnostic Supervisor on a SIMH VAX is:

BOOT RQ0 /R5:10

* <code>RQ0</code> is the device identifier for the MSCP disk, unit 0, where the diagnostics are stored; adjust this according to your requirements.
* <code>/R5:10</code> is the boot flag to boot the Diagnostic Supervisor located in directory <code>DUA0:[SYSMAINT]</code> or <code>DUA0:[SYS0.SYSMAINT]</code>.

For booting the VAX Diagnostic Supervisor on a real VAX refer chapter 2.1 of the "'''VAX DS Diagnostic Supervisor User's Guide'''" [[#ref_1|[1]]]

== Sample run of the VDS EVSBA AUTOSIZER ==

DS> '''LOAD EVSBA.EXE'''
DS> '''SET FLAGS QUICK'''
DS> '''START /SECTION:MANUAL'''

.. Program: EVSBA - AUTOSIZER LEVEL 3, revision 5.1, 3 tests,
at 18:18:28.19.

COMMAND? '''HELP'''

HELP

This is a manual section command. This program creates ATTACH
commands for all devices in the system.
(ATTACH,CHANGE,EXIT,HELP,LIST,READ,SIZE,WRITE) - These commands
control the sizer in manual and selftest mode.
To obtain further information type HELP followed by a topic.
For example;
HELP MANUAL

Additional information available:

ATTACH CHANGE DEFAULT DEVICE EVENT
EXIT HELP LIST MANUAL QUICK
READ SECTION SELFTEST SCRIPT SIZE
SUMMARY WRITE

COMMAND? '''SIZE'''
COMMAND? '''LIST'''
FILE IN MEMORY 'CONFIG.COM'
!! AUTOMATIC SIZING PROGRAM.
!! THIS IS A TOOL AND NOT A DIAGNOSTIC PROGRAM.
!! CONFIGURATION FILE FOR SYSTEM.
!! COMPUTER GENERATED CPU TYPE 2 MICROCODE REV LEVEL = 99
!! NUMERIC VALUES WITH A LEADING ZERO ARE ASSIGNED.
!! FILE VALID ONLY FOR STANDARD HARDWARE CONFIGURATION.
!! TIME IS 15-FEB-1984 18:18:56.85
!!
!! *** QUICK FLAG SET. NO CHECKS MADE FOR TERMINALS ON DZ11/DZ32'S ***
!!
!!
!! DEFINE PROCESSOR...
!!
DS> ATTACH KA750 HUB KA0 YES YES YES 027FF 0
!!
!! DEFINE MEMORY...
!!
DS> ATTACH MS750 MS0
!!
!! DEFINE UNIBUS ADAPTERS...
!!
DS> ATTACH DW750 HUB DW0
!!
DS> ATTACH LP11 DW0 LPA 777514 0200 04
DS> ATTACH LP25 LPA LPA0 !! *** PRINTER TYPE IS ESTIMATED ***
DS> ATTACH TS11 DW0 MSA0 772520 0224 05
DS> ATTACH UDA50 DW0 DUA 772150 0154 05 02
DS> ATTACH RA81 DUA DUA0
DS> ATTACH RA60 DUA DJA2
DS> ATTACH RX50 DUA DUA3
DS> ATTACH DZ11 DW0 TTA 760100 0300 05 EIA
DS> ATTACH DZ11 DW0 TTB 760110 0310 05 EIA
DS> ATTACH DZ11 DW0 TTC 760120 0320 05 EIA
DS> ATTACH DZ11 DW0 TTD 760130 0330 05 EIA
COMMAND? '''WRITE'''
CONFIGURATION FILE IS NORMALLY READ/WRITTEN TO THE SUPERVISOR CONSOLE MEDIA
VERIFY SUPERVISOR CONSOLE MEDIA LOADED.
VERIFIED? [(Yes), No] '''YES'''
COMMAND? '''EXIT'''
DS>

== See also ==

* [[Running VDS Diagnostics on the SIMH VAX-11/750]]

== External links ==

This page contains condensed information from several DEC manuals, among others:

* [http://bitsavers.org/pdf/dec/vax/diag/EP-EVNDX-25.0_Oct86.txt EVNDX25 VAX DIAGNOSTIC INDEX]
* [https://vt100.net/mirror/hcps/si75fin1.pdf EK-SI75F-IN-001 VAX-11-750 Installation Manual] pdf-page 60ff
* <div id="ref_1">[1] [http://bitsavers.org/pdf/dec/vax/diag/VAX_Diagnostic_Supervisor_Users_Guide_Apr89.pdf AA-FK66A-TE VAX DS Diagnostic Supervisor User's Guide] </div>
* [http://bitsavers.org/pdf/dec/vax/diag/EK-1VAXD-TM-001_VAX_Diagnostic_Design_Guide_Aug79.pdf EK-1VAXD-TM-003 VAX Diagnostic Design Guide]
* [http://bitsavers.org/pdf/dec/vax/diag/AA-FK67A-TE_VAX_Diagnostic_Design_Guide_Apr89.pdf AA-FK67A-TE VAX Diagnostic Design Guide]
* [http://www.bitsavers.org/pdf/dec/vax/vms/1.5/2b/AA-D643A-TE_VAX_VMS_UETP_Users_Guide_Aug78.pdf AA-D643A-TE VAX/VMS UETP User’s Guide]
* [http://www.trailing-edge.com/~shoppa/11780diags/ VAX-11/780 Diagnostic Help Files]
* [https://manx-docs.org/collections/antonio/dec/MDS-2000-01/cd1/VAX/7001ATS1.PDF EK-7001A-TS-001 VAX 7000 Advanced Troubleshooting]

[[Category: VAX]]
[[Category: VAX Software]]
[[Category: VAX Diagnostic Software]]
[[Category: SIMH Tutorials]]
[[Category: VMS Practical Guides]]

VAX Diagnostic Supervisor

2025-11-12T18:35:56Z

Vaxorcist: /* Some useful VDS commands */ "SET LOAD disk:[directory]" added

VDS - '''VAX Diagnostic Supervisor''' (sometimes abbreviated to VAX/DS) is a set of diagnostic software programs for the [[DEC]] [[VAX]] computers and peripheral devices.

== Intro ==

'''''"At best, a computer is as good as its diagnostic tools!"'''''

That's what they must have thought at DEC when they developed their diagnostic software.

Here we will take a closer look at the VAX Diagnostic Supervisor and also a quick side look at the [[User Environment Test Package]] (UETP).

== Using VDS for simulated VAX Computers ==

You may ask: "What are the VAX diagnostics good for when run on a simulated VAX?"

Yes, many diagnostics do not run on a simulated VAX, but some work very well and are used e.g. for testing the various [[SIMH]] VAX simulators for correct execution of the VAX native mode instructions.

Furthermore you can explore how precise the simulation mimics the real hardware.

If you plan to test your real VAX, you can familiarize yourself with VDS and prepare your diagnosis in SIMH, and SIMH can assist you in preparing and creating a diagnostic kit on media appropriate for your VAX.

Automated testing script for a SIMH VAX-11/750:

SET CLOCK NOCALIBRATE=600K
ATTACH -RQ RQ0 VAX_MINIMUM_DIAGS.dsk
EXPECT "DS> " SEND "ATTACH UDA50 DW0 DUA 772150 154 5 10\r"; GO -Q
EXPECT "DS> " SEND "ATTACH RA81 DUA DUA0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH KA750 CMI KA0 yes yes yes 0 0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH DW750 CMI DW0 8\r"; GO -Q
EXPECT "DS> " SEND "SET LOAD DUA0:[SYSMAINT]\r"; GO -Q
EXPECT "DS> " SEND "SELECT KA0\r"; GO -Q
EXPECT "DS> " SEND "SET FLAGS TRACE\r"; GO -Q
EXPECT "DS> " SEND "RUN EVKAB\r"; GO -Q
BOOT -Q RQ0 /R5:10

== VDS History ==

VDS development began in parallel that to the first [[VAX]] model, the [[VAX-11/780]] in 1977.

VDS was provided soley for the '''''"big VAXen"''''' (i.e. not for the [[MicroVAX]] and [[VAXstation]] computers), with one remarkable exception, the [[MicroVAX I]], resp. [[VAXstation I]].
Each new VAX model received its CPU-specific VDS modules up to the [[VAX 9000]]; only the VAX models of the last two series, [[VAX 7000]] and [[VAX 10000]], were covered by other diagnostic methods.

== Program Levels ==

All VAX diagnostic programs are assigned to a '''level'''. Levels are numbered 1, 2R, 2, 3, 4, and 5. A program’s level indicates its run-time environment.

* '''Level 1''' diagnostic programs run under an operating system. They do not use the VAX/DS. (=> UETP)
* '''Level 2R''' diagnostic programs run under VAX/DS in user mode only.
* '''Level 2''' diagnostic programs run in both user mode and standalone mode, under the control of the VAX/DS.
* '''Level 3''' diagnostic programs run only in standalone mode, under the control of the VAX/DS.
* '''Level 4''' diagnostic programs run in standalone without VAX/DS.
* '''level 5''' diagnostic programs run in [[Writable Control Store|WCS]] or system console, not in VAX main memory. They do not use the VAX/DS.

Only the levels 2R, 2, and 3 are managed by VDS.

== Sections, Tests, Subtests, and Flags ==

All diagnostic programs that run under the VAX/DS are composed of one or more '''sections'''. Each section has a name, and it is possible to specify, by name, which section of the program to execute. A program section can have one of two functions, depending on its design:

* Test a certain major portion of the unit under test.
* Facilitate a certain mode of testing. For example, there might be a quick-verify section, used to give the device a quick (but not thorough) test.

In order to determine the number and names of the sections in a particular diagnostic program, use the <code>SHOW SECTIONS</code> command. However, every program contains a default section called <code>DEFAULT</code>, which will execute automatically if you do not specifically select a section. A section is selected with the <code>/SECTION</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Each section is composed of a set of '''tests'''; each test verifies either a particular function of the hardware or a particular subset of the component logic being tested. The VAX/DS allows you to specify which tests within a section to run. Each test may have some '''subtests'''. Tests are selected with the <code>/TEST</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Two sets of '''flags''' are provided to control certain aspects of a diagnostic program’s execution. These flags may be set or cleared before the diagnostic program is started.

One set of flags is called the '''VAX/DS control flags'''. The flags in this set are interpreted by the VAX/DS and their meanings are the same in all diagnostic programs. The VAX/DS control flags are set with the <code>SET FLAGS</code> command.

The other set of flags is referred to as the '''event flags'''. This set consists of 23 flags whose purposes are defined by the diagnostic programs. The user must read the documentation for specific diagnostic programs to determine if a definition has been assigned to any of the event flags. <code>SET EVENT FLAGS</code> command.

== Some useful VDS commands ==

* <code>'''SET LOAD disk:[directory]'''</code> Set diagnostic load path
* <code>'''LOAD''' Exxxx</code> Load diagnostic Exxxx (where "Exxxx" is replaced by the diagnostics name, e.g. EVKAA)
* <code>'''SET TRACE'''</code> Show progress
* <code>'''SHOW FLAGS'''</code> Show VDS flags
* <code>'''SHOW TESTS'''</code> Show the available tests of the loaded diagnostic
* <code>'''SHOW SECTIONS'''</code> Show the available sections of the loaded diagnostic
* <code>'''START/TEST='''first:last</code> Start a subset of the loaded diagnostics tests (where "first" is the test number to start with, and -optionally- "last" is the last one to execute)
* <code>'''START/SECTION='''section-name</code> Start a single section of the loaded diagnostic (where "section-name" is the name of the section to run)
* <code>'''START/PASSES='''count</code> Start the loaded diagnostic for "count" passes (where "count" is the number of passes to execute)
* <code>'''RUN''' exxxx'''/TEST='''first:last</code> Run a subset of the diagnostics tests
* <code>'''RUN''' exxxx'''/SECTION='''section-name</code> Run a single section of the diagnostic
* <code>'''RUN''' exxxx'''/PASSES='''count</code> Run the diagnostic for "count" passes

Use a pass count of 0 to run a program continuously. If you do this, the program will run until you type CTRL/C or a failure occurs with the HALT flag set.

== Diagnostic Program Documentation ==

Documentation provided for each diagnostic program includes:

* '''Help file'''
:: The help file is referenced with the HELP command. It contains any operating instructions that may be unique to the diagnostic program. The help file for diagnostic program EVXYZ is EVXYZ.HLP; the help file for the VAX/DS is EVSAA.HLP

* '''Documentation file'''
:: The documentation file provides a detailed description of a diagnostic program's function, run-time requirements, operating instructions, fault detection, and maintenance history, plus explanations of each test’s function and execution flow. The documentation file for diagnostic program EVXYZ is EVXYZ.DOC.

* '''Source Code listings'''
:: Source code listings of the diagnostic programs are available. All VAX/DS diagnostic programs are structured in a standard format. For example, the initialization code for every diagnostic program is always located in the same relative area within the listing. To fully understand the source code listings of a VAX/DS diagnostic program, refer to the VAX Diagnostic Design Guide.

The help file for a diagnostic program is shipped with the diagnostic program. The documentation file and source codelistings are available by ordering a [[Maintenance Documentation Service]] Option on microfiche.

== Diagnostic Scopes ==

There are two diagnostic scopes.

* A CPU-specific scope: '''CPU Cluster Testing'''
* A scope for the identical diagnostic programs for all types of VAX computers: '''Peripheral Diagnostics'''

=== CPU Cluster Testing ===

'''NOTE: The term "CPU cluster" used here means all components belonging to a CPU; there is no connection with the term [[VAXcluster|"VAXcluster" (alternatively: "VMScluster")]].'''

The VAX CPU cluster is tested by a set of programs, existing at several program levels, as follows:

* Level 5
** Console tests
** Processor tests
** Memory tests
* Level 4
** VAX instruction set test (hardcore for VDS)
** Cache and translation buffer tests (VAX-11/750 only)
* Level 3
** Memory tests (if no level 5 test possible)
** Channel adapter tests
** Cluster exerciser

'''NOTE: The term "Channel adapter" used here means bus adapter, e.g. for [[UNIBUS]] or [[MASSBUS]].'''

This set of programs implements the VAX diagnostic strategy by providing a set of building blocks by which a system may be tested, starting with the level 5 basic processor tests and ending with the level 3 cluster exerciser, which is a program meant to exercise all components of the cluster.

=== Peripheral Diagnostics ===

Thorough testing of a peripheral device requires the development of three different diagnostic programs. For each device type the following will typically (but not necessarily) exist:

* A level 3 logic test
* A level 3 function test
* A level 2R function test

This group of programs implements the diagnostic strategy by providing a facility for producing very accurate and detailed identifications of fault conditions via the level 3 programs and by also providing a method by which the device may be tested without bringing down the customer's operating system via the level 2R program.

The level 3 logic test will provide the greatest detail of error resolution, indicating which section of logic is failing. This program will be used by technicians to repair bad logic boards, and will provide very high test coverage. Some devices contain ROM-resident microprograms ("self-tests") that perform logic testing, making a level 3 logic test unnecessary.

The level 3 function test will provide a comprehensive test of all of the device’s functions. This program will be used to determine accurately whether or not a device is operating correctly. This is the definitive function test and provides very high test coverage. Level 3 function tests are usually required even if the device possesses self-testing capabilities, because self-tests generally are not capable of complete detection of function failures.

The level 2R program will typically consist of a subset of the level 3 function test. It will test as much of the device’s functionality as can be tested in the user (VMS) environment. The tests it contains are exact or approximate copies of tests existing in the level 3 program.

A typical sequence of use for these programs, when dealing with a system at a customer site, is as follows:

# The customer (or field service) suspects a fault existing in the device.
# The level 2R program is run to see if the error can be detected without stopping the operating system. If the error is found, go to step 4.
# If the level 2R program cannot identify the fault, the operating system is brought down and the level 3 function test is run.
# The fault is identified and the failing [[Field Replacable Unit|FRU]] is replaced. The operating system is then brought back up.
# The failing FRU is brought back to DIGITAL, where the level 3 logic test, the level 3 function test, or perhaps a module test station is used to identify the failing logic on the FRU. The FRU is repaired.

== VAX Diagnostic Coding Convention ==

VAX diagnostic program names consist of 5 letters and a two-digit version number, e.g.: ECKAL-3.4:

* E = VAX
* C = 11/750
* K = CPU
* A = Supervisor
* L = Unique identifier
* 3 = Major revision
* 4 = Minor Revision

See the following 1986 VAX Diagnostic Coding Convention Table for letter breakdown:

EPXYD-R.P

E = System

E = VAX

P = Processor

B = VAX 8200/8300
D = VAX 8600
S = VAX 11780
T = VAX 11785
C = VAX 11750
N = VAX 11730 and 11725
H = MicroVAX I
J = VAX 8820/8830/8840
V = More than one VAX Processor
X = VAX 6000
Z = VAX 8530/8550/8700/8800

X = Device Category

A = Application (CR, LP, A-D, Misc.)
C = Channel Adaptors (MBA, UBA)
D = Communication Devices (DMC, DZ11)
G = CI Adapter
K = CPU
L = Database Files
M = Magnetic Tape (TE, TU, DT)
P = Test Equipment
Q = QIO Device Driver
R = Rotating Memory (RP, RK, RM, RS, RX)
S = System Monitor (Supervisor, Tape Monitor)
T = Terminal (LA36, VT52)
U = Utilities (Script file, Copy, Update)
W = Workstations
X = System Exerciser (EXR/BUSINT)
Z = Media Packages
0-9 = Engineering File

Y = Device Type

Category Application
A = Line Printers, LP, LCP01
B = Card Readers, CR
L = LPA11-K
Category Channel
A = MBA
B = UBA, DWBUA
C = MA780
D = IEC11, IEU11-A, DR70
E = DT07
F = DEC DATAWAY
G = CI780
H = CI750/CI780 MICROCODE VERIFICATION (INTERNAL)
I = TEST BED ADAPTERS
J = NBI ADAPTER
K = CIBCI

Category Communications
A = DZ11,DZ32,DMZ32,DHU11,DMB32
B = DMC
C = Multiple Devices
D = DR11-C
E = DV11
F = DR780,DF11-W
G = DQS11
H = KMC11-B
I = KMS11-B
J = DM11-BA
K = DMS11-BA
L = DMF32 Combo
M = DMC11,DMR11,DMP11
N = DN11
O = CPI32
P = PCL11
R = DR11B,DR11-W,DRE11
S = DRS11/DSS
T = KCT32-A,FEPCM
U = DUP11
X = Multiple Devices
W = UNA
Y = DEBNT

Category Database Files
A = CRD DATABASE FILES
B = SYSTEM EXERCISER DATABASE FILES

Category Magnetic Tape
A = TE16/77, TS11, TU78, TS05
B = TU81,TU80

Category QIO Device Drivers
For this category, the fourth and fifth letters of the code are the device mnemonic.
For example, EVQDB is the QIO device driver for the DB, or RP disk series.

Category Test Equipment
A = CI780 Node Tester
B = NI Tester

Category Rotating Memory
A = Multiple devices
B = RP04/5/6
C = DCL/RP04/5/6
D = RM03/RM05/RM80
E = RK611,RK06,RK07
F = RL02
G = RM80
H = RP07
I = RX02
J = ML11
K = IDC
L = UDA50(RA60,RA80,RA81)
M = RC25
N = RUX50

Category System Monitor
A = Supervisor
B = Autosizer
C = DYDDM

Category Terminals
A = All Terminals
B = Terminal exerciser
C = VS11
D = 11C03-LH Fastek
G = VS70

Category Utility
A = Script File
B = Copy Command file
C = Updating file

Category Workstation
A = VS100

Category Exerciser
B = Exerciser Bus Interaction

D = Fifth character makes the code unique. A through Z and 1 through 9.

R = Revision (MAJOR)
P = Revision (MINOR)

== Distribution of Diagnostic Programs ==

Typically, a VAX computer came with all the necessary diagnostic programs on console media at no additional charge, e.g.:

* VAX-11/780: [[RX01/02 floppy drive|RX01 floppies]]
* VAX-11/750, VAX-11/730, and VAX-11/725: [[TU58 DECtape II|TU58 cartridges]]
* VAX 8600: [[RL01/02 disk drive|RL02 disk pack]]
* VAX 8200, VAX 8250, VAX 8300, and VAX 8350: [[RX50 dual-diskette drive|RX50 floppies]]

Additionally, you could buy larger collections of diagnostic programs on [[magnetic tape]] or [[Removable-pack disk|removable disk packs]].

Extended documentation was available on microfiche at an extra charge.

== VMS User Enviroment Test Package (UETP) ==

From the very beginning of VMS V1.0 there was the '''[[User Enviroment Test Package]]''' (UETP), see: [http://bitsavers.trailing-edge.com/pdf/dec/vax/vms/2.0/AA-D643B-TE_VAX-VMS_2.0_UETP_Users_Guide_198003.pdf VAX/VMS UETP User’s Guide AA-D643A-TE]

Quote from the first UETP manual:

"''The UETP is a collection of tests designed to demonstrate that the hardware and software components of a VAX/VMS system are in working order. DIGITAL software support representatives run the UETP on a newly installed VAX/VMS system as the formal sample procedure.''"

UETP is still used in the latest version of VMS (V9.2-2 for x86 as of this writing).

[https://docs.vmssoftware.com/vsi-openvms-system-manager-s-manual-volume-2-tuning-monitoring-and-complex-systems/#_6017UETP| See here] for the latest VMS UETP manual.

== ULTRIX System Exerciser Package ==

[[ULTRIX]] has got a very similar tool to verify proper hardware operation at the operating system level, the '''[[System Exerciser Package]]'''.

For the earliest reference found so far see the manual: [https://drive.google.com/file/d/1i3LoLAvTQC7dZl-T9X3SsQgg_6s_6TCY/view?usp=sharing ULTRIX-32 2.2 System Exercisers 1987 AA-KS95A-TE]

The MIPS variants of ULTRIX include the System Exerciser Package, too.

== Additional Diagnostic Tools ==

* On-board ROM-based diagnostics (RBDs) / Self-tests
* [[Diagnostic and Utility Protocol|DUP]] for [[Mass Storage Control Protocol|MSCP]] devices

== CPU-specific Supervisors ==

* '''EBSAA''' VAX 8200/8250/8300/8350 & VS8000 Diagnostic Supervisor
* '''ECSAA''' VAX-11/750 DIAGNOSTIC SUPERVISOR
* '''EDSAA''' VAX 8600/8650 Diagnostic Supervisor
* '''EHSAA''' MicroVAX I VDS
* '''EJSAA''' VAX 8820/8830/8840 Diagnostic Supervisor
* '''ELSAA''' VAX 6210/6220/6230/6240/6310/6320/6330/6340/6350/6360 Diagnostic Supervisor
* '''ENSAA''' VAX 725/730 Diagnostic Supervisor
* '''ESSAA''' VAX 780/785 Diagnostic Supervisor
* '''EXSAA''' VAX 6000 Diagnostic Supervisor
* '''EZSAA''' VAX 8530/8550/8700/8800/8820N Diagnostic Supervisor
* '''E?SAA''' VAX9000 Diagnostic Supervisor

There is no supervisor for the series of VAX 7000 / VAX 10000 computers (see: [http://www.vaxhaven.com/images/4/4d/EK-7001A-TS-001.pdf VAX 7000 Advanced Troubleshooting EK-7001A-TS-001])

== Set of Diagnostics for a SV-BXTAA VAX-11/750 System ==

A SV-BXTAA VAX-11/750 System consists of:

* [[KA750 CPU|VAX-11/750 CPU]]
* [[MS750 Memory System|MS750 1MB memory]]
* [[DECwriter IV|LA38 printing console terminal]]
* [[RH750 Massbus Adapter]]
* [[RM02/03 disk drive|RM03 MASSBUS disk drive subsystem]]
* [[DZ11 asynchronous serial line interface|DZ11 terminal adapter]]
* [[TS11 Subsystem|TS11 magnetic tape unit]]

The diagnostics set for this system is made of:

* CPU-specific diagnostic main program
** '''ECSAA''' VAX 11750 DIAG SUPERVISOR

* VAX-common automatic sizing program which automatically determines the current system configuration
** '''EVSBA''' VAX AUTOSIZER DIAGNOSTIC

* Set of VAX-11/750 CPU diagnostics
** '''ECKAA''' VAX 11750 UDIAG MON
** '''ECKAB''' VAX 11750 MICRO DPM
** '''ECKAC''' VAX 11750 MICRO MIC
** '''ECKAD''' VAX FP750 MICRODIAG
** '''ECKAF''' VAX KC750 UDIAG
** '''ECKAL''' VAX 11750 CACHE/TB DIAG
** '''ECKAM''' VAX 11750 MEMORY DIAG
** '''ECKAX''' VAX 11750 CLUSTER EXER

* VAX-common instruction set diagnostic
** '''EVKAA''' VAX INSTRUCTION SET TEST

* VAX-11/750 bus diagnostics
** '''ECCAA''' VAX 11750 RH750 DIAG
** '''ECCBA''' VAX 11750 UBI/DW750 DIAG

* Set of VAX-common peripheral diagnostics
** '''EVTAA''' VAX TERMINAL DIAGNOSTIC
** '''EVTBA''' VAX TERMINAL EXERCISER
** '''EVDAA''' VAX DZ11 8 LINE ASYNC MUX
** '''EVMAA''' VAX TM03/TE16/TU45-77 Tape
** '''EVRDA''' VAX RM03/RM05/RM80 DISKLESS
** '''EVRDB''' VAX RM03/RM05 FUNCTIONAL TEST

== Booting the VAX Diagnostic Supervisor ==

The command to boot the VAX Diagnostic Supervisor on a SIMH VAX is:

BOOT RQ0 /R5:10

* <code>RQ0</code> is the device identifier for the MSCP disk, unit 0, where the diagnostics are stored; adjust this according to your requirements.
* <code>/R5:10</code> is the boot flag to boot the Diagnostic Supervisor located in directory <code>DUA0:[SYSMAINT]</code> or <code>DUA0:[SYS0.SYSMAINT]</code>.

For booting the VAX Diagnostic Supervisor on a real VAX refer chapter 2.1 of the "'''VAX DS Diagnostic Supervisor User's Guide'''" [[#ref_1|[1]]]

== Sample run of the VDS EVSBA AUTOSIZER ==

DS> '''LOAD EVSBA.EXE'''
DS> '''SET FLAGS QUICK'''
DS> '''START /SECTION:MANUAL'''

.. Program: EVSBA - AUTOSIZER LEVEL 3, revision 5.1, 3 tests,
at 18:18:28.19.

COMMAND? '''HELP'''

HELP

This is a manual section command. This program creates ATTACH
commands for all devices in the system.
(ATTACH,CHANGE,EXIT,HELP,LIST,READ,SIZE,WRITE) - These commands
control the sizer in manual and selftest mode.
To obtain further information type HELP followed by a topic.
For example;
HELP MANUAL

Additional information available:

ATTACH CHANGE DEFAULT DEVICE EVENT
EXIT HELP LIST MANUAL QUICK
READ SECTION SELFTEST SCRIPT SIZE
SUMMARY WRITE

COMMAND? '''SIZE'''
COMMAND? '''LIST'''
FILE IN MEMORY 'CONFIG.COM'
!! AUTOMATIC SIZING PROGRAM.
!! THIS IS A TOOL AND NOT A DIAGNOSTIC PROGRAM.
!! CONFIGURATION FILE FOR SYSTEM.
!! COMPUTER GENERATED CPU TYPE 2 MICROCODE REV LEVEL = 99
!! NUMERIC VALUES WITH A LEADING ZERO ARE ASSIGNED.
!! FILE VALID ONLY FOR STANDARD HARDWARE CONFIGURATION.
!! TIME IS 15-FEB-1984 18:18:56.85
!!
!! *** QUICK FLAG SET. NO CHECKS MADE FOR TERMINALS ON DZ11/DZ32'S ***
!!
!!
!! DEFINE PROCESSOR...
!!
DS> ATTACH KA750 HUB KA0 YES YES YES 027FF 0
!!
!! DEFINE MEMORY...
!!
DS> ATTACH MS750 MS0
!!
!! DEFINE UNIBUS ADAPTERS...
!!
DS> ATTACH DW750 HUB DW0
!!
DS> ATTACH LP11 DW0 LPA 777514 0200 04
DS> ATTACH LP25 LPA LPA0 !! *** PRINTER TYPE IS ESTIMATED ***
DS> ATTACH TS11 DW0 MSA0 772520 0224 05
DS> ATTACH UDA50 DW0 DUA 772150 0154 05 02
DS> ATTACH RA81 DUA DUA0
DS> ATTACH RA60 DUA DJA2
DS> ATTACH RX50 DUA DUA3
DS> ATTACH DZ11 DW0 TTA 760100 0300 05 EIA
DS> ATTACH DZ11 DW0 TTB 760110 0310 05 EIA
DS> ATTACH DZ11 DW0 TTC 760120 0320 05 EIA
DS> ATTACH DZ11 DW0 TTD 760130 0330 05 EIA
COMMAND? '''WRITE'''
CONFIGURATION FILE IS NORMALLY READ/WRITTEN TO THE SUPERVISOR CONSOLE MEDIA
VERIFY SUPERVISOR CONSOLE MEDIA LOADED.
VERIFIED? [(Yes), No] '''YES'''
COMMAND? '''EXIT'''
DS>

== See also ==

* [[Running VDS Diagnostics on the SIMH VAX-11/750]]

== External links ==

This page contains condensed information from several DEC manuals, among others:

* [http://bitsavers.org/pdf/dec/vax/diag/EP-EVNDX-25.0_Oct86.txt EVNDX25 VAX DIAGNOSTIC INDEX]
* [https://vt100.net/mirror/hcps/si75fin1.pdf EK-SI75F-IN-001 VAX-11-750 Installation Manual] pdf-page 60ff
* <div id="ref_1">[1] [http://bitsavers.org/pdf/dec/vax/diag/VAX_Diagnostic_Supervisor_Users_Guide_Apr89.pdf AA-FK66A-TE VAX DS Diagnostic Supervisor User's Guide] </div>
* [http://bitsavers.org/pdf/dec/vax/diag/EK-1VAXD-TM-001_VAX_Diagnostic_Design_Guide_Aug79.pdf EK-1VAXD-TM-003 VAX Diagnostic Design Guide]
* [http://bitsavers.org/pdf/dec/vax/diag/AA-FK67A-TE_VAX_Diagnostic_Design_Guide_Apr89.pdf AA-FK67A-TE VAX Diagnostic Design Guide]
* [http://www.bitsavers.org/pdf/dec/vax/vms/1.5/2b/AA-D643A-TE_VAX_VMS_UETP_Users_Guide_Aug78.pdf AA-D643A-TE VAX/VMS UETP User’s Guide]
* [http://www.trailing-edge.com/~shoppa/11780diags/ VAX-11/780 Diagnostic Help Files]
* [https://manx-docs.org/collections/antonio/dec/MDS-2000-01/cd1/VAX/7001ATS1.PDF EK-7001A-TS-001 VAX 7000 Advanced Troubleshooting]

[[Category: VAX]]
[[Category: VAX Software]]
[[Category: VAX Diagnostic Software]]
[[Category: SIMH Tutorials]]
[[Category: VMS Practical Guides]]

VAX Diagnostic Supervisor

2025-11-12T18:33:59Z

Vaxorcist: /* Some useful VDS commands */ "SET TRACE" added

VDS - '''VAX Diagnostic Supervisor''' (sometimes abbreviated to VAX/DS) is a set of diagnostic software programs for the [[DEC]] [[VAX]] computers and peripheral devices.

== Intro ==

'''''"At best, a computer is as good as its diagnostic tools!"'''''

That's what they must have thought at DEC when they developed their diagnostic software.

Here we will take a closer look at the VAX Diagnostic Supervisor and also a quick side look at the [[User Environment Test Package]] (UETP).

== Using VDS for simulated VAX Computers ==

You may ask: "What are the VAX diagnostics good for when run on a simulated VAX?"

Yes, many diagnostics do not run on a simulated VAX, but some work very well and are used e.g. for testing the various [[SIMH]] VAX simulators for correct execution of the VAX native mode instructions.

Furthermore you can explore how precise the simulation mimics the real hardware.

If you plan to test your real VAX, you can familiarize yourself with VDS and prepare your diagnosis in SIMH, and SIMH can assist you in preparing and creating a diagnostic kit on media appropriate for your VAX.

Automated testing script for a SIMH VAX-11/750:

SET CLOCK NOCALIBRATE=600K
ATTACH -RQ RQ0 VAX_MINIMUM_DIAGS.dsk
EXPECT "DS> " SEND "ATTACH UDA50 DW0 DUA 772150 154 5 10\r"; GO -Q
EXPECT "DS> " SEND "ATTACH RA81 DUA DUA0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH KA750 CMI KA0 yes yes yes 0 0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH DW750 CMI DW0 8\r"; GO -Q
EXPECT "DS> " SEND "SET LOAD DUA0:[SYSMAINT]\r"; GO -Q
EXPECT "DS> " SEND "SELECT KA0\r"; GO -Q
EXPECT "DS> " SEND "SET FLAGS TRACE\r"; GO -Q
EXPECT "DS> " SEND "RUN EVKAB\r"; GO -Q
BOOT -Q RQ0 /R5:10

== VDS History ==

VDS development began in parallel that to the first [[VAX]] model, the [[VAX-11/780]] in 1977.

VDS was provided soley for the '''''"big VAXen"''''' (i.e. not for the [[MicroVAX]] and [[VAXstation]] computers), with one remarkable exception, the [[MicroVAX I]], resp. [[VAXstation I]].
Each new VAX model received its CPU-specific VDS modules up to the [[VAX 9000]]; only the VAX models of the last two series, [[VAX 7000]] and [[VAX 10000]], were covered by other diagnostic methods.

== Program Levels ==

All VAX diagnostic programs are assigned to a '''level'''. Levels are numbered 1, 2R, 2, 3, 4, and 5. A program’s level indicates its run-time environment.

* '''Level 1''' diagnostic programs run under an operating system. They do not use the VAX/DS. (=> UETP)
* '''Level 2R''' diagnostic programs run under VAX/DS in user mode only.
* '''Level 2''' diagnostic programs run in both user mode and standalone mode, under the control of the VAX/DS.
* '''Level 3''' diagnostic programs run only in standalone mode, under the control of the VAX/DS.
* '''Level 4''' diagnostic programs run in standalone without VAX/DS.
* '''level 5''' diagnostic programs run in [[Writable Control Store|WCS]] or system console, not in VAX main memory. They do not use the VAX/DS.

Only the levels 2R, 2, and 3 are managed by VDS.

== Sections, Tests, Subtests, and Flags ==

All diagnostic programs that run under the VAX/DS are composed of one or more '''sections'''. Each section has a name, and it is possible to specify, by name, which section of the program to execute. A program section can have one of two functions, depending on its design:

* Test a certain major portion of the unit under test.
* Facilitate a certain mode of testing. For example, there might be a quick-verify section, used to give the device a quick (but not thorough) test.

In order to determine the number and names of the sections in a particular diagnostic program, use the <code>SHOW SECTIONS</code> command. However, every program contains a default section called <code>DEFAULT</code>, which will execute automatically if you do not specifically select a section. A section is selected with the <code>/SECTION</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Each section is composed of a set of '''tests'''; each test verifies either a particular function of the hardware or a particular subset of the component logic being tested. The VAX/DS allows you to specify which tests within a section to run. Each test may have some '''subtests'''. Tests are selected with the <code>/TEST</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Two sets of '''flags''' are provided to control certain aspects of a diagnostic program’s execution. These flags may be set or cleared before the diagnostic program is started.

One set of flags is called the '''VAX/DS control flags'''. The flags in this set are interpreted by the VAX/DS and their meanings are the same in all diagnostic programs. The VAX/DS control flags are set with the <code>SET FLAGS</code> command.

The other set of flags is referred to as the '''event flags'''. This set consists of 23 flags whose purposes are defined by the diagnostic programs. The user must read the documentation for specific diagnostic programs to determine if a definition has been assigned to any of the event flags. <code>SET EVENT FLAGS</code> command.

== Some useful VDS commands ==

* <code>'''LOAD''' Exxxx</code> Load diagnostic Exxxx (where "Exxxx" is replaced by the diagnostics name, e.g. EVKAA)
* <code>'''SET TRACE'''</code> Show progress
* <code>'''SHOW FLAGS'''</code> Show VDS flags
* <code>'''SHOW TESTS'''</code> Show the available tests of the loaded diagnostic
* <code>'''SHOW SECTIONS'''</code> Show the available sections of the loaded diagnostic
* <code>'''START/TEST='''first:last</code> Start a subset of the loaded diagnostics tests (where "first" is the test number to start with, and -optionally- "last" is the last one to execute)
* <code>'''START/SECTION='''section-name</code> Start a single section of the loaded diagnostic (where "section-name" is the name of the section to run)
* <code>'''START/PASSES='''count</code> Start the loaded diagnostic for "count" passes (where "count" is the number of passes to execute)
* <code>'''RUN''' exxxx'''/TEST='''first:last</code> Run a subset of the diagnostics tests
* <code>'''RUN''' exxxx'''/SECTION='''section-name</code> Run a single section of the diagnostic
* <code>'''RUN''' exxxx'''/PASSES='''count</code> Run the diagnostic for "count" passes

Use a pass count of 0 to run a program continuously. If you do this, the program will run until you type CTRL/C or a failure occurs with the HALT flag set.

== Diagnostic Program Documentation ==

Documentation provided for each diagnostic program includes:

* '''Help file'''
:: The help file is referenced with the HELP command. It contains any operating instructions that may be unique to the diagnostic program. The help file for diagnostic program EVXYZ is EVXYZ.HLP; the help file for the VAX/DS is EVSAA.HLP

* '''Documentation file'''
:: The documentation file provides a detailed description of a diagnostic program's function, run-time requirements, operating instructions, fault detection, and maintenance history, plus explanations of each test’s function and execution flow. The documentation file for diagnostic program EVXYZ is EVXYZ.DOC.

* '''Source Code listings'''
:: Source code listings of the diagnostic programs are available. All VAX/DS diagnostic programs are structured in a standard format. For example, the initialization code for every diagnostic program is always located in the same relative area within the listing. To fully understand the source code listings of a VAX/DS diagnostic program, refer to the VAX Diagnostic Design Guide.

The help file for a diagnostic program is shipped with the diagnostic program. The documentation file and source codelistings are available by ordering a [[Maintenance Documentation Service]] Option on microfiche.

== Diagnostic Scopes ==

There are two diagnostic scopes.

* A CPU-specific scope: '''CPU Cluster Testing'''
* A scope for the identical diagnostic programs for all types of VAX computers: '''Peripheral Diagnostics'''

=== CPU Cluster Testing ===

'''NOTE: The term "CPU cluster" used here means all components belonging to a CPU; there is no connection with the term [[VAXcluster|"VAXcluster" (alternatively: "VMScluster")]].'''

The VAX CPU cluster is tested by a set of programs, existing at several program levels, as follows:

* Level 5
** Console tests
** Processor tests
** Memory tests
* Level 4
** VAX instruction set test (hardcore for VDS)
** Cache and translation buffer tests (VAX-11/750 only)
* Level 3
** Memory tests (if no level 5 test possible)
** Channel adapter tests
** Cluster exerciser

'''NOTE: The term "Channel adapter" used here means bus adapter, e.g. for [[UNIBUS]] or [[MASSBUS]].'''

This set of programs implements the VAX diagnostic strategy by providing a set of building blocks by which a system may be tested, starting with the level 5 basic processor tests and ending with the level 3 cluster exerciser, which is a program meant to exercise all components of the cluster.

=== Peripheral Diagnostics ===

Thorough testing of a peripheral device requires the development of three different diagnostic programs. For each device type the following will typically (but not necessarily) exist:

* A level 3 logic test
* A level 3 function test
* A level 2R function test

This group of programs implements the diagnostic strategy by providing a facility for producing very accurate and detailed identifications of fault conditions via the level 3 programs and by also providing a method by which the device may be tested without bringing down the customer's operating system via the level 2R program.

The level 3 logic test will provide the greatest detail of error resolution, indicating which section of logic is failing. This program will be used by technicians to repair bad logic boards, and will provide very high test coverage. Some devices contain ROM-resident microprograms ("self-tests") that perform logic testing, making a level 3 logic test unnecessary.

The level 3 function test will provide a comprehensive test of all of the device’s functions. This program will be used to determine accurately whether or not a device is operating correctly. This is the definitive function test and provides very high test coverage. Level 3 function tests are usually required even if the device possesses self-testing capabilities, because self-tests generally are not capable of complete detection of function failures.

The level 2R program will typically consist of a subset of the level 3 function test. It will test as much of the device’s functionality as can be tested in the user (VMS) environment. The tests it contains are exact or approximate copies of tests existing in the level 3 program.

A typical sequence of use for these programs, when dealing with a system at a customer site, is as follows:

# The customer (or field service) suspects a fault existing in the device.
# The level 2R program is run to see if the error can be detected without stopping the operating system. If the error is found, go to step 4.
# If the level 2R program cannot identify the fault, the operating system is brought down and the level 3 function test is run.
# The fault is identified and the failing [[Field Replacable Unit|FRU]] is replaced. The operating system is then brought back up.
# The failing FRU is brought back to DIGITAL, where the level 3 logic test, the level 3 function test, or perhaps a module test station is used to identify the failing logic on the FRU. The FRU is repaired.

== VAX Diagnostic Coding Convention ==

VAX diagnostic program names consist of 5 letters and a two-digit version number, e.g.: ECKAL-3.4:

* E = VAX
* C = 11/750
* K = CPU
* A = Supervisor
* L = Unique identifier
* 3 = Major revision
* 4 = Minor Revision

See the following 1986 VAX Diagnostic Coding Convention Table for letter breakdown:

EPXYD-R.P

E = System

E = VAX

P = Processor

B = VAX 8200/8300
D = VAX 8600
S = VAX 11780
T = VAX 11785
C = VAX 11750
N = VAX 11730 and 11725
H = MicroVAX I
J = VAX 8820/8830/8840
V = More than one VAX Processor
X = VAX 6000
Z = VAX 8530/8550/8700/8800

X = Device Category

A = Application (CR, LP, A-D, Misc.)
C = Channel Adaptors (MBA, UBA)
D = Communication Devices (DMC, DZ11)
G = CI Adapter
K = CPU
L = Database Files
M = Magnetic Tape (TE, TU, DT)
P = Test Equipment
Q = QIO Device Driver
R = Rotating Memory (RP, RK, RM, RS, RX)
S = System Monitor (Supervisor, Tape Monitor)
T = Terminal (LA36, VT52)
U = Utilities (Script file, Copy, Update)
W = Workstations
X = System Exerciser (EXR/BUSINT)
Z = Media Packages
0-9 = Engineering File

Y = Device Type

Category Application
A = Line Printers, LP, LCP01
B = Card Readers, CR
L = LPA11-K
Category Channel
A = MBA
B = UBA, DWBUA
C = MA780
D = IEC11, IEU11-A, DR70
E = DT07
F = DEC DATAWAY
G = CI780
H = CI750/CI780 MICROCODE VERIFICATION (INTERNAL)
I = TEST BED ADAPTERS
J = NBI ADAPTER
K = CIBCI

Category Communications
A = DZ11,DZ32,DMZ32,DHU11,DMB32
B = DMC
C = Multiple Devices
D = DR11-C
E = DV11
F = DR780,DF11-W
G = DQS11
H = KMC11-B
I = KMS11-B
J = DM11-BA
K = DMS11-BA
L = DMF32 Combo
M = DMC11,DMR11,DMP11
N = DN11
O = CPI32
P = PCL11
R = DR11B,DR11-W,DRE11
S = DRS11/DSS
T = KCT32-A,FEPCM
U = DUP11
X = Multiple Devices
W = UNA
Y = DEBNT

Category Database Files
A = CRD DATABASE FILES
B = SYSTEM EXERCISER DATABASE FILES

Category Magnetic Tape
A = TE16/77, TS11, TU78, TS05
B = TU81,TU80

Category QIO Device Drivers
For this category, the fourth and fifth letters of the code are the device mnemonic.
For example, EVQDB is the QIO device driver for the DB, or RP disk series.

Category Test Equipment
A = CI780 Node Tester
B = NI Tester

Category Rotating Memory
A = Multiple devices
B = RP04/5/6
C = DCL/RP04/5/6
D = RM03/RM05/RM80
E = RK611,RK06,RK07
F = RL02
G = RM80
H = RP07
I = RX02
J = ML11
K = IDC
L = UDA50(RA60,RA80,RA81)
M = RC25
N = RUX50

Category System Monitor
A = Supervisor
B = Autosizer
C = DYDDM

Category Terminals
A = All Terminals
B = Terminal exerciser
C = VS11
D = 11C03-LH Fastek
G = VS70

Category Utility
A = Script File
B = Copy Command file
C = Updating file

Category Workstation
A = VS100

Category Exerciser
B = Exerciser Bus Interaction

D = Fifth character makes the code unique. A through Z and 1 through 9.

R = Revision (MAJOR)
P = Revision (MINOR)

== Distribution of Diagnostic Programs ==

Typically, a VAX computer came with all the necessary diagnostic programs on console media at no additional charge, e.g.:

* VAX-11/780: [[RX01/02 floppy drive|RX01 floppies]]
* VAX-11/750, VAX-11/730, and VAX-11/725: [[TU58 DECtape II|TU58 cartridges]]
* VAX 8600: [[RL01/02 disk drive|RL02 disk pack]]
* VAX 8200, VAX 8250, VAX 8300, and VAX 8350: [[RX50 dual-diskette drive|RX50 floppies]]

Additionally, you could buy larger collections of diagnostic programs on [[magnetic tape]] or [[Removable-pack disk|removable disk packs]].

Extended documentation was available on microfiche at an extra charge.

== VMS User Enviroment Test Package (UETP) ==

From the very beginning of VMS V1.0 there was the '''[[User Enviroment Test Package]]''' (UETP), see: [http://bitsavers.trailing-edge.com/pdf/dec/vax/vms/2.0/AA-D643B-TE_VAX-VMS_2.0_UETP_Users_Guide_198003.pdf VAX/VMS UETP User’s Guide AA-D643A-TE]

Quote from the first UETP manual:

"''The UETP is a collection of tests designed to demonstrate that the hardware and software components of a VAX/VMS system are in working order. DIGITAL software support representatives run the UETP on a newly installed VAX/VMS system as the formal sample procedure.''"

UETP is still used in the latest version of VMS (V9.2-2 for x86 as of this writing).

[https://docs.vmssoftware.com/vsi-openvms-system-manager-s-manual-volume-2-tuning-monitoring-and-complex-systems/#_6017UETP| See here] for the latest VMS UETP manual.

== ULTRIX System Exerciser Package ==

[[ULTRIX]] has got a very similar tool to verify proper hardware operation at the operating system level, the '''[[System Exerciser Package]]'''.

For the earliest reference found so far see the manual: [https://drive.google.com/file/d/1i3LoLAvTQC7dZl-T9X3SsQgg_6s_6TCY/view?usp=sharing ULTRIX-32 2.2 System Exercisers 1987 AA-KS95A-TE]

The MIPS variants of ULTRIX include the System Exerciser Package, too.

== Additional Diagnostic Tools ==

* On-board ROM-based diagnostics (RBDs) / Self-tests
* [[Diagnostic and Utility Protocol|DUP]] for [[Mass Storage Control Protocol|MSCP]] devices

== CPU-specific Supervisors ==

* '''EBSAA''' VAX 8200/8250/8300/8350 & VS8000 Diagnostic Supervisor
* '''ECSAA''' VAX-11/750 DIAGNOSTIC SUPERVISOR
* '''EDSAA''' VAX 8600/8650 Diagnostic Supervisor
* '''EHSAA''' MicroVAX I VDS
* '''EJSAA''' VAX 8820/8830/8840 Diagnostic Supervisor
* '''ELSAA''' VAX 6210/6220/6230/6240/6310/6320/6330/6340/6350/6360 Diagnostic Supervisor
* '''ENSAA''' VAX 725/730 Diagnostic Supervisor
* '''ESSAA''' VAX 780/785 Diagnostic Supervisor
* '''EXSAA''' VAX 6000 Diagnostic Supervisor
* '''EZSAA''' VAX 8530/8550/8700/8800/8820N Diagnostic Supervisor
* '''E?SAA''' VAX9000 Diagnostic Supervisor

There is no supervisor for the series of VAX 7000 / VAX 10000 computers (see: [http://www.vaxhaven.com/images/4/4d/EK-7001A-TS-001.pdf VAX 7000 Advanced Troubleshooting EK-7001A-TS-001])

== Set of Diagnostics for a SV-BXTAA VAX-11/750 System ==

A SV-BXTAA VAX-11/750 System consists of:

* [[KA750 CPU|VAX-11/750 CPU]]
* [[MS750 Memory System|MS750 1MB memory]]
* [[DECwriter IV|LA38 printing console terminal]]
* [[RH750 Massbus Adapter]]
* [[RM02/03 disk drive|RM03 MASSBUS disk drive subsystem]]
* [[DZ11 asynchronous serial line interface|DZ11 terminal adapter]]
* [[TS11 Subsystem|TS11 magnetic tape unit]]

The diagnostics set for this system is made of:

* CPU-specific diagnostic main program
** '''ECSAA''' VAX 11750 DIAG SUPERVISOR

* VAX-common automatic sizing program which automatically determines the current system configuration
** '''EVSBA''' VAX AUTOSIZER DIAGNOSTIC

* Set of VAX-11/750 CPU diagnostics
** '''ECKAA''' VAX 11750 UDIAG MON
** '''ECKAB''' VAX 11750 MICRO DPM
** '''ECKAC''' VAX 11750 MICRO MIC
** '''ECKAD''' VAX FP750 MICRODIAG
** '''ECKAF''' VAX KC750 UDIAG
** '''ECKAL''' VAX 11750 CACHE/TB DIAG
** '''ECKAM''' VAX 11750 MEMORY DIAG
** '''ECKAX''' VAX 11750 CLUSTER EXER

* VAX-common instruction set diagnostic
** '''EVKAA''' VAX INSTRUCTION SET TEST

* VAX-11/750 bus diagnostics
** '''ECCAA''' VAX 11750 RH750 DIAG
** '''ECCBA''' VAX 11750 UBI/DW750 DIAG

* Set of VAX-common peripheral diagnostics
** '''EVTAA''' VAX TERMINAL DIAGNOSTIC
** '''EVTBA''' VAX TERMINAL EXERCISER
** '''EVDAA''' VAX DZ11 8 LINE ASYNC MUX
** '''EVMAA''' VAX TM03/TE16/TU45-77 Tape
** '''EVRDA''' VAX RM03/RM05/RM80 DISKLESS
** '''EVRDB''' VAX RM03/RM05 FUNCTIONAL TEST

== Booting the VAX Diagnostic Supervisor ==

The command to boot the VAX Diagnostic Supervisor on a SIMH VAX is:

BOOT RQ0 /R5:10

* <code>RQ0</code> is the device identifier for the MSCP disk, unit 0, where the diagnostics are stored; adjust this according to your requirements.
* <code>/R5:10</code> is the boot flag to boot the Diagnostic Supervisor located in directory <code>DUA0:[SYSMAINT]</code> or <code>DUA0:[SYS0.SYSMAINT]</code>.

For booting the VAX Diagnostic Supervisor on a real VAX refer chapter 2.1 of the "'''VAX DS Diagnostic Supervisor User's Guide'''" [[#ref_1|[1]]]

== Sample run of the VDS EVSBA AUTOSIZER ==

DS> '''LOAD EVSBA.EXE'''
DS> '''SET FLAGS QUICK'''
DS> '''START /SECTION:MANUAL'''

.. Program: EVSBA - AUTOSIZER LEVEL 3, revision 5.1, 3 tests,
at 18:18:28.19.

COMMAND? '''HELP'''

HELP

This is a manual section command. This program creates ATTACH
commands for all devices in the system.
(ATTACH,CHANGE,EXIT,HELP,LIST,READ,SIZE,WRITE) - These commands
control the sizer in manual and selftest mode.
To obtain further information type HELP followed by a topic.
For example;
HELP MANUAL

Additional information available:

ATTACH CHANGE DEFAULT DEVICE EVENT
EXIT HELP LIST MANUAL QUICK
READ SECTION SELFTEST SCRIPT SIZE
SUMMARY WRITE

COMMAND? '''SIZE'''
COMMAND? '''LIST'''
FILE IN MEMORY 'CONFIG.COM'
!! AUTOMATIC SIZING PROGRAM.
!! THIS IS A TOOL AND NOT A DIAGNOSTIC PROGRAM.
!! CONFIGURATION FILE FOR SYSTEM.
!! COMPUTER GENERATED CPU TYPE 2 MICROCODE REV LEVEL = 99
!! NUMERIC VALUES WITH A LEADING ZERO ARE ASSIGNED.
!! FILE VALID ONLY FOR STANDARD HARDWARE CONFIGURATION.
!! TIME IS 15-FEB-1984 18:18:56.85
!!
!! *** QUICK FLAG SET. NO CHECKS MADE FOR TERMINALS ON DZ11/DZ32'S ***
!!
!!
!! DEFINE PROCESSOR...
!!
DS> ATTACH KA750 HUB KA0 YES YES YES 027FF 0
!!
!! DEFINE MEMORY...
!!
DS> ATTACH MS750 MS0
!!
!! DEFINE UNIBUS ADAPTERS...
!!
DS> ATTACH DW750 HUB DW0
!!
DS> ATTACH LP11 DW0 LPA 777514 0200 04
DS> ATTACH LP25 LPA LPA0 !! *** PRINTER TYPE IS ESTIMATED ***
DS> ATTACH TS11 DW0 MSA0 772520 0224 05
DS> ATTACH UDA50 DW0 DUA 772150 0154 05 02
DS> ATTACH RA81 DUA DUA0
DS> ATTACH RA60 DUA DJA2
DS> ATTACH RX50 DUA DUA3
DS> ATTACH DZ11 DW0 TTA 760100 0300 05 EIA
DS> ATTACH DZ11 DW0 TTB 760110 0310 05 EIA
DS> ATTACH DZ11 DW0 TTC 760120 0320 05 EIA
DS> ATTACH DZ11 DW0 TTD 760130 0330 05 EIA
COMMAND? '''WRITE'''
CONFIGURATION FILE IS NORMALLY READ/WRITTEN TO THE SUPERVISOR CONSOLE MEDIA
VERIFY SUPERVISOR CONSOLE MEDIA LOADED.
VERIFIED? [(Yes), No] '''YES'''
COMMAND? '''EXIT'''
DS>

== See also ==

* [[Running VDS Diagnostics on the SIMH VAX-11/750]]

== External links ==

This page contains condensed information from several DEC manuals, among others:

* [http://bitsavers.org/pdf/dec/vax/diag/EP-EVNDX-25.0_Oct86.txt EVNDX25 VAX DIAGNOSTIC INDEX]
* [https://vt100.net/mirror/hcps/si75fin1.pdf EK-SI75F-IN-001 VAX-11-750 Installation Manual] pdf-page 60ff
* <div id="ref_1">[1] [http://bitsavers.org/pdf/dec/vax/diag/VAX_Diagnostic_Supervisor_Users_Guide_Apr89.pdf AA-FK66A-TE VAX DS Diagnostic Supervisor User's Guide] </div>
* [http://bitsavers.org/pdf/dec/vax/diag/EK-1VAXD-TM-001_VAX_Diagnostic_Design_Guide_Aug79.pdf EK-1VAXD-TM-003 VAX Diagnostic Design Guide]
* [http://bitsavers.org/pdf/dec/vax/diag/AA-FK67A-TE_VAX_Diagnostic_Design_Guide_Apr89.pdf AA-FK67A-TE VAX Diagnostic Design Guide]
* [http://www.bitsavers.org/pdf/dec/vax/vms/1.5/2b/AA-D643A-TE_VAX_VMS_UETP_Users_Guide_Aug78.pdf AA-D643A-TE VAX/VMS UETP User’s Guide]
* [http://www.trailing-edge.com/~shoppa/11780diags/ VAX-11/780 Diagnostic Help Files]
* [https://manx-docs.org/collections/antonio/dec/MDS-2000-01/cd1/VAX/7001ATS1.PDF EK-7001A-TS-001 VAX 7000 Advanced Troubleshooting]

[[Category: VAX]]
[[Category: VAX Software]]
[[Category: VAX Diagnostic Software]]
[[Category: SIMH Tutorials]]
[[Category: VMS Practical Guides]]

VAX Diagnostic Supervisor

2025-11-11T20:57:32Z

Vaxorcist: /* VAX Diagnostic Coding Convention */ Processor code J = VAX 8820/8830/8840 added

VDS - '''VAX Diagnostic Supervisor''' (sometimes abbreviated to VAX/DS) is a set of diagnostic software programs for the [[DEC]] [[VAX]] computers and peripheral devices.

== Intro ==

'''''"At best, a computer is as good as its diagnostic tools!"'''''

That's what they must have thought at DEC when they developed their diagnostic software.

Here we will take a closer look at the VAX Diagnostic Supervisor and also a quick side look at the [[User Environment Test Package]] (UETP).

== Using VDS for simulated VAX Computers ==

You may ask: "What are the VAX diagnostics good for when run on a simulated VAX?"

Yes, many diagnostics do not run on a simulated VAX, but some work very well and are used e.g. for testing the various [[SIMH]] VAX simulators for correct execution of the VAX native mode instructions.

Furthermore you can explore how precise the simulation mimics the real hardware.

If you plan to test your real VAX, you can familiarize yourself with VDS and prepare your diagnosis in SIMH, and SIMH can assist you in preparing and creating a diagnostic kit on media appropriate for your VAX.

Automated testing script for a SIMH VAX-11/750:

SET CLOCK NOCALIBRATE=600K
ATTACH -RQ RQ0 VAX_MINIMUM_DIAGS.dsk
EXPECT "DS> " SEND "ATTACH UDA50 DW0 DUA 772150 154 5 10\r"; GO -Q
EXPECT "DS> " SEND "ATTACH RA81 DUA DUA0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH KA750 CMI KA0 yes yes yes 0 0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH DW750 CMI DW0 8\r"; GO -Q
EXPECT "DS> " SEND "SET LOAD DUA0:[SYSMAINT]\r"; GO -Q
EXPECT "DS> " SEND "SELECT KA0\r"; GO -Q
EXPECT "DS> " SEND "SET FLAGS TRACE\r"; GO -Q
EXPECT "DS> " SEND "RUN EVKAB\r"; GO -Q
BOOT -Q RQ0 /R5:10

== VDS History ==

VDS development began in parallel that to the first [[VAX]] model, the [[VAX-11/780]] in 1977.

VDS was provided soley for the '''''"big VAXen"''''' (i.e. not for the [[MicroVAX]] and [[VAXstation]] computers), with one remarkable exception, the [[MicroVAX I]], resp. [[VAXstation I]].
Each new VAX model received its CPU-specific VDS modules up to the [[VAX 9000]]; only the VAX models of the last two series, [[VAX 7000]] and [[VAX 10000]], were covered by other diagnostic methods.

== Program Levels ==

All VAX diagnostic programs are assigned to a '''level'''. Levels are numbered 1, 2R, 2, 3, 4, and 5. A program’s level indicates its run-time environment.

* '''Level 1''' diagnostic programs run under an operating system. They do not use the VAX/DS. (=> UETP)
* '''Level 2R''' diagnostic programs run under VAX/DS in user mode only.
* '''Level 2''' diagnostic programs run in both user mode and standalone mode, under the control of the VAX/DS.
* '''Level 3''' diagnostic programs run only in standalone mode, under the control of the VAX/DS.
* '''Level 4''' diagnostic programs run in standalone without VAX/DS.
* '''level 5''' diagnostic programs run in [[Writable Control Store|WCS]] or system console, not in VAX main memory. They do not use the VAX/DS.

Only the levels 2R, 2, and 3 are managed by VDS.

== Sections, Tests, Subtests, and Flags ==

All diagnostic programs that run under the VAX/DS are composed of one or more '''sections'''. Each section has a name, and it is possible to specify, by name, which section of the program to execute. A program section can have one of two functions, depending on its design:

* Test a certain major portion of the unit under test.
* Facilitate a certain mode of testing. For example, there might be a quick-verify section, used to give the device a quick (but not thorough) test.

In order to determine the number and names of the sections in a particular diagnostic program, use the <code>SHOW SECTIONS</code> command. However, every program contains a default section called <code>DEFAULT</code>, which will execute automatically if you do not specifically select a section. A section is selected with the <code>/SECTION</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Each section is composed of a set of '''tests'''; each test verifies either a particular function of the hardware or a particular subset of the component logic being tested. The VAX/DS allows you to specify which tests within a section to run. Each test may have some '''subtests'''. Tests are selected with the <code>/TEST</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Two sets of '''flags''' are provided to control certain aspects of a diagnostic program’s execution. These flags may be set or cleared before the diagnostic program is started.

One set of flags is called the '''VAX/DS control flags'''. The flags in this set are interpreted by the VAX/DS and their meanings are the same in all diagnostic programs. The VAX/DS control flags are set with the <code>SET FLAGS</code> command.

The other set of flags is referred to as the '''event flags'''. This set consists of 23 flags whose purposes are defined by the diagnostic programs. The user must read the documentation for specific diagnostic programs to determine if a definition has been assigned to any of the event flags. <code>SET EVENT FLAGS</code> command.

== Some useful VDS commands ==

* <code>'''LOAD''' Exxxx</code> Load diagnostic Exxxx (where "Exxxx" is replaced by the diagnostics name, e.g. EVKAA)
* <code>'''SHOW FLAGS'''</code> Show VDS flags
* <code>'''SHOW TESTS'''</code> Show the available tests of the loaded diagnostic
* <code>'''SHOW SECTIONS'''</code> Show the available sections of the loaded diagnostic
* <code>'''START/TEST='''first:last</code> Start a subset of the loaded diagnostics tests (where "first" is the test number to start with, and -optionally- "last" is the last one to execute)
* <code>'''START/SECTION='''section-name</code> Start a single section of the loaded diagnostic (where "section-name" is the name of the section to run)
* <code>'''START/PASSES='''count</code> Start the loaded diagnostic for "count" passes (where "count" is the number of passes to execute)
* <code>'''RUN''' exxxx'''/TEST='''first:last</code> Run a subset of the diagnostics tests
* <code>'''RUN''' exxxx'''/SECTION='''section-name</code> Run a single section of the diagnostic
* <code>'''RUN''' exxxx'''/PASSES='''count</code> Run the diagnostic for "count" passes

Use a pass count of 0 to run a program continuously. If you do this, the program will run until you type CTRL/C or a failure occurs with the HALT flag set.

== Diagnostic Program Documentation ==

Documentation provided for each diagnostic program includes:

* '''Help file'''
:: The help file is referenced with the HELP command. It contains any operating instructions that may be unique to the diagnostic program. The help file for diagnostic program EVXYZ is EVXYZ.HLP; the help file for the VAX/DS is EVSAA.HLP

* '''Documentation file'''
:: The documentation file provides a detailed description of a diagnostic program's function, run-time requirements, operating instructions, fault detection, and maintenance history, plus explanations of each test’s function and execution flow. The documentation file for diagnostic program EVXYZ is EVXYZ.DOC.

* '''Source Code listings'''
:: Source code listings of the diagnostic programs are available. All VAX/DS diagnostic programs are structured in a standard format. For example, the initialization code for every diagnostic program is always located in the same relative area within the listing. To fully understand the source code listings of a VAX/DS diagnostic program, refer to the VAX Diagnostic Design Guide.

The help file for a diagnostic program is shipped with the diagnostic program. The documentation file and source codelistings are available by ordering a [[Maintenance Documentation Service]] Option on microfiche.

== Diagnostic Scopes ==

There are two diagnostic scopes.

* A CPU-specific scope: '''CPU Cluster Testing'''
* A scope for the identical diagnostic programs for all types of VAX computers: '''Peripheral Diagnostics'''

=== CPU Cluster Testing ===

'''NOTE: The term "CPU cluster" used here means all components belonging to a CPU; there is no connection with the term [[VAXcluster|"VAXcluster" (alternatively: "VMScluster")]].'''

The VAX CPU cluster is tested by a set of programs, existing at several program levels, as follows:

* Level 5
** Console tests
** Processor tests
** Memory tests
* Level 4
** VAX instruction set test (hardcore for VDS)
** Cache and translation buffer tests (VAX-11/750 only)
* Level 3
** Memory tests (if no level 5 test possible)
** Channel adapter tests
** Cluster exerciser

'''NOTE: The term "Channel adapter" used here means bus adapter, e.g. for [[UNIBUS]] or [[MASSBUS]].'''

This set of programs implements the VAX diagnostic strategy by providing a set of building blocks by which a system may be tested, starting with the level 5 basic processor tests and ending with the level 3 cluster exerciser, which is a program meant to exercise all components of the cluster.

=== Peripheral Diagnostics ===

Thorough testing of a peripheral device requires the development of three different diagnostic programs. For each device type the following will typically (but not necessarily) exist:

* A level 3 logic test
* A level 3 function test
* A level 2R function test

This group of programs implements the diagnostic strategy by providing a facility for producing very accurate and detailed identifications of fault conditions via the level 3 programs and by also providing a method by which the device may be tested without bringing down the customer's operating system via the level 2R program.

The level 3 logic test will provide the greatest detail of error resolution, indicating which section of logic is failing. This program will be used by technicians to repair bad logic boards, and will provide very high test coverage. Some devices contain ROM-resident microprograms ("self-tests") that perform logic testing, making a level 3 logic test unnecessary.

The level 3 function test will provide a comprehensive test of all of the device’s functions. This program will be used to determine accurately whether or not a device is operating correctly. This is the definitive function test and provides very high test coverage. Level 3 function tests are usually required even if the device possesses self-testing capabilities, because self-tests generally are not capable of complete detection of function failures.

The level 2R program will typically consist of a subset of the level 3 function test. It will test as much of the device’s functionality as can be tested in the user (VMS) environment. The tests it contains are exact or approximate copies of tests existing in the level 3 program.

A typical sequence of use for these programs, when dealing with a system at a customer site, is as follows:

# The customer (or field service) suspects a fault existing in the device.
# The level 2R program is run to see if the error can be detected without stopping the operating system. If the error is found, go to step 4.
# If the level 2R program cannot identify the fault, the operating system is brought down and the level 3 function test is run.
# The fault is identified and the failing [[Field Replacable Unit|FRU]] is replaced. The operating system is then brought back up.
# The failing FRU is brought back to DIGITAL, where the level 3 logic test, the level 3 function test, or perhaps a module test station is used to identify the failing logic on the FRU. The FRU is repaired.

== VAX Diagnostic Coding Convention ==

VAX diagnostic program names consist of 5 letters and a two-digit version number, e.g.: ECKAL-3.4:

* E = VAX
* C = 11/750
* K = CPU
* A = Supervisor
* L = Unique identifier
* 3 = Major revision
* 4 = Minor Revision

See the following 1986 VAX Diagnostic Coding Convention Table for letter breakdown:

EPXYD-R.P

E = System

E = VAX

P = Processor

B = VAX 8200/8300
D = VAX 8600
S = VAX 11780
T = VAX 11785
C = VAX 11750
N = VAX 11730 and 11725
H = MicroVAX I
J = VAX 8820/8830/8840
V = More than one VAX Processor
X = VAX 6000
Z = VAX 8530/8550/8700/8800

X = Device Category

A = Application (CR, LP, A-D, Misc.)
C = Channel Adaptors (MBA, UBA)
D = Communication Devices (DMC, DZ11)
G = CI Adapter
K = CPU
L = Database Files
M = Magnetic Tape (TE, TU, DT)
P = Test Equipment
Q = QIO Device Driver
R = Rotating Memory (RP, RK, RM, RS, RX)
S = System Monitor (Supervisor, Tape Monitor)
T = Terminal (LA36, VT52)
U = Utilities (Script file, Copy, Update)
W = Workstations
X = System Exerciser (EXR/BUSINT)
Z = Media Packages
0-9 = Engineering File

Y = Device Type

Category Application
A = Line Printers, LP, LCP01
B = Card Readers, CR
L = LPA11-K
Category Channel
A = MBA
B = UBA, DWBUA
C = MA780
D = IEC11, IEU11-A, DR70
E = DT07
F = DEC DATAWAY
G = CI780
H = CI750/CI780 MICROCODE VERIFICATION (INTERNAL)
I = TEST BED ADAPTERS
J = NBI ADAPTER
K = CIBCI

Category Communications
A = DZ11,DZ32,DMZ32,DHU11,DMB32
B = DMC
C = Multiple Devices
D = DR11-C
E = DV11
F = DR780,DF11-W
G = DQS11
H = KMC11-B
I = KMS11-B
J = DM11-BA
K = DMS11-BA
L = DMF32 Combo
M = DMC11,DMR11,DMP11
N = DN11
O = CPI32
P = PCL11
R = DR11B,DR11-W,DRE11
S = DRS11/DSS
T = KCT32-A,FEPCM
U = DUP11
X = Multiple Devices
W = UNA
Y = DEBNT

Category Database Files
A = CRD DATABASE FILES
B = SYSTEM EXERCISER DATABASE FILES

Category Magnetic Tape
A = TE16/77, TS11, TU78, TS05
B = TU81,TU80

Category QIO Device Drivers
For this category, the fourth and fifth letters of the code are the device mnemonic.
For example, EVQDB is the QIO device driver for the DB, or RP disk series.

Category Test Equipment
A = CI780 Node Tester
B = NI Tester

Category Rotating Memory
A = Multiple devices
B = RP04/5/6
C = DCL/RP04/5/6
D = RM03/RM05/RM80
E = RK611,RK06,RK07
F = RL02
G = RM80
H = RP07
I = RX02
J = ML11
K = IDC
L = UDA50(RA60,RA80,RA81)
M = RC25
N = RUX50

Category System Monitor
A = Supervisor
B = Autosizer
C = DYDDM

Category Terminals
A = All Terminals
B = Terminal exerciser
C = VS11
D = 11C03-LH Fastek
G = VS70

Category Utility
A = Script File
B = Copy Command file
C = Updating file

Category Workstation
A = VS100

Category Exerciser
B = Exerciser Bus Interaction

D = Fifth character makes the code unique. A through Z and 1 through 9.

R = Revision (MAJOR)
P = Revision (MINOR)

== Distribution of Diagnostic Programs ==

Typically, a VAX computer came with all the necessary diagnostic programs on console media at no additional charge, e.g.:

* VAX-11/780: [[RX01/02 floppy drive|RX01 floppies]]
* VAX-11/750, VAX-11/730, and VAX-11/725: [[TU58 DECtape II|TU58 cartridges]]
* VAX 8600: [[RL01/02 disk drive|RL02 disk pack]]
* VAX 8200, VAX 8250, VAX 8300, and VAX 8350: [[RX50 dual-diskette drive|RX50 floppies]]

Additionally, you could buy larger collections of diagnostic programs on [[magnetic tape]] or [[Removable-pack disk|removable disk packs]].

Extended documentation was available on microfiche at an extra charge.

== VMS User Enviroment Test Package (UETP) ==

From the very beginning of VMS V1.0 there was the '''[[User Enviroment Test Package]]''' (UETP), see: [http://bitsavers.trailing-edge.com/pdf/dec/vax/vms/2.0/AA-D643B-TE_VAX-VMS_2.0_UETP_Users_Guide_198003.pdf VAX/VMS UETP User’s Guide AA-D643A-TE]

Quote from the first UETP manual:

"''The UETP is a collection of tests designed to demonstrate that the hardware and software components of a VAX/VMS system are in working order. DIGITAL software support representatives run the UETP on a newly installed VAX/VMS system as the formal sample procedure.''"

UETP is still used in the latest version of VMS (V9.2-2 for x86 as of this writing).

[https://docs.vmssoftware.com/vsi-openvms-system-manager-s-manual-volume-2-tuning-monitoring-and-complex-systems/#_6017UETP| See here] for the latest VMS UETP manual.

== ULTRIX System Exerciser Package ==

[[ULTRIX]] has got a very similar tool to verify proper hardware operation at the operating system level, the '''[[System Exerciser Package]]'''.

For the earliest reference found so far see the manual: [https://drive.google.com/file/d/1i3LoLAvTQC7dZl-T9X3SsQgg_6s_6TCY/view?usp=sharing ULTRIX-32 2.2 System Exercisers 1987 AA-KS95A-TE]

The MIPS variants of ULTRIX include the System Exerciser Package, too.

== Additional Diagnostic Tools ==

* On-board ROM-based diagnostics (RBDs) / Self-tests
* [[Diagnostic and Utility Protocol|DUP]] for [[Mass Storage Control Protocol|MSCP]] devices

== CPU-specific Supervisors ==

* '''EBSAA''' VAX 8200/8250/8300/8350 & VS8000 Diagnostic Supervisor
* '''ECSAA''' VAX-11/750 DIAGNOSTIC SUPERVISOR
* '''EDSAA''' VAX 8600/8650 Diagnostic Supervisor
* '''EHSAA''' MicroVAX I VDS
* '''EJSAA''' VAX 8820/8830/8840 Diagnostic Supervisor
* '''ELSAA''' VAX 6210/6220/6230/6240/6310/6320/6330/6340/6350/6360 Diagnostic Supervisor
* '''ENSAA''' VAX 725/730 Diagnostic Supervisor
* '''ESSAA''' VAX 780/785 Diagnostic Supervisor
* '''EXSAA''' VAX 6000 Diagnostic Supervisor
* '''EZSAA''' VAX 8530/8550/8700/8800/8820N Diagnostic Supervisor
* '''E?SAA''' VAX9000 Diagnostic Supervisor

There is no supervisor for the series of VAX 7000 / VAX 10000 computers (see: [http://www.vaxhaven.com/images/4/4d/EK-7001A-TS-001.pdf VAX 7000 Advanced Troubleshooting EK-7001A-TS-001])

== Set of Diagnostics for a SV-BXTAA VAX-11/750 System ==

A SV-BXTAA VAX-11/750 System consists of:

* [[KA750 CPU|VAX-11/750 CPU]]
* [[MS750 Memory System|MS750 1MB memory]]
* [[DECwriter IV|LA38 printing console terminal]]
* [[RH750 Massbus Adapter]]
* [[RM02/03 disk drive|RM03 MASSBUS disk drive subsystem]]
* [[DZ11 asynchronous serial line interface|DZ11 terminal adapter]]
* [[TS11 Subsystem|TS11 magnetic tape unit]]

The diagnostics set for this system is made of:

* CPU-specific diagnostic main program
** '''ECSAA''' VAX 11750 DIAG SUPERVISOR

* VAX-common automatic sizing program which automatically determines the current system configuration
** '''EVSBA''' VAX AUTOSIZER DIAGNOSTIC

* Set of VAX-11/750 CPU diagnostics
** '''ECKAA''' VAX 11750 UDIAG MON
** '''ECKAB''' VAX 11750 MICRO DPM
** '''ECKAC''' VAX 11750 MICRO MIC
** '''ECKAD''' VAX FP750 MICRODIAG
** '''ECKAF''' VAX KC750 UDIAG
** '''ECKAL''' VAX 11750 CACHE/TB DIAG
** '''ECKAM''' VAX 11750 MEMORY DIAG
** '''ECKAX''' VAX 11750 CLUSTER EXER

* VAX-common instruction set diagnostic
** '''EVKAA''' VAX INSTRUCTION SET TEST

* VAX-11/750 bus diagnostics
** '''ECCAA''' VAX 11750 RH750 DIAG
** '''ECCBA''' VAX 11750 UBI/DW750 DIAG

* Set of VAX-common peripheral diagnostics
** '''EVTAA''' VAX TERMINAL DIAGNOSTIC
** '''EVTBA''' VAX TERMINAL EXERCISER
** '''EVDAA''' VAX DZ11 8 LINE ASYNC MUX
** '''EVMAA''' VAX TM03/TE16/TU45-77 Tape
** '''EVRDA''' VAX RM03/RM05/RM80 DISKLESS
** '''EVRDB''' VAX RM03/RM05 FUNCTIONAL TEST

== Booting the VAX Diagnostic Supervisor ==

The command to boot the VAX Diagnostic Supervisor on a SIMH VAX is:

BOOT RQ0 /R5:10

* <code>RQ0</code> is the device identifier for the MSCP disk, unit 0, where the diagnostics are stored; adjust this according to your requirements.
* <code>/R5:10</code> is the boot flag to boot the Diagnostic Supervisor located in directory <code>DUA0:[SYSMAINT]</code> or <code>DUA0:[SYS0.SYSMAINT]</code>.

For booting the VAX Diagnostic Supervisor on a real VAX refer chapter 2.1 of the "'''VAX DS Diagnostic Supervisor User's Guide'''" [[#ref_1|[1]]]

== Sample run of the VDS EVSBA AUTOSIZER ==

DS> '''LOAD EVSBA.EXE'''
DS> '''SET FLAGS QUICK'''
DS> '''START /SECTION:MANUAL'''

.. Program: EVSBA - AUTOSIZER LEVEL 3, revision 5.1, 3 tests,
at 18:18:28.19.

COMMAND? '''HELP'''

HELP

This is a manual section command. This program creates ATTACH
commands for all devices in the system.
(ATTACH,CHANGE,EXIT,HELP,LIST,READ,SIZE,WRITE) - These commands
control the sizer in manual and selftest mode.
To obtain further information type HELP followed by a topic.
For example;
HELP MANUAL

Additional information available:

ATTACH CHANGE DEFAULT DEVICE EVENT
EXIT HELP LIST MANUAL QUICK
READ SECTION SELFTEST SCRIPT SIZE
SUMMARY WRITE

COMMAND? '''SIZE'''
COMMAND? '''LIST'''
FILE IN MEMORY 'CONFIG.COM'
!! AUTOMATIC SIZING PROGRAM.
!! THIS IS A TOOL AND NOT A DIAGNOSTIC PROGRAM.
!! CONFIGURATION FILE FOR SYSTEM.
!! COMPUTER GENERATED CPU TYPE 2 MICROCODE REV LEVEL = 99
!! NUMERIC VALUES WITH A LEADING ZERO ARE ASSIGNED.
!! FILE VALID ONLY FOR STANDARD HARDWARE CONFIGURATION.
!! TIME IS 15-FEB-1984 18:18:56.85
!!
!! *** QUICK FLAG SET. NO CHECKS MADE FOR TERMINALS ON DZ11/DZ32'S ***
!!
!!
!! DEFINE PROCESSOR...
!!
DS> ATTACH KA750 HUB KA0 YES YES YES 027FF 0
!!
!! DEFINE MEMORY...
!!
DS> ATTACH MS750 MS0
!!
!! DEFINE UNIBUS ADAPTERS...
!!
DS> ATTACH DW750 HUB DW0
!!
DS> ATTACH LP11 DW0 LPA 777514 0200 04
DS> ATTACH LP25 LPA LPA0 !! *** PRINTER TYPE IS ESTIMATED ***
DS> ATTACH TS11 DW0 MSA0 772520 0224 05
DS> ATTACH UDA50 DW0 DUA 772150 0154 05 02
DS> ATTACH RA81 DUA DUA0
DS> ATTACH RA60 DUA DJA2
DS> ATTACH RX50 DUA DUA3
DS> ATTACH DZ11 DW0 TTA 760100 0300 05 EIA
DS> ATTACH DZ11 DW0 TTB 760110 0310 05 EIA
DS> ATTACH DZ11 DW0 TTC 760120 0320 05 EIA
DS> ATTACH DZ11 DW0 TTD 760130 0330 05 EIA
COMMAND? '''WRITE'''
CONFIGURATION FILE IS NORMALLY READ/WRITTEN TO THE SUPERVISOR CONSOLE MEDIA
VERIFY SUPERVISOR CONSOLE MEDIA LOADED.
VERIFIED? [(Yes), No] '''YES'''
COMMAND? '''EXIT'''
DS>

== See also ==

* [[Running VDS Diagnostics on the SIMH VAX-11/750]]

== External links ==

This page contains condensed information from several DEC manuals, among others:

* [http://bitsavers.org/pdf/dec/vax/diag/EP-EVNDX-25.0_Oct86.txt EVNDX25 VAX DIAGNOSTIC INDEX]
* [https://vt100.net/mirror/hcps/si75fin1.pdf EK-SI75F-IN-001 VAX-11-750 Installation Manual] pdf-page 60ff
* <div id="ref_1">[1] [http://bitsavers.org/pdf/dec/vax/diag/VAX_Diagnostic_Supervisor_Users_Guide_Apr89.pdf AA-FK66A-TE VAX DS Diagnostic Supervisor User's Guide] </div>
* [http://bitsavers.org/pdf/dec/vax/diag/EK-1VAXD-TM-001_VAX_Diagnostic_Design_Guide_Aug79.pdf EK-1VAXD-TM-003 VAX Diagnostic Design Guide]
* [http://bitsavers.org/pdf/dec/vax/diag/AA-FK67A-TE_VAX_Diagnostic_Design_Guide_Apr89.pdf AA-FK67A-TE VAX Diagnostic Design Guide]
* [http://www.bitsavers.org/pdf/dec/vax/vms/1.5/2b/AA-D643A-TE_VAX_VMS_UETP_Users_Guide_Aug78.pdf AA-D643A-TE VAX/VMS UETP User’s Guide]
* [http://www.trailing-edge.com/~shoppa/11780diags/ VAX-11/780 Diagnostic Help Files]
* [https://manx-docs.org/collections/antonio/dec/MDS-2000-01/cd1/VAX/7001ATS1.PDF EK-7001A-TS-001 VAX 7000 Advanced Troubleshooting]

[[Category: VAX]]
[[Category: VAX Software]]
[[Category: VAX Diagnostic Software]]
[[Category: SIMH Tutorials]]
[[Category: VMS Practical Guides]]

VAX Diagnostic Supervisor

2025-11-11T20:56:13Z

Vaxorcist: /* CPU-specific Supervisors */ EXSAA = VAX 6000 Diagnostic Supervisor added

VDS - '''VAX Diagnostic Supervisor''' (sometimes abbreviated to VAX/DS) is a set of diagnostic software programs for the [[DEC]] [[VAX]] computers and peripheral devices.

== Intro ==

'''''"At best, a computer is as good as its diagnostic tools!"'''''

That's what they must have thought at DEC when they developed their diagnostic software.

Here we will take a closer look at the VAX Diagnostic Supervisor and also a quick side look at the [[User Environment Test Package]] (UETP).

== Using VDS for simulated VAX Computers ==

You may ask: "What are the VAX diagnostics good for when run on a simulated VAX?"

Yes, many diagnostics do not run on a simulated VAX, but some work very well and are used e.g. for testing the various [[SIMH]] VAX simulators for correct execution of the VAX native mode instructions.

Furthermore you can explore how precise the simulation mimics the real hardware.

If you plan to test your real VAX, you can familiarize yourself with VDS and prepare your diagnosis in SIMH, and SIMH can assist you in preparing and creating a diagnostic kit on media appropriate for your VAX.

Automated testing script for a SIMH VAX-11/750:

SET CLOCK NOCALIBRATE=600K
ATTACH -RQ RQ0 VAX_MINIMUM_DIAGS.dsk
EXPECT "DS> " SEND "ATTACH UDA50 DW0 DUA 772150 154 5 10\r"; GO -Q
EXPECT "DS> " SEND "ATTACH RA81 DUA DUA0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH KA750 CMI KA0 yes yes yes 0 0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH DW750 CMI DW0 8\r"; GO -Q
EXPECT "DS> " SEND "SET LOAD DUA0:[SYSMAINT]\r"; GO -Q
EXPECT "DS> " SEND "SELECT KA0\r"; GO -Q
EXPECT "DS> " SEND "SET FLAGS TRACE\r"; GO -Q
EXPECT "DS> " SEND "RUN EVKAB\r"; GO -Q
BOOT -Q RQ0 /R5:10

== VDS History ==

VDS development began in parallel that to the first [[VAX]] model, the [[VAX-11/780]] in 1977.

VDS was provided soley for the '''''"big VAXen"''''' (i.e. not for the [[MicroVAX]] and [[VAXstation]] computers), with one remarkable exception, the [[MicroVAX I]], resp. [[VAXstation I]].
Each new VAX model received its CPU-specific VDS modules up to the [[VAX 9000]]; only the VAX models of the last two series, [[VAX 7000]] and [[VAX 10000]], were covered by other diagnostic methods.

== Program Levels ==

All VAX diagnostic programs are assigned to a '''level'''. Levels are numbered 1, 2R, 2, 3, 4, and 5. A program’s level indicates its run-time environment.

* '''Level 1''' diagnostic programs run under an operating system. They do not use the VAX/DS. (=> UETP)
* '''Level 2R''' diagnostic programs run under VAX/DS in user mode only.
* '''Level 2''' diagnostic programs run in both user mode and standalone mode, under the control of the VAX/DS.
* '''Level 3''' diagnostic programs run only in standalone mode, under the control of the VAX/DS.
* '''Level 4''' diagnostic programs run in standalone without VAX/DS.
* '''level 5''' diagnostic programs run in [[Writable Control Store|WCS]] or system console, not in VAX main memory. They do not use the VAX/DS.

Only the levels 2R, 2, and 3 are managed by VDS.

== Sections, Tests, Subtests, and Flags ==

All diagnostic programs that run under the VAX/DS are composed of one or more '''sections'''. Each section has a name, and it is possible to specify, by name, which section of the program to execute. A program section can have one of two functions, depending on its design:

* Test a certain major portion of the unit under test.
* Facilitate a certain mode of testing. For example, there might be a quick-verify section, used to give the device a quick (but not thorough) test.

In order to determine the number and names of the sections in a particular diagnostic program, use the <code>SHOW SECTIONS</code> command. However, every program contains a default section called <code>DEFAULT</code>, which will execute automatically if you do not specifically select a section. A section is selected with the <code>/SECTION</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Each section is composed of a set of '''tests'''; each test verifies either a particular function of the hardware or a particular subset of the component logic being tested. The VAX/DS allows you to specify which tests within a section to run. Each test may have some '''subtests'''. Tests are selected with the <code>/TEST</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Two sets of '''flags''' are provided to control certain aspects of a diagnostic program’s execution. These flags may be set or cleared before the diagnostic program is started.

One set of flags is called the '''VAX/DS control flags'''. The flags in this set are interpreted by the VAX/DS and their meanings are the same in all diagnostic programs. The VAX/DS control flags are set with the <code>SET FLAGS</code> command.

The other set of flags is referred to as the '''event flags'''. This set consists of 23 flags whose purposes are defined by the diagnostic programs. The user must read the documentation for specific diagnostic programs to determine if a definition has been assigned to any of the event flags. <code>SET EVENT FLAGS</code> command.

== Some useful VDS commands ==

* <code>'''LOAD''' Exxxx</code> Load diagnostic Exxxx (where "Exxxx" is replaced by the diagnostics name, e.g. EVKAA)
* <code>'''SHOW FLAGS'''</code> Show VDS flags
* <code>'''SHOW TESTS'''</code> Show the available tests of the loaded diagnostic
* <code>'''SHOW SECTIONS'''</code> Show the available sections of the loaded diagnostic
* <code>'''START/TEST='''first:last</code> Start a subset of the loaded diagnostics tests (where "first" is the test number to start with, and -optionally- "last" is the last one to execute)
* <code>'''START/SECTION='''section-name</code> Start a single section of the loaded diagnostic (where "section-name" is the name of the section to run)
* <code>'''START/PASSES='''count</code> Start the loaded diagnostic for "count" passes (where "count" is the number of passes to execute)
* <code>'''RUN''' exxxx'''/TEST='''first:last</code> Run a subset of the diagnostics tests
* <code>'''RUN''' exxxx'''/SECTION='''section-name</code> Run a single section of the diagnostic
* <code>'''RUN''' exxxx'''/PASSES='''count</code> Run the diagnostic for "count" passes

Use a pass count of 0 to run a program continuously. If you do this, the program will run until you type CTRL/C or a failure occurs with the HALT flag set.

== Diagnostic Program Documentation ==

Documentation provided for each diagnostic program includes:

* '''Help file'''
:: The help file is referenced with the HELP command. It contains any operating instructions that may be unique to the diagnostic program. The help file for diagnostic program EVXYZ is EVXYZ.HLP; the help file for the VAX/DS is EVSAA.HLP

* '''Documentation file'''
:: The documentation file provides a detailed description of a diagnostic program's function, run-time requirements, operating instructions, fault detection, and maintenance history, plus explanations of each test’s function and execution flow. The documentation file for diagnostic program EVXYZ is EVXYZ.DOC.

* '''Source Code listings'''
:: Source code listings of the diagnostic programs are available. All VAX/DS diagnostic programs are structured in a standard format. For example, the initialization code for every diagnostic program is always located in the same relative area within the listing. To fully understand the source code listings of a VAX/DS diagnostic program, refer to the VAX Diagnostic Design Guide.

The help file for a diagnostic program is shipped with the diagnostic program. The documentation file and source codelistings are available by ordering a [[Maintenance Documentation Service]] Option on microfiche.

== Diagnostic Scopes ==

There are two diagnostic scopes.

* A CPU-specific scope: '''CPU Cluster Testing'''
* A scope for the identical diagnostic programs for all types of VAX computers: '''Peripheral Diagnostics'''

=== CPU Cluster Testing ===

'''NOTE: The term "CPU cluster" used here means all components belonging to a CPU; there is no connection with the term [[VAXcluster|"VAXcluster" (alternatively: "VMScluster")]].'''

The VAX CPU cluster is tested by a set of programs, existing at several program levels, as follows:

* Level 5
** Console tests
** Processor tests
** Memory tests
* Level 4
** VAX instruction set test (hardcore for VDS)
** Cache and translation buffer tests (VAX-11/750 only)
* Level 3
** Memory tests (if no level 5 test possible)
** Channel adapter tests
** Cluster exerciser

'''NOTE: The term "Channel adapter" used here means bus adapter, e.g. for [[UNIBUS]] or [[MASSBUS]].'''

This set of programs implements the VAX diagnostic strategy by providing a set of building blocks by which a system may be tested, starting with the level 5 basic processor tests and ending with the level 3 cluster exerciser, which is a program meant to exercise all components of the cluster.

=== Peripheral Diagnostics ===

Thorough testing of a peripheral device requires the development of three different diagnostic programs. For each device type the following will typically (but not necessarily) exist:

* A level 3 logic test
* A level 3 function test
* A level 2R function test

This group of programs implements the diagnostic strategy by providing a facility for producing very accurate and detailed identifications of fault conditions via the level 3 programs and by also providing a method by which the device may be tested without bringing down the customer's operating system via the level 2R program.

The level 3 logic test will provide the greatest detail of error resolution, indicating which section of logic is failing. This program will be used by technicians to repair bad logic boards, and will provide very high test coverage. Some devices contain ROM-resident microprograms ("self-tests") that perform logic testing, making a level 3 logic test unnecessary.

The level 3 function test will provide a comprehensive test of all of the device’s functions. This program will be used to determine accurately whether or not a device is operating correctly. This is the definitive function test and provides very high test coverage. Level 3 function tests are usually required even if the device possesses self-testing capabilities, because self-tests generally are not capable of complete detection of function failures.

The level 2R program will typically consist of a subset of the level 3 function test. It will test as much of the device’s functionality as can be tested in the user (VMS) environment. The tests it contains are exact or approximate copies of tests existing in the level 3 program.

A typical sequence of use for these programs, when dealing with a system at a customer site, is as follows:

# The customer (or field service) suspects a fault existing in the device.
# The level 2R program is run to see if the error can be detected without stopping the operating system. If the error is found, go to step 4.
# If the level 2R program cannot identify the fault, the operating system is brought down and the level 3 function test is run.
# The fault is identified and the failing [[Field Replacable Unit|FRU]] is replaced. The operating system is then brought back up.
# The failing FRU is brought back to DIGITAL, where the level 3 logic test, the level 3 function test, or perhaps a module test station is used to identify the failing logic on the FRU. The FRU is repaired.

== VAX Diagnostic Coding Convention ==

VAX diagnostic program names consist of 5 letters and a two-digit version number, e.g.: ECKAL-3.4:

* E = VAX
* C = 11/750
* K = CPU
* A = Supervisor
* L = Unique identifier
* 3 = Major revision
* 4 = Minor Revision

See the following 1986 VAX Diagnostic Coding Convention Table for letter breakdown:

EPXYD-R.P

E = System

E = VAX

P = Processor

B = VAX 8200/8300
D = VAX 8600
S = VAX 11780
T = VAX 11785
C = VAX 11750
N = VAX 11730 and 11725
H = MicroVAX I
V = More than one VAX Processor
X = VAX 6000
Z = VAX 8530/8550/8700/8800

X = Device Category

A = Application (CR, LP, A-D, Misc.)
C = Channel Adaptors (MBA, UBA)
D = Communication Devices (DMC, DZ11)
G = CI Adapter
K = CPU
L = Database Files
M = Magnetic Tape (TE, TU, DT)
P = Test Equipment
Q = QIO Device Driver
R = Rotating Memory (RP, RK, RM, RS, RX)
S = System Monitor (Supervisor, Tape Monitor)
T = Terminal (LA36, VT52)
U = Utilities (Script file, Copy, Update)
W = Workstations
X = System Exerciser (EXR/BUSINT)
Z = Media Packages
0-9 = Engineering File

Y = Device Type

Category Application
A = Line Printers, LP, LCP01
B = Card Readers, CR
L = LPA11-K
Category Channel
A = MBA
B = UBA, DWBUA
C = MA780
D = IEC11, IEU11-A, DR70
E = DT07
F = DEC DATAWAY
G = CI780
H = CI750/CI780 MICROCODE VERIFICATION (INTERNAL)
I = TEST BED ADAPTERS
J = NBI ADAPTER
K = CIBCI

Category Communications
A = DZ11,DZ32,DMZ32,DHU11,DMB32
B = DMC
C = Multiple Devices
D = DR11-C
E = DV11
F = DR780,DF11-W
G = DQS11
H = KMC11-B
I = KMS11-B
J = DM11-BA
K = DMS11-BA
L = DMF32 Combo
M = DMC11,DMR11,DMP11
N = DN11
O = CPI32
P = PCL11
R = DR11B,DR11-W,DRE11
S = DRS11/DSS
T = KCT32-A,FEPCM
U = DUP11
X = Multiple Devices
W = UNA
Y = DEBNT

Category Database Files
A = CRD DATABASE FILES
B = SYSTEM EXERCISER DATABASE FILES

Category Magnetic Tape
A = TE16/77, TS11, TU78, TS05
B = TU81,TU80

Category QIO Device Drivers
For this category, the fourth and fifth letters of the code are the device mnemonic.
For example, EVQDB is the QIO device driver for the DB, or RP disk series.

Category Test Equipment
A = CI780 Node Tester
B = NI Tester

Category Rotating Memory
A = Multiple devices
B = RP04/5/6
C = DCL/RP04/5/6
D = RM03/RM05/RM80
E = RK611,RK06,RK07
F = RL02
G = RM80
H = RP07
I = RX02
J = ML11
K = IDC
L = UDA50(RA60,RA80,RA81)
M = RC25
N = RUX50

Category System Monitor
A = Supervisor
B = Autosizer
C = DYDDM

Category Terminals
A = All Terminals
B = Terminal exerciser
C = VS11
D = 11C03-LH Fastek
G = VS70

Category Utility
A = Script File
B = Copy Command file
C = Updating file

Category Workstation
A = VS100

Category Exerciser
B = Exerciser Bus Interaction

D = Fifth character makes the code unique. A through Z and 1 through 9.

R = Revision (MAJOR)
P = Revision (MINOR)

== Distribution of Diagnostic Programs ==

Typically, a VAX computer came with all the necessary diagnostic programs on console media at no additional charge, e.g.:

* VAX-11/780: [[RX01/02 floppy drive|RX01 floppies]]
* VAX-11/750, VAX-11/730, and VAX-11/725: [[TU58 DECtape II|TU58 cartridges]]
* VAX 8600: [[RL01/02 disk drive|RL02 disk pack]]
* VAX 8200, VAX 8250, VAX 8300, and VAX 8350: [[RX50 dual-diskette drive|RX50 floppies]]

Additionally, you could buy larger collections of diagnostic programs on [[magnetic tape]] or [[Removable-pack disk|removable disk packs]].

Extended documentation was available on microfiche at an extra charge.

== VMS User Enviroment Test Package (UETP) ==

From the very beginning of VMS V1.0 there was the '''[[User Enviroment Test Package]]''' (UETP), see: [http://bitsavers.trailing-edge.com/pdf/dec/vax/vms/2.0/AA-D643B-TE_VAX-VMS_2.0_UETP_Users_Guide_198003.pdf VAX/VMS UETP User’s Guide AA-D643A-TE]

Quote from the first UETP manual:

"''The UETP is a collection of tests designed to demonstrate that the hardware and software components of a VAX/VMS system are in working order. DIGITAL software support representatives run the UETP on a newly installed VAX/VMS system as the formal sample procedure.''"

UETP is still used in the latest version of VMS (V9.2-2 for x86 as of this writing).

[https://docs.vmssoftware.com/vsi-openvms-system-manager-s-manual-volume-2-tuning-monitoring-and-complex-systems/#_6017UETP| See here] for the latest VMS UETP manual.

== ULTRIX System Exerciser Package ==

[[ULTRIX]] has got a very similar tool to verify proper hardware operation at the operating system level, the '''[[System Exerciser Package]]'''.

For the earliest reference found so far see the manual: [https://drive.google.com/file/d/1i3LoLAvTQC7dZl-T9X3SsQgg_6s_6TCY/view?usp=sharing ULTRIX-32 2.2 System Exercisers 1987 AA-KS95A-TE]

The MIPS variants of ULTRIX include the System Exerciser Package, too.

== Additional Diagnostic Tools ==

* On-board ROM-based diagnostics (RBDs) / Self-tests
* [[Diagnostic and Utility Protocol|DUP]] for [[Mass Storage Control Protocol|MSCP]] devices

== CPU-specific Supervisors ==

* '''EBSAA''' VAX 8200/8250/8300/8350 & VS8000 Diagnostic Supervisor
* '''ECSAA''' VAX-11/750 DIAGNOSTIC SUPERVISOR
* '''EDSAA''' VAX 8600/8650 Diagnostic Supervisor
* '''EHSAA''' MicroVAX I VDS
* '''EJSAA''' VAX 8820/8830/8840 Diagnostic Supervisor
* '''ELSAA''' VAX 6210/6220/6230/6240/6310/6320/6330/6340/6350/6360 Diagnostic Supervisor
* '''ENSAA''' VAX 725/730 Diagnostic Supervisor
* '''ESSAA''' VAX 780/785 Diagnostic Supervisor
* '''EXSAA''' VAX 6000 Diagnostic Supervisor
* '''EZSAA''' VAX 8530/8550/8700/8800/8820N Diagnostic Supervisor
* '''E?SAA''' VAX9000 Diagnostic Supervisor

There is no supervisor for the series of VAX 7000 / VAX 10000 computers (see: [http://www.vaxhaven.com/images/4/4d/EK-7001A-TS-001.pdf VAX 7000 Advanced Troubleshooting EK-7001A-TS-001])

== Set of Diagnostics for a SV-BXTAA VAX-11/750 System ==

A SV-BXTAA VAX-11/750 System consists of:

* [[KA750 CPU|VAX-11/750 CPU]]
* [[MS750 Memory System|MS750 1MB memory]]
* [[DECwriter IV|LA38 printing console terminal]]
* [[RH750 Massbus Adapter]]
* [[RM02/03 disk drive|RM03 MASSBUS disk drive subsystem]]
* [[DZ11 asynchronous serial line interface|DZ11 terminal adapter]]
* [[TS11 Subsystem|TS11 magnetic tape unit]]

The diagnostics set for this system is made of:

* CPU-specific diagnostic main program
** '''ECSAA''' VAX 11750 DIAG SUPERVISOR

* VAX-common automatic sizing program which automatically determines the current system configuration
** '''EVSBA''' VAX AUTOSIZER DIAGNOSTIC

* Set of VAX-11/750 CPU diagnostics
** '''ECKAA''' VAX 11750 UDIAG MON
** '''ECKAB''' VAX 11750 MICRO DPM
** '''ECKAC''' VAX 11750 MICRO MIC
** '''ECKAD''' VAX FP750 MICRODIAG
** '''ECKAF''' VAX KC750 UDIAG
** '''ECKAL''' VAX 11750 CACHE/TB DIAG
** '''ECKAM''' VAX 11750 MEMORY DIAG
** '''ECKAX''' VAX 11750 CLUSTER EXER

* VAX-common instruction set diagnostic
** '''EVKAA''' VAX INSTRUCTION SET TEST

* VAX-11/750 bus diagnostics
** '''ECCAA''' VAX 11750 RH750 DIAG
** '''ECCBA''' VAX 11750 UBI/DW750 DIAG

* Set of VAX-common peripheral diagnostics
** '''EVTAA''' VAX TERMINAL DIAGNOSTIC
** '''EVTBA''' VAX TERMINAL EXERCISER
** '''EVDAA''' VAX DZ11 8 LINE ASYNC MUX
** '''EVMAA''' VAX TM03/TE16/TU45-77 Tape
** '''EVRDA''' VAX RM03/RM05/RM80 DISKLESS
** '''EVRDB''' VAX RM03/RM05 FUNCTIONAL TEST

== Booting the VAX Diagnostic Supervisor ==

The command to boot the VAX Diagnostic Supervisor on a SIMH VAX is:

BOOT RQ0 /R5:10

* <code>RQ0</code> is the device identifier for the MSCP disk, unit 0, where the diagnostics are stored; adjust this according to your requirements.
* <code>/R5:10</code> is the boot flag to boot the Diagnostic Supervisor located in directory <code>DUA0:[SYSMAINT]</code> or <code>DUA0:[SYS0.SYSMAINT]</code>.

For booting the VAX Diagnostic Supervisor on a real VAX refer chapter 2.1 of the "'''VAX DS Diagnostic Supervisor User's Guide'''" [[#ref_1|[1]]]

== Sample run of the VDS EVSBA AUTOSIZER ==

DS> '''LOAD EVSBA.EXE'''
DS> '''SET FLAGS QUICK'''
DS> '''START /SECTION:MANUAL'''

.. Program: EVSBA - AUTOSIZER LEVEL 3, revision 5.1, 3 tests,
at 18:18:28.19.

COMMAND? '''HELP'''

HELP

This is a manual section command. This program creates ATTACH
commands for all devices in the system.
(ATTACH,CHANGE,EXIT,HELP,LIST,READ,SIZE,WRITE) - These commands
control the sizer in manual and selftest mode.
To obtain further information type HELP followed by a topic.
For example;
HELP MANUAL

Additional information available:

ATTACH CHANGE DEFAULT DEVICE EVENT
EXIT HELP LIST MANUAL QUICK
READ SECTION SELFTEST SCRIPT SIZE
SUMMARY WRITE

COMMAND? '''SIZE'''
COMMAND? '''LIST'''
FILE IN MEMORY 'CONFIG.COM'
!! AUTOMATIC SIZING PROGRAM.
!! THIS IS A TOOL AND NOT A DIAGNOSTIC PROGRAM.
!! CONFIGURATION FILE FOR SYSTEM.
!! COMPUTER GENERATED CPU TYPE 2 MICROCODE REV LEVEL = 99
!! NUMERIC VALUES WITH A LEADING ZERO ARE ASSIGNED.
!! FILE VALID ONLY FOR STANDARD HARDWARE CONFIGURATION.
!! TIME IS 15-FEB-1984 18:18:56.85
!!
!! *** QUICK FLAG SET. NO CHECKS MADE FOR TERMINALS ON DZ11/DZ32'S ***
!!
!!
!! DEFINE PROCESSOR...
!!
DS> ATTACH KA750 HUB KA0 YES YES YES 027FF 0
!!
!! DEFINE MEMORY...
!!
DS> ATTACH MS750 MS0
!!
!! DEFINE UNIBUS ADAPTERS...
!!
DS> ATTACH DW750 HUB DW0
!!
DS> ATTACH LP11 DW0 LPA 777514 0200 04
DS> ATTACH LP25 LPA LPA0 !! *** PRINTER TYPE IS ESTIMATED ***
DS> ATTACH TS11 DW0 MSA0 772520 0224 05
DS> ATTACH UDA50 DW0 DUA 772150 0154 05 02
DS> ATTACH RA81 DUA DUA0
DS> ATTACH RA60 DUA DJA2
DS> ATTACH RX50 DUA DUA3
DS> ATTACH DZ11 DW0 TTA 760100 0300 05 EIA
DS> ATTACH DZ11 DW0 TTB 760110 0310 05 EIA
DS> ATTACH DZ11 DW0 TTC 760120 0320 05 EIA
DS> ATTACH DZ11 DW0 TTD 760130 0330 05 EIA
COMMAND? '''WRITE'''
CONFIGURATION FILE IS NORMALLY READ/WRITTEN TO THE SUPERVISOR CONSOLE MEDIA
VERIFY SUPERVISOR CONSOLE MEDIA LOADED.
VERIFIED? [(Yes), No] '''YES'''
COMMAND? '''EXIT'''
DS>

== See also ==

* [[Running VDS Diagnostics on the SIMH VAX-11/750]]

== External links ==

This page contains condensed information from several DEC manuals, among others:

* [http://bitsavers.org/pdf/dec/vax/diag/EP-EVNDX-25.0_Oct86.txt EVNDX25 VAX DIAGNOSTIC INDEX]
* [https://vt100.net/mirror/hcps/si75fin1.pdf EK-SI75F-IN-001 VAX-11-750 Installation Manual] pdf-page 60ff
* <div id="ref_1">[1] [http://bitsavers.org/pdf/dec/vax/diag/VAX_Diagnostic_Supervisor_Users_Guide_Apr89.pdf AA-FK66A-TE VAX DS Diagnostic Supervisor User's Guide] </div>
* [http://bitsavers.org/pdf/dec/vax/diag/EK-1VAXD-TM-001_VAX_Diagnostic_Design_Guide_Aug79.pdf EK-1VAXD-TM-003 VAX Diagnostic Design Guide]
* [http://bitsavers.org/pdf/dec/vax/diag/AA-FK67A-TE_VAX_Diagnostic_Design_Guide_Apr89.pdf AA-FK67A-TE VAX Diagnostic Design Guide]
* [http://www.bitsavers.org/pdf/dec/vax/vms/1.5/2b/AA-D643A-TE_VAX_VMS_UETP_Users_Guide_Aug78.pdf AA-D643A-TE VAX/VMS UETP User’s Guide]
* [http://www.trailing-edge.com/~shoppa/11780diags/ VAX-11/780 Diagnostic Help Files]
* [https://manx-docs.org/collections/antonio/dec/MDS-2000-01/cd1/VAX/7001ATS1.PDF EK-7001A-TS-001 VAX 7000 Advanced Troubleshooting]

[[Category: VAX]]
[[Category: VAX Software]]
[[Category: VAX Diagnostic Software]]
[[Category: SIMH Tutorials]]
[[Category: VMS Practical Guides]]

VAX Diagnostic Supervisor

2025-11-11T20:54:26Z

Vaxorcist: /* VAX Diagnostic Coding Convention */ Processor code "X" for VAX 6000 added

VDS - '''VAX Diagnostic Supervisor''' (sometimes abbreviated to VAX/DS) is a set of diagnostic software programs for the [[DEC]] [[VAX]] computers and peripheral devices.

== Intro ==

'''''"At best, a computer is as good as its diagnostic tools!"'''''

That's what they must have thought at DEC when they developed their diagnostic software.

Here we will take a closer look at the VAX Diagnostic Supervisor and also a quick side look at the [[User Environment Test Package]] (UETP).

== Using VDS for simulated VAX Computers ==

You may ask: "What are the VAX diagnostics good for when run on a simulated VAX?"

Yes, many diagnostics do not run on a simulated VAX, but some work very well and are used e.g. for testing the various [[SIMH]] VAX simulators for correct execution of the VAX native mode instructions.

Furthermore you can explore how precise the simulation mimics the real hardware.

If you plan to test your real VAX, you can familiarize yourself with VDS and prepare your diagnosis in SIMH, and SIMH can assist you in preparing and creating a diagnostic kit on media appropriate for your VAX.

Automated testing script for a SIMH VAX-11/750:

SET CLOCK NOCALIBRATE=600K
ATTACH -RQ RQ0 VAX_MINIMUM_DIAGS.dsk
EXPECT "DS> " SEND "ATTACH UDA50 DW0 DUA 772150 154 5 10\r"; GO -Q
EXPECT "DS> " SEND "ATTACH RA81 DUA DUA0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH KA750 CMI KA0 yes yes yes 0 0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH DW750 CMI DW0 8\r"; GO -Q
EXPECT "DS> " SEND "SET LOAD DUA0:[SYSMAINT]\r"; GO -Q
EXPECT "DS> " SEND "SELECT KA0\r"; GO -Q
EXPECT "DS> " SEND "SET FLAGS TRACE\r"; GO -Q
EXPECT "DS> " SEND "RUN EVKAB\r"; GO -Q
BOOT -Q RQ0 /R5:10

== VDS History ==

VDS development began in parallel that to the first [[VAX]] model, the [[VAX-11/780]] in 1977.

VDS was provided soley for the '''''"big VAXen"''''' (i.e. not for the [[MicroVAX]] and [[VAXstation]] computers), with one remarkable exception, the [[MicroVAX I]], resp. [[VAXstation I]].
Each new VAX model received its CPU-specific VDS modules up to the [[VAX 9000]]; only the VAX models of the last two series, [[VAX 7000]] and [[VAX 10000]], were covered by other diagnostic methods.

== Program Levels ==

All VAX diagnostic programs are assigned to a '''level'''. Levels are numbered 1, 2R, 2, 3, 4, and 5. A program’s level indicates its run-time environment.

* '''Level 1''' diagnostic programs run under an operating system. They do not use the VAX/DS. (=> UETP)
* '''Level 2R''' diagnostic programs run under VAX/DS in user mode only.
* '''Level 2''' diagnostic programs run in both user mode and standalone mode, under the control of the VAX/DS.
* '''Level 3''' diagnostic programs run only in standalone mode, under the control of the VAX/DS.
* '''Level 4''' diagnostic programs run in standalone without VAX/DS.
* '''level 5''' diagnostic programs run in [[Writable Control Store|WCS]] or system console, not in VAX main memory. They do not use the VAX/DS.

Only the levels 2R, 2, and 3 are managed by VDS.

== Sections, Tests, Subtests, and Flags ==

All diagnostic programs that run under the VAX/DS are composed of one or more '''sections'''. Each section has a name, and it is possible to specify, by name, which section of the program to execute. A program section can have one of two functions, depending on its design:

* Test a certain major portion of the unit under test.
* Facilitate a certain mode of testing. For example, there might be a quick-verify section, used to give the device a quick (but not thorough) test.

In order to determine the number and names of the sections in a particular diagnostic program, use the <code>SHOW SECTIONS</code> command. However, every program contains a default section called <code>DEFAULT</code>, which will execute automatically if you do not specifically select a section. A section is selected with the <code>/SECTION</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Each section is composed of a set of '''tests'''; each test verifies either a particular function of the hardware or a particular subset of the component logic being tested. The VAX/DS allows you to specify which tests within a section to run. Each test may have some '''subtests'''. Tests are selected with the <code>/TEST</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Two sets of '''flags''' are provided to control certain aspects of a diagnostic program’s execution. These flags may be set or cleared before the diagnostic program is started.

One set of flags is called the '''VAX/DS control flags'''. The flags in this set are interpreted by the VAX/DS and their meanings are the same in all diagnostic programs. The VAX/DS control flags are set with the <code>SET FLAGS</code> command.

The other set of flags is referred to as the '''event flags'''. This set consists of 23 flags whose purposes are defined by the diagnostic programs. The user must read the documentation for specific diagnostic programs to determine if a definition has been assigned to any of the event flags. <code>SET EVENT FLAGS</code> command.

== Some useful VDS commands ==

* <code>'''LOAD''' Exxxx</code> Load diagnostic Exxxx (where "Exxxx" is replaced by the diagnostics name, e.g. EVKAA)
* <code>'''SHOW FLAGS'''</code> Show VDS flags
* <code>'''SHOW TESTS'''</code> Show the available tests of the loaded diagnostic
* <code>'''SHOW SECTIONS'''</code> Show the available sections of the loaded diagnostic
* <code>'''START/TEST='''first:last</code> Start a subset of the loaded diagnostics tests (where "first" is the test number to start with, and -optionally- "last" is the last one to execute)
* <code>'''START/SECTION='''section-name</code> Start a single section of the loaded diagnostic (where "section-name" is the name of the section to run)
* <code>'''START/PASSES='''count</code> Start the loaded diagnostic for "count" passes (where "count" is the number of passes to execute)
* <code>'''RUN''' exxxx'''/TEST='''first:last</code> Run a subset of the diagnostics tests
* <code>'''RUN''' exxxx'''/SECTION='''section-name</code> Run a single section of the diagnostic
* <code>'''RUN''' exxxx'''/PASSES='''count</code> Run the diagnostic for "count" passes

Use a pass count of 0 to run a program continuously. If you do this, the program will run until you type CTRL/C or a failure occurs with the HALT flag set.

== Diagnostic Program Documentation ==

Documentation provided for each diagnostic program includes:

* '''Help file'''
:: The help file is referenced with the HELP command. It contains any operating instructions that may be unique to the diagnostic program. The help file for diagnostic program EVXYZ is EVXYZ.HLP; the help file for the VAX/DS is EVSAA.HLP

* '''Documentation file'''
:: The documentation file provides a detailed description of a diagnostic program's function, run-time requirements, operating instructions, fault detection, and maintenance history, plus explanations of each test’s function and execution flow. The documentation file for diagnostic program EVXYZ is EVXYZ.DOC.

* '''Source Code listings'''
:: Source code listings of the diagnostic programs are available. All VAX/DS diagnostic programs are structured in a standard format. For example, the initialization code for every diagnostic program is always located in the same relative area within the listing. To fully understand the source code listings of a VAX/DS diagnostic program, refer to the VAX Diagnostic Design Guide.

The help file for a diagnostic program is shipped with the diagnostic program. The documentation file and source codelistings are available by ordering a [[Maintenance Documentation Service]] Option on microfiche.

== Diagnostic Scopes ==

There are two diagnostic scopes.

* A CPU-specific scope: '''CPU Cluster Testing'''
* A scope for the identical diagnostic programs for all types of VAX computers: '''Peripheral Diagnostics'''

=== CPU Cluster Testing ===

'''NOTE: The term "CPU cluster" used here means all components belonging to a CPU; there is no connection with the term [[VAXcluster|"VAXcluster" (alternatively: "VMScluster")]].'''

The VAX CPU cluster is tested by a set of programs, existing at several program levels, as follows:

* Level 5
** Console tests
** Processor tests
** Memory tests
* Level 4
** VAX instruction set test (hardcore for VDS)
** Cache and translation buffer tests (VAX-11/750 only)
* Level 3
** Memory tests (if no level 5 test possible)
** Channel adapter tests
** Cluster exerciser

'''NOTE: The term "Channel adapter" used here means bus adapter, e.g. for [[UNIBUS]] or [[MASSBUS]].'''

This set of programs implements the VAX diagnostic strategy by providing a set of building blocks by which a system may be tested, starting with the level 5 basic processor tests and ending with the level 3 cluster exerciser, which is a program meant to exercise all components of the cluster.

=== Peripheral Diagnostics ===

Thorough testing of a peripheral device requires the development of three different diagnostic programs. For each device type the following will typically (but not necessarily) exist:

* A level 3 logic test
* A level 3 function test
* A level 2R function test

This group of programs implements the diagnostic strategy by providing a facility for producing very accurate and detailed identifications of fault conditions via the level 3 programs and by also providing a method by which the device may be tested without bringing down the customer's operating system via the level 2R program.

The level 3 logic test will provide the greatest detail of error resolution, indicating which section of logic is failing. This program will be used by technicians to repair bad logic boards, and will provide very high test coverage. Some devices contain ROM-resident microprograms ("self-tests") that perform logic testing, making a level 3 logic test unnecessary.

The level 3 function test will provide a comprehensive test of all of the device’s functions. This program will be used to determine accurately whether or not a device is operating correctly. This is the definitive function test and provides very high test coverage. Level 3 function tests are usually required even if the device possesses self-testing capabilities, because self-tests generally are not capable of complete detection of function failures.

The level 2R program will typically consist of a subset of the level 3 function test. It will test as much of the device’s functionality as can be tested in the user (VMS) environment. The tests it contains are exact or approximate copies of tests existing in the level 3 program.

A typical sequence of use for these programs, when dealing with a system at a customer site, is as follows:

# The customer (or field service) suspects a fault existing in the device.
# The level 2R program is run to see if the error can be detected without stopping the operating system. If the error is found, go to step 4.
# If the level 2R program cannot identify the fault, the operating system is brought down and the level 3 function test is run.
# The fault is identified and the failing [[Field Replacable Unit|FRU]] is replaced. The operating system is then brought back up.
# The failing FRU is brought back to DIGITAL, where the level 3 logic test, the level 3 function test, or perhaps a module test station is used to identify the failing logic on the FRU. The FRU is repaired.

== VAX Diagnostic Coding Convention ==

VAX diagnostic program names consist of 5 letters and a two-digit version number, e.g.: ECKAL-3.4:

* E = VAX
* C = 11/750
* K = CPU
* A = Supervisor
* L = Unique identifier
* 3 = Major revision
* 4 = Minor Revision

See the following 1986 VAX Diagnostic Coding Convention Table for letter breakdown:

EPXYD-R.P

E = System

E = VAX

P = Processor

B = VAX 8200/8300
D = VAX 8600
S = VAX 11780
T = VAX 11785
C = VAX 11750
N = VAX 11730 and 11725
H = MicroVAX I
V = More than one VAX Processor
X = VAX 6000
Z = VAX 8530/8550/8700/8800

X = Device Category

A = Application (CR, LP, A-D, Misc.)
C = Channel Adaptors (MBA, UBA)
D = Communication Devices (DMC, DZ11)
G = CI Adapter
K = CPU
L = Database Files
M = Magnetic Tape (TE, TU, DT)
P = Test Equipment
Q = QIO Device Driver
R = Rotating Memory (RP, RK, RM, RS, RX)
S = System Monitor (Supervisor, Tape Monitor)
T = Terminal (LA36, VT52)
U = Utilities (Script file, Copy, Update)
W = Workstations
X = System Exerciser (EXR/BUSINT)
Z = Media Packages
0-9 = Engineering File

Y = Device Type

Category Application
A = Line Printers, LP, LCP01
B = Card Readers, CR
L = LPA11-K
Category Channel
A = MBA
B = UBA, DWBUA
C = MA780
D = IEC11, IEU11-A, DR70
E = DT07
F = DEC DATAWAY
G = CI780
H = CI750/CI780 MICROCODE VERIFICATION (INTERNAL)
I = TEST BED ADAPTERS
J = NBI ADAPTER
K = CIBCI

Category Communications
A = DZ11,DZ32,DMZ32,DHU11,DMB32
B = DMC
C = Multiple Devices
D = DR11-C
E = DV11
F = DR780,DF11-W
G = DQS11
H = KMC11-B
I = KMS11-B
J = DM11-BA
K = DMS11-BA
L = DMF32 Combo
M = DMC11,DMR11,DMP11
N = DN11
O = CPI32
P = PCL11
R = DR11B,DR11-W,DRE11
S = DRS11/DSS
T = KCT32-A,FEPCM
U = DUP11
X = Multiple Devices
W = UNA
Y = DEBNT

Category Database Files
A = CRD DATABASE FILES
B = SYSTEM EXERCISER DATABASE FILES

Category Magnetic Tape
A = TE16/77, TS11, TU78, TS05
B = TU81,TU80

Category QIO Device Drivers
For this category, the fourth and fifth letters of the code are the device mnemonic.
For example, EVQDB is the QIO device driver for the DB, or RP disk series.

Category Test Equipment
A = CI780 Node Tester
B = NI Tester

Category Rotating Memory
A = Multiple devices
B = RP04/5/6
C = DCL/RP04/5/6
D = RM03/RM05/RM80
E = RK611,RK06,RK07
F = RL02
G = RM80
H = RP07
I = RX02
J = ML11
K = IDC
L = UDA50(RA60,RA80,RA81)
M = RC25
N = RUX50

Category System Monitor
A = Supervisor
B = Autosizer
C = DYDDM

Category Terminals
A = All Terminals
B = Terminal exerciser
C = VS11
D = 11C03-LH Fastek
G = VS70

Category Utility
A = Script File
B = Copy Command file
C = Updating file

Category Workstation
A = VS100

Category Exerciser
B = Exerciser Bus Interaction

D = Fifth character makes the code unique. A through Z and 1 through 9.

R = Revision (MAJOR)
P = Revision (MINOR)

== Distribution of Diagnostic Programs ==

Typically, a VAX computer came with all the necessary diagnostic programs on console media at no additional charge, e.g.:

* VAX-11/780: [[RX01/02 floppy drive|RX01 floppies]]
* VAX-11/750, VAX-11/730, and VAX-11/725: [[TU58 DECtape II|TU58 cartridges]]
* VAX 8600: [[RL01/02 disk drive|RL02 disk pack]]
* VAX 8200, VAX 8250, VAX 8300, and VAX 8350: [[RX50 dual-diskette drive|RX50 floppies]]

Additionally, you could buy larger collections of diagnostic programs on [[magnetic tape]] or [[Removable-pack disk|removable disk packs]].

Extended documentation was available on microfiche at an extra charge.

== VMS User Enviroment Test Package (UETP) ==

From the very beginning of VMS V1.0 there was the '''[[User Enviroment Test Package]]''' (UETP), see: [http://bitsavers.trailing-edge.com/pdf/dec/vax/vms/2.0/AA-D643B-TE_VAX-VMS_2.0_UETP_Users_Guide_198003.pdf VAX/VMS UETP User’s Guide AA-D643A-TE]

Quote from the first UETP manual:

"''The UETP is a collection of tests designed to demonstrate that the hardware and software components of a VAX/VMS system are in working order. DIGITAL software support representatives run the UETP on a newly installed VAX/VMS system as the formal sample procedure.''"

UETP is still used in the latest version of VMS (V9.2-2 for x86 as of this writing).

[https://docs.vmssoftware.com/vsi-openvms-system-manager-s-manual-volume-2-tuning-monitoring-and-complex-systems/#_6017UETP| See here] for the latest VMS UETP manual.

== ULTRIX System Exerciser Package ==

[[ULTRIX]] has got a very similar tool to verify proper hardware operation at the operating system level, the '''[[System Exerciser Package]]'''.

For the earliest reference found so far see the manual: [https://drive.google.com/file/d/1i3LoLAvTQC7dZl-T9X3SsQgg_6s_6TCY/view?usp=sharing ULTRIX-32 2.2 System Exercisers 1987 AA-KS95A-TE]

The MIPS variants of ULTRIX include the System Exerciser Package, too.

== Additional Diagnostic Tools ==

* On-board ROM-based diagnostics (RBDs) / Self-tests
* [[Diagnostic and Utility Protocol|DUP]] for [[Mass Storage Control Protocol|MSCP]] devices

== CPU-specific Supervisors ==

* '''EBSAA''' VAX 8200/8250/8300/8350 & VS8000 Diagnostic Supervisor
* '''ECSAA''' VAX-11/750 DIAGNOSTIC SUPERVISOR
* '''EDSAA''' VAX 8600/8650 Diagnostic Supervisor
* '''EHSAA''' MicroVAX I VDS
* '''EJSAA''' VAX 8820/8830/8840 Diagnostic Supervisor
* '''ELSAA''' VAX 6210/6220/6230/6240/6310/6320/6330/6340/6350/6360 Diagnostic Supervisor
* '''ENSAA''' VAX 725/730 Diagnostic Supervisor
* '''ESSAA''' VAX 780/785 Diagnostic Supervisor
* '''EXSAA''' ???
* '''EZSAA''' VAX 8530/8550/8700/8800/8820N Diagnostic Supervisor
* '''E?SAA''' VAX9000 Diagnostic Supervisor

There is no supervisor for the series of VAX 7000 / VAX 10000 computers (see: [http://www.vaxhaven.com/images/4/4d/EK-7001A-TS-001.pdf VAX 7000 Advanced Troubleshooting EK-7001A-TS-001])

== Set of Diagnostics for a SV-BXTAA VAX-11/750 System ==

A SV-BXTAA VAX-11/750 System consists of:

* [[KA750 CPU|VAX-11/750 CPU]]
* [[MS750 Memory System|MS750 1MB memory]]
* [[DECwriter IV|LA38 printing console terminal]]
* [[RH750 Massbus Adapter]]
* [[RM02/03 disk drive|RM03 MASSBUS disk drive subsystem]]
* [[DZ11 asynchronous serial line interface|DZ11 terminal adapter]]
* [[TS11 Subsystem|TS11 magnetic tape unit]]

The diagnostics set for this system is made of:

* CPU-specific diagnostic main program
** '''ECSAA''' VAX 11750 DIAG SUPERVISOR

* VAX-common automatic sizing program which automatically determines the current system configuration
** '''EVSBA''' VAX AUTOSIZER DIAGNOSTIC

* Set of VAX-11/750 CPU diagnostics
** '''ECKAA''' VAX 11750 UDIAG MON
** '''ECKAB''' VAX 11750 MICRO DPM
** '''ECKAC''' VAX 11750 MICRO MIC
** '''ECKAD''' VAX FP750 MICRODIAG
** '''ECKAF''' VAX KC750 UDIAG
** '''ECKAL''' VAX 11750 CACHE/TB DIAG
** '''ECKAM''' VAX 11750 MEMORY DIAG
** '''ECKAX''' VAX 11750 CLUSTER EXER

* VAX-common instruction set diagnostic
** '''EVKAA''' VAX INSTRUCTION SET TEST

* VAX-11/750 bus diagnostics
** '''ECCAA''' VAX 11750 RH750 DIAG
** '''ECCBA''' VAX 11750 UBI/DW750 DIAG

* Set of VAX-common peripheral diagnostics
** '''EVTAA''' VAX TERMINAL DIAGNOSTIC
** '''EVTBA''' VAX TERMINAL EXERCISER
** '''EVDAA''' VAX DZ11 8 LINE ASYNC MUX
** '''EVMAA''' VAX TM03/TE16/TU45-77 Tape
** '''EVRDA''' VAX RM03/RM05/RM80 DISKLESS
** '''EVRDB''' VAX RM03/RM05 FUNCTIONAL TEST

== Booting the VAX Diagnostic Supervisor ==

The command to boot the VAX Diagnostic Supervisor on a SIMH VAX is:

BOOT RQ0 /R5:10

* <code>RQ0</code> is the device identifier for the MSCP disk, unit 0, where the diagnostics are stored; adjust this according to your requirements.
* <code>/R5:10</code> is the boot flag to boot the Diagnostic Supervisor located in directory <code>DUA0:[SYSMAINT]</code> or <code>DUA0:[SYS0.SYSMAINT]</code>.

For booting the VAX Diagnostic Supervisor on a real VAX refer chapter 2.1 of the "'''VAX DS Diagnostic Supervisor User's Guide'''" [[#ref_1|[1]]]

== Sample run of the VDS EVSBA AUTOSIZER ==

DS> '''LOAD EVSBA.EXE'''
DS> '''SET FLAGS QUICK'''
DS> '''START /SECTION:MANUAL'''

.. Program: EVSBA - AUTOSIZER LEVEL 3, revision 5.1, 3 tests,
at 18:18:28.19.

COMMAND? '''HELP'''

HELP

This is a manual section command. This program creates ATTACH
commands for all devices in the system.
(ATTACH,CHANGE,EXIT,HELP,LIST,READ,SIZE,WRITE) - These commands
control the sizer in manual and selftest mode.
To obtain further information type HELP followed by a topic.
For example;
HELP MANUAL

Additional information available:

ATTACH CHANGE DEFAULT DEVICE EVENT
EXIT HELP LIST MANUAL QUICK
READ SECTION SELFTEST SCRIPT SIZE
SUMMARY WRITE

COMMAND? '''SIZE'''
COMMAND? '''LIST'''
FILE IN MEMORY 'CONFIG.COM'
!! AUTOMATIC SIZING PROGRAM.
!! THIS IS A TOOL AND NOT A DIAGNOSTIC PROGRAM.
!! CONFIGURATION FILE FOR SYSTEM.
!! COMPUTER GENERATED CPU TYPE 2 MICROCODE REV LEVEL = 99
!! NUMERIC VALUES WITH A LEADING ZERO ARE ASSIGNED.
!! FILE VALID ONLY FOR STANDARD HARDWARE CONFIGURATION.
!! TIME IS 15-FEB-1984 18:18:56.85
!!
!! *** QUICK FLAG SET. NO CHECKS MADE FOR TERMINALS ON DZ11/DZ32'S ***
!!
!!
!! DEFINE PROCESSOR...
!!
DS> ATTACH KA750 HUB KA0 YES YES YES 027FF 0
!!
!! DEFINE MEMORY...
!!
DS> ATTACH MS750 MS0
!!
!! DEFINE UNIBUS ADAPTERS...
!!
DS> ATTACH DW750 HUB DW0
!!
DS> ATTACH LP11 DW0 LPA 777514 0200 04
DS> ATTACH LP25 LPA LPA0 !! *** PRINTER TYPE IS ESTIMATED ***
DS> ATTACH TS11 DW0 MSA0 772520 0224 05
DS> ATTACH UDA50 DW0 DUA 772150 0154 05 02
DS> ATTACH RA81 DUA DUA0
DS> ATTACH RA60 DUA DJA2
DS> ATTACH RX50 DUA DUA3
DS> ATTACH DZ11 DW0 TTA 760100 0300 05 EIA
DS> ATTACH DZ11 DW0 TTB 760110 0310 05 EIA
DS> ATTACH DZ11 DW0 TTC 760120 0320 05 EIA
DS> ATTACH DZ11 DW0 TTD 760130 0330 05 EIA
COMMAND? '''WRITE'''
CONFIGURATION FILE IS NORMALLY READ/WRITTEN TO THE SUPERVISOR CONSOLE MEDIA
VERIFY SUPERVISOR CONSOLE MEDIA LOADED.
VERIFIED? [(Yes), No] '''YES'''
COMMAND? '''EXIT'''
DS>

== See also ==

* [[Running VDS Diagnostics on the SIMH VAX-11/750]]

== External links ==

This page contains condensed information from several DEC manuals, among others:

* [http://bitsavers.org/pdf/dec/vax/diag/EP-EVNDX-25.0_Oct86.txt EVNDX25 VAX DIAGNOSTIC INDEX]
* [https://vt100.net/mirror/hcps/si75fin1.pdf EK-SI75F-IN-001 VAX-11-750 Installation Manual] pdf-page 60ff
* <div id="ref_1">[1] [http://bitsavers.org/pdf/dec/vax/diag/VAX_Diagnostic_Supervisor_Users_Guide_Apr89.pdf AA-FK66A-TE VAX DS Diagnostic Supervisor User's Guide] </div>
* [http://bitsavers.org/pdf/dec/vax/diag/EK-1VAXD-TM-001_VAX_Diagnostic_Design_Guide_Aug79.pdf EK-1VAXD-TM-003 VAX Diagnostic Design Guide]
* [http://bitsavers.org/pdf/dec/vax/diag/AA-FK67A-TE_VAX_Diagnostic_Design_Guide_Apr89.pdf AA-FK67A-TE VAX Diagnostic Design Guide]
* [http://www.bitsavers.org/pdf/dec/vax/vms/1.5/2b/AA-D643A-TE_VAX_VMS_UETP_Users_Guide_Aug78.pdf AA-D643A-TE VAX/VMS UETP User’s Guide]
* [http://www.trailing-edge.com/~shoppa/11780diags/ VAX-11/780 Diagnostic Help Files]
* [https://manx-docs.org/collections/antonio/dec/MDS-2000-01/cd1/VAX/7001ATS1.PDF EK-7001A-TS-001 VAX 7000 Advanced Troubleshooting]

[[Category: VAX]]
[[Category: VAX Software]]
[[Category: VAX Diagnostic Software]]
[[Category: SIMH Tutorials]]
[[Category: VMS Practical Guides]]

VAX Diagnostic Supervisor

2025-11-11T18:40:06Z

Vaxorcist: /* VAX Diagnostic Coding Convention */ Processor code "Z" decoded

VDS - '''VAX Diagnostic Supervisor''' (sometimes abbreviated to VAX/DS) is a set of diagnostic software programs for the [[DEC]] [[VAX]] computers and peripheral devices.

== Intro ==

'''''"At best, a computer is as good as its diagnostic tools!"'''''

That's what they must have thought at DEC when they developed their diagnostic software.

Here we will take a closer look at the VAX Diagnostic Supervisor and also a quick side look at the [[User Environment Test Package]] (UETP).

== Using VDS for simulated VAX Computers ==

You may ask: "What are the VAX diagnostics good for when run on a simulated VAX?"

Yes, many diagnostics do not run on a simulated VAX, but some work very well and are used e.g. for testing the various [[SIMH]] VAX simulators for correct execution of the VAX native mode instructions.

Furthermore you can explore how precise the simulation mimics the real hardware.

If you plan to test your real VAX, you can familiarize yourself with VDS and prepare your diagnosis in SIMH, and SIMH can assist you in preparing and creating a diagnostic kit on media appropriate for your VAX.

Automated testing script for a SIMH VAX-11/750:

SET CLOCK NOCALIBRATE=600K
ATTACH -RQ RQ0 VAX_MINIMUM_DIAGS.dsk
EXPECT "DS> " SEND "ATTACH UDA50 DW0 DUA 772150 154 5 10\r"; GO -Q
EXPECT "DS> " SEND "ATTACH RA81 DUA DUA0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH KA750 CMI KA0 yes yes yes 0 0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH DW750 CMI DW0 8\r"; GO -Q
EXPECT "DS> " SEND "SET LOAD DUA0:[SYSMAINT]\r"; GO -Q
EXPECT "DS> " SEND "SELECT KA0\r"; GO -Q
EXPECT "DS> " SEND "SET FLAGS TRACE\r"; GO -Q
EXPECT "DS> " SEND "RUN EVKAB\r"; GO -Q
BOOT -Q RQ0 /R5:10

== VDS History ==

VDS development began in parallel that to the first [[VAX]] model, the [[VAX-11/780]] in 1977.

VDS was provided soley for the '''''"big VAXen"''''' (i.e. not for the [[MicroVAX]] and [[VAXstation]] computers), with one remarkable exception, the [[MicroVAX I]], resp. [[VAXstation I]].
Each new VAX model received its CPU-specific VDS modules up to the [[VAX 9000]]; only the VAX models of the last two series, [[VAX 7000]] and [[VAX 10000]], were covered by other diagnostic methods.

== Program Levels ==

All VAX diagnostic programs are assigned to a '''level'''. Levels are numbered 1, 2R, 2, 3, 4, and 5. A program’s level indicates its run-time environment.

* '''Level 1''' diagnostic programs run under an operating system. They do not use the VAX/DS. (=> UETP)
* '''Level 2R''' diagnostic programs run under VAX/DS in user mode only.
* '''Level 2''' diagnostic programs run in both user mode and standalone mode, under the control of the VAX/DS.
* '''Level 3''' diagnostic programs run only in standalone mode, under the control of the VAX/DS.
* '''Level 4''' diagnostic programs run in standalone without VAX/DS.
* '''level 5''' diagnostic programs run in [[Writable Control Store|WCS]] or system console, not in VAX main memory. They do not use the VAX/DS.

Only the levels 2R, 2, and 3 are managed by VDS.

== Sections, Tests, Subtests, and Flags ==

All diagnostic programs that run under the VAX/DS are composed of one or more '''sections'''. Each section has a name, and it is possible to specify, by name, which section of the program to execute. A program section can have one of two functions, depending on its design:

* Test a certain major portion of the unit under test.
* Facilitate a certain mode of testing. For example, there might be a quick-verify section, used to give the device a quick (but not thorough) test.

In order to determine the number and names of the sections in a particular diagnostic program, use the <code>SHOW SECTIONS</code> command. However, every program contains a default section called <code>DEFAULT</code>, which will execute automatically if you do not specifically select a section. A section is selected with the <code>/SECTION</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Each section is composed of a set of '''tests'''; each test verifies either a particular function of the hardware or a particular subset of the component logic being tested. The VAX/DS allows you to specify which tests within a section to run. Each test may have some '''subtests'''. Tests are selected with the <code>/TEST</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Two sets of '''flags''' are provided to control certain aspects of a diagnostic program’s execution. These flags may be set or cleared before the diagnostic program is started.

One set of flags is called the '''VAX/DS control flags'''. The flags in this set are interpreted by the VAX/DS and their meanings are the same in all diagnostic programs. The VAX/DS control flags are set with the <code>SET FLAGS</code> command.

The other set of flags is referred to as the '''event flags'''. This set consists of 23 flags whose purposes are defined by the diagnostic programs. The user must read the documentation for specific diagnostic programs to determine if a definition has been assigned to any of the event flags. <code>SET EVENT FLAGS</code> command.

== Some useful VDS commands ==

* <code>'''LOAD''' Exxxx</code> Load diagnostic Exxxx (where "Exxxx" is replaced by the diagnostics name, e.g. EVKAA)
* <code>'''SHOW FLAGS'''</code> Show VDS flags
* <code>'''SHOW TESTS'''</code> Show the available tests of the loaded diagnostic
* <code>'''SHOW SECTIONS'''</code> Show the available sections of the loaded diagnostic
* <code>'''START/TEST='''first:last</code> Start a subset of the loaded diagnostics tests (where "first" is the test number to start with, and -optionally- "last" is the last one to execute)
* <code>'''START/SECTION='''section-name</code> Start a single section of the loaded diagnostic (where "section-name" is the name of the section to run)
* <code>'''START/PASSES='''count</code> Start the loaded diagnostic for "count" passes (where "count" is the number of passes to execute)
* <code>'''RUN''' exxxx'''/TEST='''first:last</code> Run a subset of the diagnostics tests
* <code>'''RUN''' exxxx'''/SECTION='''section-name</code> Run a single section of the diagnostic
* <code>'''RUN''' exxxx'''/PASSES='''count</code> Run the diagnostic for "count" passes

Use a pass count of 0 to run a program continuously. If you do this, the program will run until you type CTRL/C or a failure occurs with the HALT flag set.

== Diagnostic Program Documentation ==

Documentation provided for each diagnostic program includes:

* '''Help file'''
:: The help file is referenced with the HELP command. It contains any operating instructions that may be unique to the diagnostic program. The help file for diagnostic program EVXYZ is EVXYZ.HLP; the help file for the VAX/DS is EVSAA.HLP

* '''Documentation file'''
:: The documentation file provides a detailed description of a diagnostic program's function, run-time requirements, operating instructions, fault detection, and maintenance history, plus explanations of each test’s function and execution flow. The documentation file for diagnostic program EVXYZ is EVXYZ.DOC.

* '''Source Code listings'''
:: Source code listings of the diagnostic programs are available. All VAX/DS diagnostic programs are structured in a standard format. For example, the initialization code for every diagnostic program is always located in the same relative area within the listing. To fully understand the source code listings of a VAX/DS diagnostic program, refer to the VAX Diagnostic Design Guide.

The help file for a diagnostic program is shipped with the diagnostic program. The documentation file and source codelistings are available by ordering a [[Maintenance Documentation Service]] Option on microfiche.

== Diagnostic Scopes ==

There are two diagnostic scopes.

* A CPU-specific scope: '''CPU Cluster Testing'''
* A scope for the identical diagnostic programs for all types of VAX computers: '''Peripheral Diagnostics'''

=== CPU Cluster Testing ===

'''NOTE: The term "CPU cluster" used here means all components belonging to a CPU; there is no connection with the term [[VAXcluster|"VAXcluster" (alternatively: "VMScluster")]].'''

The VAX CPU cluster is tested by a set of programs, existing at several program levels, as follows:

* Level 5
** Console tests
** Processor tests
** Memory tests
* Level 4
** VAX instruction set test (hardcore for VDS)
** Cache and translation buffer tests (VAX-11/750 only)
* Level 3
** Memory tests (if no level 5 test possible)
** Channel adapter tests
** Cluster exerciser

'''NOTE: The term "Channel adapter" used here means bus adapter, e.g. for [[UNIBUS]] or [[MASSBUS]].'''

This set of programs implements the VAX diagnostic strategy by providing a set of building blocks by which a system may be tested, starting with the level 5 basic processor tests and ending with the level 3 cluster exerciser, which is a program meant to exercise all components of the cluster.

=== Peripheral Diagnostics ===

Thorough testing of a peripheral device requires the development of three different diagnostic programs. For each device type the following will typically (but not necessarily) exist:

* A level 3 logic test
* A level 3 function test
* A level 2R function test

This group of programs implements the diagnostic strategy by providing a facility for producing very accurate and detailed identifications of fault conditions via the level 3 programs and by also providing a method by which the device may be tested without bringing down the customer's operating system via the level 2R program.

The level 3 logic test will provide the greatest detail of error resolution, indicating which section of logic is failing. This program will be used by technicians to repair bad logic boards, and will provide very high test coverage. Some devices contain ROM-resident microprograms ("self-tests") that perform logic testing, making a level 3 logic test unnecessary.

The level 3 function test will provide a comprehensive test of all of the device’s functions. This program will be used to determine accurately whether or not a device is operating correctly. This is the definitive function test and provides very high test coverage. Level 3 function tests are usually required even if the device possesses self-testing capabilities, because self-tests generally are not capable of complete detection of function failures.

The level 2R program will typically consist of a subset of the level 3 function test. It will test as much of the device’s functionality as can be tested in the user (VMS) environment. The tests it contains are exact or approximate copies of tests existing in the level 3 program.

A typical sequence of use for these programs, when dealing with a system at a customer site, is as follows:

# The customer (or field service) suspects a fault existing in the device.
# The level 2R program is run to see if the error can be detected without stopping the operating system. If the error is found, go to step 4.
# If the level 2R program cannot identify the fault, the operating system is brought down and the level 3 function test is run.
# The fault is identified and the failing [[Field Replacable Unit|FRU]] is replaced. The operating system is then brought back up.
# The failing FRU is brought back to DIGITAL, where the level 3 logic test, the level 3 function test, or perhaps a module test station is used to identify the failing logic on the FRU. The FRU is repaired.

== VAX Diagnostic Coding Convention ==

VAX diagnostic program names consist of 5 letters and a two-digit version number, e.g.: ECKAL-3.4:

* E = VAX
* C = 11/750
* K = CPU
* A = Supervisor
* L = Unique identifier
* 3 = Major revision
* 4 = Minor Revision

See the following 1986 VAX Diagnostic Coding Convention Table for letter breakdown:

EPXYD-R.P

E = System

E = VAX

P = Processor

B = VAX 8200/8300
D = VAX 8600
S = VAX 11780
T = VAX 11785
C = VAX 11750
N = VAX 11730 and 11725
H = MicroVAX I
V = More than one VAX Processor
Z = VAX 8530/8550/8700/8800

X = Device Category

A = Application (CR, LP, A-D, Misc.)
C = Channel Adaptors (MBA, UBA)
D = Communication Devices (DMC, DZ11)
G = CI Adapter
K = CPU
L = Database Files
M = Magnetic Tape (TE, TU, DT)
P = Test Equipment
Q = QIO Device Driver
R = Rotating Memory (RP, RK, RM, RS, RX)
S = System Monitor (Supervisor, Tape Monitor)
T = Terminal (LA36, VT52)
U = Utilities (Script file, Copy, Update)
W = Workstations
X = System Exerciser (EXR/BUSINT)
Z = Media Packages
0-9 = Engineering File

Y = Device Type

Category Application
A = Line Printers, LP, LCP01
B = Card Readers, CR
L = LPA11-K
Category Channel
A = MBA
B = UBA, DWBUA
C = MA780
D = IEC11, IEU11-A, DR70
E = DT07
F = DEC DATAWAY
G = CI780
H = CI750/CI780 MICROCODE VERIFICATION (INTERNAL)
I = TEST BED ADAPTERS
J = NBI ADAPTER
K = CIBCI

Category Communications
A = DZ11,DZ32,DMZ32,DHU11,DMB32
B = DMC
C = Multiple Devices
D = DR11-C
E = DV11
F = DR780,DF11-W
G = DQS11
H = KMC11-B
I = KMS11-B
J = DM11-BA
K = DMS11-BA
L = DMF32 Combo
M = DMC11,DMR11,DMP11
N = DN11
O = CPI32
P = PCL11
R = DR11B,DR11-W,DRE11
S = DRS11/DSS
T = KCT32-A,FEPCM
U = DUP11
X = Multiple Devices
W = UNA
Y = DEBNT

Category Database Files
A = CRD DATABASE FILES
B = SYSTEM EXERCISER DATABASE FILES

Category Magnetic Tape
A = TE16/77, TS11, TU78, TS05
B = TU81,TU80

Category QIO Device Drivers
For this category, the fourth and fifth letters of the code are the device mnemonic.
For example, EVQDB is the QIO device driver for the DB, or RP disk series.

Category Test Equipment
A = CI780 Node Tester
B = NI Tester

Category Rotating Memory
A = Multiple devices
B = RP04/5/6
C = DCL/RP04/5/6
D = RM03/RM05/RM80
E = RK611,RK06,RK07
F = RL02
G = RM80
H = RP07
I = RX02
J = ML11
K = IDC
L = UDA50(RA60,RA80,RA81)
M = RC25
N = RUX50

Category System Monitor
A = Supervisor
B = Autosizer
C = DYDDM

Category Terminals
A = All Terminals
B = Terminal exerciser
C = VS11
D = 11C03-LH Fastek
G = VS70

Category Utility
A = Script File
B = Copy Command file
C = Updating file

Category Workstation
A = VS100

Category Exerciser
B = Exerciser Bus Interaction

D = Fifth character makes the code unique. A through Z and 1 through 9.

R = Revision (MAJOR)
P = Revision (MINOR)

== Distribution of Diagnostic Programs ==

Typically, a VAX computer came with all the necessary diagnostic programs on console media at no additional charge, e.g.:

* VAX-11/780: [[RX01/02 floppy drive|RX01 floppies]]
* VAX-11/750, VAX-11/730, and VAX-11/725: [[TU58 DECtape II|TU58 cartridges]]
* VAX 8600: [[RL01/02 disk drive|RL02 disk pack]]
* VAX 8200, VAX 8250, VAX 8300, and VAX 8350: [[RX50 dual-diskette drive|RX50 floppies]]

Additionally, you could buy larger collections of diagnostic programs on [[magnetic tape]] or [[Removable-pack disk|removable disk packs]].

Extended documentation was available on microfiche at an extra charge.

== VMS User Enviroment Test Package (UETP) ==

From the very beginning of VMS V1.0 there was the '''[[User Enviroment Test Package]]''' (UETP), see: [http://bitsavers.trailing-edge.com/pdf/dec/vax/vms/2.0/AA-D643B-TE_VAX-VMS_2.0_UETP_Users_Guide_198003.pdf VAX/VMS UETP User’s Guide AA-D643A-TE]

Quote from the first UETP manual:

"''The UETP is a collection of tests designed to demonstrate that the hardware and software components of a VAX/VMS system are in working order. DIGITAL software support representatives run the UETP on a newly installed VAX/VMS system as the formal sample procedure.''"

UETP is still used in the latest version of VMS (V9.2-2 for x86 as of this writing).

[https://docs.vmssoftware.com/vsi-openvms-system-manager-s-manual-volume-2-tuning-monitoring-and-complex-systems/#_6017UETP| See here] for the latest VMS UETP manual.

== ULTRIX System Exerciser Package ==

[[ULTRIX]] has got a very similar tool to verify proper hardware operation at the operating system level, the '''[[System Exerciser Package]]'''.

For the earliest reference found so far see the manual: [https://drive.google.com/file/d/1i3LoLAvTQC7dZl-T9X3SsQgg_6s_6TCY/view?usp=sharing ULTRIX-32 2.2 System Exercisers 1987 AA-KS95A-TE]

The MIPS variants of ULTRIX include the System Exerciser Package, too.

== Additional Diagnostic Tools ==

* On-board ROM-based diagnostics (RBDs) / Self-tests
* [[Diagnostic and Utility Protocol|DUP]] for [[Mass Storage Control Protocol|MSCP]] devices

== CPU-specific Supervisors ==

* '''EBSAA''' VAX 8200/8250/8300/8350 & VS8000 Diagnostic Supervisor
* '''ECSAA''' VAX-11/750 DIAGNOSTIC SUPERVISOR
* '''EDSAA''' VAX 8600/8650 Diagnostic Supervisor
* '''EHSAA''' MicroVAX I VDS
* '''EJSAA''' VAX 8820/8830/8840 Diagnostic Supervisor
* '''ELSAA''' VAX 6210/6220/6230/6240/6310/6320/6330/6340/6350/6360 Diagnostic Supervisor
* '''ENSAA''' VAX 725/730 Diagnostic Supervisor
* '''ESSAA''' VAX 780/785 Diagnostic Supervisor
* '''EXSAA''' ???
* '''EZSAA''' VAX 8530/8550/8700/8800/8820N Diagnostic Supervisor
* '''E?SAA''' VAX9000 Diagnostic Supervisor

There is no supervisor for the series of VAX 7000 / VAX 10000 computers (see: [http://www.vaxhaven.com/images/4/4d/EK-7001A-TS-001.pdf VAX 7000 Advanced Troubleshooting EK-7001A-TS-001])

== Set of Diagnostics for a SV-BXTAA VAX-11/750 System ==

A SV-BXTAA VAX-11/750 System consists of:

* [[KA750 CPU|VAX-11/750 CPU]]
* [[MS750 Memory System|MS750 1MB memory]]
* [[DECwriter IV|LA38 printing console terminal]]
* [[RH750 Massbus Adapter]]
* [[RM02/03 disk drive|RM03 MASSBUS disk drive subsystem]]
* [[DZ11 asynchronous serial line interface|DZ11 terminal adapter]]
* [[TS11 Subsystem|TS11 magnetic tape unit]]

The diagnostics set for this system is made of:

* CPU-specific diagnostic main program
** '''ECSAA''' VAX 11750 DIAG SUPERVISOR

* VAX-common automatic sizing program which automatically determines the current system configuration
** '''EVSBA''' VAX AUTOSIZER DIAGNOSTIC

* Set of VAX-11/750 CPU diagnostics
** '''ECKAA''' VAX 11750 UDIAG MON
** '''ECKAB''' VAX 11750 MICRO DPM
** '''ECKAC''' VAX 11750 MICRO MIC
** '''ECKAD''' VAX FP750 MICRODIAG
** '''ECKAF''' VAX KC750 UDIAG
** '''ECKAL''' VAX 11750 CACHE/TB DIAG
** '''ECKAM''' VAX 11750 MEMORY DIAG
** '''ECKAX''' VAX 11750 CLUSTER EXER

* VAX-common instruction set diagnostic
** '''EVKAA''' VAX INSTRUCTION SET TEST

* VAX-11/750 bus diagnostics
** '''ECCAA''' VAX 11750 RH750 DIAG
** '''ECCBA''' VAX 11750 UBI/DW750 DIAG

* Set of VAX-common peripheral diagnostics
** '''EVTAA''' VAX TERMINAL DIAGNOSTIC
** '''EVTBA''' VAX TERMINAL EXERCISER
** '''EVDAA''' VAX DZ11 8 LINE ASYNC MUX
** '''EVMAA''' VAX TM03/TE16/TU45-77 Tape
** '''EVRDA''' VAX RM03/RM05/RM80 DISKLESS
** '''EVRDB''' VAX RM03/RM05 FUNCTIONAL TEST

== Booting the VAX Diagnostic Supervisor ==

The command to boot the VAX Diagnostic Supervisor on a SIMH VAX is:

BOOT RQ0 /R5:10

* <code>RQ0</code> is the device identifier for the MSCP disk, unit 0, where the diagnostics are stored; adjust this according to your requirements.
* <code>/R5:10</code> is the boot flag to boot the Diagnostic Supervisor located in directory <code>DUA0:[SYSMAINT]</code> or <code>DUA0:[SYS0.SYSMAINT]</code>.

For booting the VAX Diagnostic Supervisor on a real VAX refer chapter 2.1 of the "'''VAX DS Diagnostic Supervisor User's Guide'''" [[#ref_1|[1]]]

== Sample run of the VDS EVSBA AUTOSIZER ==

DS> '''LOAD EVSBA.EXE'''
DS> '''SET FLAGS QUICK'''
DS> '''START /SECTION:MANUAL'''

.. Program: EVSBA - AUTOSIZER LEVEL 3, revision 5.1, 3 tests,
at 18:18:28.19.

COMMAND? '''HELP'''

HELP

This is a manual section command. This program creates ATTACH
commands for all devices in the system.
(ATTACH,CHANGE,EXIT,HELP,LIST,READ,SIZE,WRITE) - These commands
control the sizer in manual and selftest mode.
To obtain further information type HELP followed by a topic.
For example;
HELP MANUAL

Additional information available:

ATTACH CHANGE DEFAULT DEVICE EVENT
EXIT HELP LIST MANUAL QUICK
READ SECTION SELFTEST SCRIPT SIZE
SUMMARY WRITE

COMMAND? '''SIZE'''
COMMAND? '''LIST'''
FILE IN MEMORY 'CONFIG.COM'
!! AUTOMATIC SIZING PROGRAM.
!! THIS IS A TOOL AND NOT A DIAGNOSTIC PROGRAM.
!! CONFIGURATION FILE FOR SYSTEM.
!! COMPUTER GENERATED CPU TYPE 2 MICROCODE REV LEVEL = 99
!! NUMERIC VALUES WITH A LEADING ZERO ARE ASSIGNED.
!! FILE VALID ONLY FOR STANDARD HARDWARE CONFIGURATION.
!! TIME IS 15-FEB-1984 18:18:56.85
!!
!! *** QUICK FLAG SET. NO CHECKS MADE FOR TERMINALS ON DZ11/DZ32'S ***
!!
!!
!! DEFINE PROCESSOR...
!!
DS> ATTACH KA750 HUB KA0 YES YES YES 027FF 0
!!
!! DEFINE MEMORY...
!!
DS> ATTACH MS750 MS0
!!
!! DEFINE UNIBUS ADAPTERS...
!!
DS> ATTACH DW750 HUB DW0
!!
DS> ATTACH LP11 DW0 LPA 777514 0200 04
DS> ATTACH LP25 LPA LPA0 !! *** PRINTER TYPE IS ESTIMATED ***
DS> ATTACH TS11 DW0 MSA0 772520 0224 05
DS> ATTACH UDA50 DW0 DUA 772150 0154 05 02
DS> ATTACH RA81 DUA DUA0
DS> ATTACH RA60 DUA DJA2
DS> ATTACH RX50 DUA DUA3
DS> ATTACH DZ11 DW0 TTA 760100 0300 05 EIA
DS> ATTACH DZ11 DW0 TTB 760110 0310 05 EIA
DS> ATTACH DZ11 DW0 TTC 760120 0320 05 EIA
DS> ATTACH DZ11 DW0 TTD 760130 0330 05 EIA
COMMAND? '''WRITE'''
CONFIGURATION FILE IS NORMALLY READ/WRITTEN TO THE SUPERVISOR CONSOLE MEDIA
VERIFY SUPERVISOR CONSOLE MEDIA LOADED.
VERIFIED? [(Yes), No] '''YES'''
COMMAND? '''EXIT'''
DS>

== See also ==

* [[Running VDS Diagnostics on the SIMH VAX-11/750]]

== External links ==

This page contains condensed information from several DEC manuals, among others:

* [http://bitsavers.org/pdf/dec/vax/diag/EP-EVNDX-25.0_Oct86.txt EVNDX25 VAX DIAGNOSTIC INDEX]
* [https://vt100.net/mirror/hcps/si75fin1.pdf EK-SI75F-IN-001 VAX-11-750 Installation Manual] pdf-page 60ff
* <div id="ref_1">[1] [http://bitsavers.org/pdf/dec/vax/diag/VAX_Diagnostic_Supervisor_Users_Guide_Apr89.pdf AA-FK66A-TE VAX DS Diagnostic Supervisor User's Guide] </div>
* [http://bitsavers.org/pdf/dec/vax/diag/EK-1VAXD-TM-001_VAX_Diagnostic_Design_Guide_Aug79.pdf EK-1VAXD-TM-003 VAX Diagnostic Design Guide]
* [http://bitsavers.org/pdf/dec/vax/diag/AA-FK67A-TE_VAX_Diagnostic_Design_Guide_Apr89.pdf AA-FK67A-TE VAX Diagnostic Design Guide]
* [http://www.bitsavers.org/pdf/dec/vax/vms/1.5/2b/AA-D643A-TE_VAX_VMS_UETP_Users_Guide_Aug78.pdf AA-D643A-TE VAX/VMS UETP User’s Guide]
* [http://www.trailing-edge.com/~shoppa/11780diags/ VAX-11/780 Diagnostic Help Files]
* [https://manx-docs.org/collections/antonio/dec/MDS-2000-01/cd1/VAX/7001ATS1.PDF EK-7001A-TS-001 VAX 7000 Advanced Troubleshooting]

[[Category: VAX]]
[[Category: VAX Software]]
[[Category: VAX Diagnostic Software]]
[[Category: SIMH Tutorials]]
[[Category: VMS Practical Guides]]

VAX Diagnostic Supervisor

2025-11-11T18:38:24Z

Vaxorcist: /* VAX Diagnostic Coding Convention */ Processor code "Z" added

VDS - '''VAX Diagnostic Supervisor''' (sometimes abbreviated to VAX/DS) is a set of diagnostic software programs for the [[DEC]] [[VAX]] computers and peripheral devices.

== Intro ==

'''''"At best, a computer is as good as its diagnostic tools!"'''''

That's what they must have thought at DEC when they developed their diagnostic software.

Here we will take a closer look at the VAX Diagnostic Supervisor and also a quick side look at the [[User Environment Test Package]] (UETP).

== Using VDS for simulated VAX Computers ==

You may ask: "What are the VAX diagnostics good for when run on a simulated VAX?"

Yes, many diagnostics do not run on a simulated VAX, but some work very well and are used e.g. for testing the various [[SIMH]] VAX simulators for correct execution of the VAX native mode instructions.

Furthermore you can explore how precise the simulation mimics the real hardware.

If you plan to test your real VAX, you can familiarize yourself with VDS and prepare your diagnosis in SIMH, and SIMH can assist you in preparing and creating a diagnostic kit on media appropriate for your VAX.

Automated testing script for a SIMH VAX-11/750:

SET CLOCK NOCALIBRATE=600K
ATTACH -RQ RQ0 VAX_MINIMUM_DIAGS.dsk
EXPECT "DS> " SEND "ATTACH UDA50 DW0 DUA 772150 154 5 10\r"; GO -Q
EXPECT "DS> " SEND "ATTACH RA81 DUA DUA0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH KA750 CMI KA0 yes yes yes 0 0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH DW750 CMI DW0 8\r"; GO -Q
EXPECT "DS> " SEND "SET LOAD DUA0:[SYSMAINT]\r"; GO -Q
EXPECT "DS> " SEND "SELECT KA0\r"; GO -Q
EXPECT "DS> " SEND "SET FLAGS TRACE\r"; GO -Q
EXPECT "DS> " SEND "RUN EVKAB\r"; GO -Q
BOOT -Q RQ0 /R5:10

== VDS History ==

VDS development began in parallel that to the first [[VAX]] model, the [[VAX-11/780]] in 1977.

VDS was provided soley for the '''''"big VAXen"''''' (i.e. not for the [[MicroVAX]] and [[VAXstation]] computers), with one remarkable exception, the [[MicroVAX I]], resp. [[VAXstation I]].
Each new VAX model received its CPU-specific VDS modules up to the [[VAX 9000]]; only the VAX models of the last two series, [[VAX 7000]] and [[VAX 10000]], were covered by other diagnostic methods.

== Program Levels ==

All VAX diagnostic programs are assigned to a '''level'''. Levels are numbered 1, 2R, 2, 3, 4, and 5. A program’s level indicates its run-time environment.

* '''Level 1''' diagnostic programs run under an operating system. They do not use the VAX/DS. (=> UETP)
* '''Level 2R''' diagnostic programs run under VAX/DS in user mode only.
* '''Level 2''' diagnostic programs run in both user mode and standalone mode, under the control of the VAX/DS.
* '''Level 3''' diagnostic programs run only in standalone mode, under the control of the VAX/DS.
* '''Level 4''' diagnostic programs run in standalone without VAX/DS.
* '''level 5''' diagnostic programs run in [[Writable Control Store|WCS]] or system console, not in VAX main memory. They do not use the VAX/DS.

Only the levels 2R, 2, and 3 are managed by VDS.

== Sections, Tests, Subtests, and Flags ==

All diagnostic programs that run under the VAX/DS are composed of one or more '''sections'''. Each section has a name, and it is possible to specify, by name, which section of the program to execute. A program section can have one of two functions, depending on its design:

* Test a certain major portion of the unit under test.
* Facilitate a certain mode of testing. For example, there might be a quick-verify section, used to give the device a quick (but not thorough) test.

In order to determine the number and names of the sections in a particular diagnostic program, use the <code>SHOW SECTIONS</code> command. However, every program contains a default section called <code>DEFAULT</code>, which will execute automatically if you do not specifically select a section. A section is selected with the <code>/SECTION</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Each section is composed of a set of '''tests'''; each test verifies either a particular function of the hardware or a particular subset of the component logic being tested. The VAX/DS allows you to specify which tests within a section to run. Each test may have some '''subtests'''. Tests are selected with the <code>/TEST</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Two sets of '''flags''' are provided to control certain aspects of a diagnostic program’s execution. These flags may be set or cleared before the diagnostic program is started.

One set of flags is called the '''VAX/DS control flags'''. The flags in this set are interpreted by the VAX/DS and their meanings are the same in all diagnostic programs. The VAX/DS control flags are set with the <code>SET FLAGS</code> command.

The other set of flags is referred to as the '''event flags'''. This set consists of 23 flags whose purposes are defined by the diagnostic programs. The user must read the documentation for specific diagnostic programs to determine if a definition has been assigned to any of the event flags. <code>SET EVENT FLAGS</code> command.

== Some useful VDS commands ==

* <code>'''LOAD''' Exxxx</code> Load diagnostic Exxxx (where "Exxxx" is replaced by the diagnostics name, e.g. EVKAA)
* <code>'''SHOW FLAGS'''</code> Show VDS flags
* <code>'''SHOW TESTS'''</code> Show the available tests of the loaded diagnostic
* <code>'''SHOW SECTIONS'''</code> Show the available sections of the loaded diagnostic
* <code>'''START/TEST='''first:last</code> Start a subset of the loaded diagnostics tests (where "first" is the test number to start with, and -optionally- "last" is the last one to execute)
* <code>'''START/SECTION='''section-name</code> Start a single section of the loaded diagnostic (where "section-name" is the name of the section to run)
* <code>'''START/PASSES='''count</code> Start the loaded diagnostic for "count" passes (where "count" is the number of passes to execute)
* <code>'''RUN''' exxxx'''/TEST='''first:last</code> Run a subset of the diagnostics tests
* <code>'''RUN''' exxxx'''/SECTION='''section-name</code> Run a single section of the diagnostic
* <code>'''RUN''' exxxx'''/PASSES='''count</code> Run the diagnostic for "count" passes

Use a pass count of 0 to run a program continuously. If you do this, the program will run until you type CTRL/C or a failure occurs with the HALT flag set.

== Diagnostic Program Documentation ==

Documentation provided for each diagnostic program includes:

* '''Help file'''
:: The help file is referenced with the HELP command. It contains any operating instructions that may be unique to the diagnostic program. The help file for diagnostic program EVXYZ is EVXYZ.HLP; the help file for the VAX/DS is EVSAA.HLP

* '''Documentation file'''
:: The documentation file provides a detailed description of a diagnostic program's function, run-time requirements, operating instructions, fault detection, and maintenance history, plus explanations of each test’s function and execution flow. The documentation file for diagnostic program EVXYZ is EVXYZ.DOC.

* '''Source Code listings'''
:: Source code listings of the diagnostic programs are available. All VAX/DS diagnostic programs are structured in a standard format. For example, the initialization code for every diagnostic program is always located in the same relative area within the listing. To fully understand the source code listings of a VAX/DS diagnostic program, refer to the VAX Diagnostic Design Guide.

The help file for a diagnostic program is shipped with the diagnostic program. The documentation file and source codelistings are available by ordering a [[Maintenance Documentation Service]] Option on microfiche.

== Diagnostic Scopes ==

There are two diagnostic scopes.

* A CPU-specific scope: '''CPU Cluster Testing'''
* A scope for the identical diagnostic programs for all types of VAX computers: '''Peripheral Diagnostics'''

=== CPU Cluster Testing ===

'''NOTE: The term "CPU cluster" used here means all components belonging to a CPU; there is no connection with the term [[VAXcluster|"VAXcluster" (alternatively: "VMScluster")]].'''

The VAX CPU cluster is tested by a set of programs, existing at several program levels, as follows:

* Level 5
** Console tests
** Processor tests
** Memory tests
* Level 4
** VAX instruction set test (hardcore for VDS)
** Cache and translation buffer tests (VAX-11/750 only)
* Level 3
** Memory tests (if no level 5 test possible)
** Channel adapter tests
** Cluster exerciser

'''NOTE: The term "Channel adapter" used here means bus adapter, e.g. for [[UNIBUS]] or [[MASSBUS]].'''

This set of programs implements the VAX diagnostic strategy by providing a set of building blocks by which a system may be tested, starting with the level 5 basic processor tests and ending with the level 3 cluster exerciser, which is a program meant to exercise all components of the cluster.

=== Peripheral Diagnostics ===

Thorough testing of a peripheral device requires the development of three different diagnostic programs. For each device type the following will typically (but not necessarily) exist:

* A level 3 logic test
* A level 3 function test
* A level 2R function test

This group of programs implements the diagnostic strategy by providing a facility for producing very accurate and detailed identifications of fault conditions via the level 3 programs and by also providing a method by which the device may be tested without bringing down the customer's operating system via the level 2R program.

The level 3 logic test will provide the greatest detail of error resolution, indicating which section of logic is failing. This program will be used by technicians to repair bad logic boards, and will provide very high test coverage. Some devices contain ROM-resident microprograms ("self-tests") that perform logic testing, making a level 3 logic test unnecessary.

The level 3 function test will provide a comprehensive test of all of the device’s functions. This program will be used to determine accurately whether or not a device is operating correctly. This is the definitive function test and provides very high test coverage. Level 3 function tests are usually required even if the device possesses self-testing capabilities, because self-tests generally are not capable of complete detection of function failures.

The level 2R program will typically consist of a subset of the level 3 function test. It will test as much of the device’s functionality as can be tested in the user (VMS) environment. The tests it contains are exact or approximate copies of tests existing in the level 3 program.

A typical sequence of use for these programs, when dealing with a system at a customer site, is as follows:

# The customer (or field service) suspects a fault existing in the device.
# The level 2R program is run to see if the error can be detected without stopping the operating system. If the error is found, go to step 4.
# If the level 2R program cannot identify the fault, the operating system is brought down and the level 3 function test is run.
# The fault is identified and the failing [[Field Replacable Unit|FRU]] is replaced. The operating system is then brought back up.
# The failing FRU is brought back to DIGITAL, where the level 3 logic test, the level 3 function test, or perhaps a module test station is used to identify the failing logic on the FRU. The FRU is repaired.

== VAX Diagnostic Coding Convention ==

VAX diagnostic program names consist of 5 letters and a two-digit version number, e.g.: ECKAL-3.4:

* E = VAX
* C = 11/750
* K = CPU
* A = Supervisor
* L = Unique identifier
* 3 = Major revision
* 4 = Minor Revision

See the following 1986 VAX Diagnostic Coding Convention Table for letter breakdown:

EPXYD-R.P

E = System

E = VAX

P = Processor

B = VAX 8200/8300
D = VAX 8600
S = VAX 11780
T = VAX 11785
C = VAX 11750
N = VAX 11730 and 11725
H = MicroVAX I
V = More than one VAX Processor
Z = ?

X = Device Category

A = Application (CR, LP, A-D, Misc.)
C = Channel Adaptors (MBA, UBA)
D = Communication Devices (DMC, DZ11)
G = CI Adapter
K = CPU
L = Database Files
M = Magnetic Tape (TE, TU, DT)
P = Test Equipment
Q = QIO Device Driver
R = Rotating Memory (RP, RK, RM, RS, RX)
S = System Monitor (Supervisor, Tape Monitor)
T = Terminal (LA36, VT52)
U = Utilities (Script file, Copy, Update)
W = Workstations
X = System Exerciser (EXR/BUSINT)
Z = Media Packages
0-9 = Engineering File

Y = Device Type

Category Application
A = Line Printers, LP, LCP01
B = Card Readers, CR
L = LPA11-K
Category Channel
A = MBA
B = UBA, DWBUA
C = MA780
D = IEC11, IEU11-A, DR70
E = DT07
F = DEC DATAWAY
G = CI780
H = CI750/CI780 MICROCODE VERIFICATION (INTERNAL)
I = TEST BED ADAPTERS
J = NBI ADAPTER
K = CIBCI

Category Communications
A = DZ11,DZ32,DMZ32,DHU11,DMB32
B = DMC
C = Multiple Devices
D = DR11-C
E = DV11
F = DR780,DF11-W
G = DQS11
H = KMC11-B
I = KMS11-B
J = DM11-BA
K = DMS11-BA
L = DMF32 Combo
M = DMC11,DMR11,DMP11
N = DN11
O = CPI32
P = PCL11
R = DR11B,DR11-W,DRE11
S = DRS11/DSS
T = KCT32-A,FEPCM
U = DUP11
X = Multiple Devices
W = UNA
Y = DEBNT

Category Database Files
A = CRD DATABASE FILES
B = SYSTEM EXERCISER DATABASE FILES

Category Magnetic Tape
A = TE16/77, TS11, TU78, TS05
B = TU81,TU80

Category QIO Device Drivers
For this category, the fourth and fifth letters of the code are the device mnemonic.
For example, EVQDB is the QIO device driver for the DB, or RP disk series.

Category Test Equipment
A = CI780 Node Tester
B = NI Tester

Category Rotating Memory
A = Multiple devices
B = RP04/5/6
C = DCL/RP04/5/6
D = RM03/RM05/RM80
E = RK611,RK06,RK07
F = RL02
G = RM80
H = RP07
I = RX02
J = ML11
K = IDC
L = UDA50(RA60,RA80,RA81)
M = RC25
N = RUX50

Category System Monitor
A = Supervisor
B = Autosizer
C = DYDDM

Category Terminals
A = All Terminals
B = Terminal exerciser
C = VS11
D = 11C03-LH Fastek
G = VS70

Category Utility
A = Script File
B = Copy Command file
C = Updating file

Category Workstation
A = VS100

Category Exerciser
B = Exerciser Bus Interaction

D = Fifth character makes the code unique. A through Z and 1 through 9.

R = Revision (MAJOR)
P = Revision (MINOR)

== Distribution of Diagnostic Programs ==

Typically, a VAX computer came with all the necessary diagnostic programs on console media at no additional charge, e.g.:

* VAX-11/780: [[RX01/02 floppy drive|RX01 floppies]]
* VAX-11/750, VAX-11/730, and VAX-11/725: [[TU58 DECtape II|TU58 cartridges]]
* VAX 8600: [[RL01/02 disk drive|RL02 disk pack]]
* VAX 8200, VAX 8250, VAX 8300, and VAX 8350: [[RX50 dual-diskette drive|RX50 floppies]]

Additionally, you could buy larger collections of diagnostic programs on [[magnetic tape]] or [[Removable-pack disk|removable disk packs]].

Extended documentation was available on microfiche at an extra charge.

== VMS User Enviroment Test Package (UETP) ==

From the very beginning of VMS V1.0 there was the '''[[User Enviroment Test Package]]''' (UETP), see: [http://bitsavers.trailing-edge.com/pdf/dec/vax/vms/2.0/AA-D643B-TE_VAX-VMS_2.0_UETP_Users_Guide_198003.pdf VAX/VMS UETP User’s Guide AA-D643A-TE]

Quote from the first UETP manual:

"''The UETP is a collection of tests designed to demonstrate that the hardware and software components of a VAX/VMS system are in working order. DIGITAL software support representatives run the UETP on a newly installed VAX/VMS system as the formal sample procedure.''"

UETP is still used in the latest version of VMS (V9.2-2 for x86 as of this writing).

[https://docs.vmssoftware.com/vsi-openvms-system-manager-s-manual-volume-2-tuning-monitoring-and-complex-systems/#_6017UETP| See here] for the latest VMS UETP manual.

== ULTRIX System Exerciser Package ==

[[ULTRIX]] has got a very similar tool to verify proper hardware operation at the operating system level, the '''[[System Exerciser Package]]'''.

For the earliest reference found so far see the manual: [https://drive.google.com/file/d/1i3LoLAvTQC7dZl-T9X3SsQgg_6s_6TCY/view?usp=sharing ULTRIX-32 2.2 System Exercisers 1987 AA-KS95A-TE]

The MIPS variants of ULTRIX include the System Exerciser Package, too.

== Additional Diagnostic Tools ==

* On-board ROM-based diagnostics (RBDs) / Self-tests
* [[Diagnostic and Utility Protocol|DUP]] for [[Mass Storage Control Protocol|MSCP]] devices

== CPU-specific Supervisors ==

* '''EBSAA''' VAX 8200/8250/8300/8350 & VS8000 Diagnostic Supervisor
* '''ECSAA''' VAX-11/750 DIAGNOSTIC SUPERVISOR
* '''EDSAA''' VAX 8600/8650 Diagnostic Supervisor
* '''EHSAA''' MicroVAX I VDS
* '''EJSAA''' VAX 8820/8830/8840 Diagnostic Supervisor
* '''ELSAA''' VAX 6210/6220/6230/6240/6310/6320/6330/6340/6350/6360 Diagnostic Supervisor
* '''ENSAA''' VAX 725/730 Diagnostic Supervisor
* '''ESSAA''' VAX 780/785 Diagnostic Supervisor
* '''EXSAA''' ???
* '''EZSAA''' VAX 8530/8550/8700/8800/8820N Diagnostic Supervisor
* '''E?SAA''' VAX9000 Diagnostic Supervisor

There is no supervisor for the series of VAX 7000 / VAX 10000 computers (see: [http://www.vaxhaven.com/images/4/4d/EK-7001A-TS-001.pdf VAX 7000 Advanced Troubleshooting EK-7001A-TS-001])

== Set of Diagnostics for a SV-BXTAA VAX-11/750 System ==

A SV-BXTAA VAX-11/750 System consists of:

* [[KA750 CPU|VAX-11/750 CPU]]
* [[MS750 Memory System|MS750 1MB memory]]
* [[DECwriter IV|LA38 printing console terminal]]
* [[RH750 Massbus Adapter]]
* [[RM02/03 disk drive|RM03 MASSBUS disk drive subsystem]]
* [[DZ11 asynchronous serial line interface|DZ11 terminal adapter]]
* [[TS11 Subsystem|TS11 magnetic tape unit]]

The diagnostics set for this system is made of:

* CPU-specific diagnostic main program
** '''ECSAA''' VAX 11750 DIAG SUPERVISOR

* VAX-common automatic sizing program which automatically determines the current system configuration
** '''EVSBA''' VAX AUTOSIZER DIAGNOSTIC

* Set of VAX-11/750 CPU diagnostics
** '''ECKAA''' VAX 11750 UDIAG MON
** '''ECKAB''' VAX 11750 MICRO DPM
** '''ECKAC''' VAX 11750 MICRO MIC
** '''ECKAD''' VAX FP750 MICRODIAG
** '''ECKAF''' VAX KC750 UDIAG
** '''ECKAL''' VAX 11750 CACHE/TB DIAG
** '''ECKAM''' VAX 11750 MEMORY DIAG
** '''ECKAX''' VAX 11750 CLUSTER EXER

* VAX-common instruction set diagnostic
** '''EVKAA''' VAX INSTRUCTION SET TEST

* VAX-11/750 bus diagnostics
** '''ECCAA''' VAX 11750 RH750 DIAG
** '''ECCBA''' VAX 11750 UBI/DW750 DIAG

* Set of VAX-common peripheral diagnostics
** '''EVTAA''' VAX TERMINAL DIAGNOSTIC
** '''EVTBA''' VAX TERMINAL EXERCISER
** '''EVDAA''' VAX DZ11 8 LINE ASYNC MUX
** '''EVMAA''' VAX TM03/TE16/TU45-77 Tape
** '''EVRDA''' VAX RM03/RM05/RM80 DISKLESS
** '''EVRDB''' VAX RM03/RM05 FUNCTIONAL TEST

== Booting the VAX Diagnostic Supervisor ==

The command to boot the VAX Diagnostic Supervisor on a SIMH VAX is:

BOOT RQ0 /R5:10

* <code>RQ0</code> is the device identifier for the MSCP disk, unit 0, where the diagnostics are stored; adjust this according to your requirements.
* <code>/R5:10</code> is the boot flag to boot the Diagnostic Supervisor located in directory <code>DUA0:[SYSMAINT]</code> or <code>DUA0:[SYS0.SYSMAINT]</code>.

For booting the VAX Diagnostic Supervisor on a real VAX refer chapter 2.1 of the "'''VAX DS Diagnostic Supervisor User's Guide'''" [[#ref_1|[1]]]

== Sample run of the VDS EVSBA AUTOSIZER ==

DS> '''LOAD EVSBA.EXE'''
DS> '''SET FLAGS QUICK'''
DS> '''START /SECTION:MANUAL'''

.. Program: EVSBA - AUTOSIZER LEVEL 3, revision 5.1, 3 tests,
at 18:18:28.19.

COMMAND? '''HELP'''

HELP

This is a manual section command. This program creates ATTACH
commands for all devices in the system.
(ATTACH,CHANGE,EXIT,HELP,LIST,READ,SIZE,WRITE) - These commands
control the sizer in manual and selftest mode.
To obtain further information type HELP followed by a topic.
For example;
HELP MANUAL

Additional information available:

ATTACH CHANGE DEFAULT DEVICE EVENT
EXIT HELP LIST MANUAL QUICK
READ SECTION SELFTEST SCRIPT SIZE
SUMMARY WRITE

COMMAND? '''SIZE'''
COMMAND? '''LIST'''
FILE IN MEMORY 'CONFIG.COM'
!! AUTOMATIC SIZING PROGRAM.
!! THIS IS A TOOL AND NOT A DIAGNOSTIC PROGRAM.
!! CONFIGURATION FILE FOR SYSTEM.
!! COMPUTER GENERATED CPU TYPE 2 MICROCODE REV LEVEL = 99
!! NUMERIC VALUES WITH A LEADING ZERO ARE ASSIGNED.
!! FILE VALID ONLY FOR STANDARD HARDWARE CONFIGURATION.
!! TIME IS 15-FEB-1984 18:18:56.85
!!
!! *** QUICK FLAG SET. NO CHECKS MADE FOR TERMINALS ON DZ11/DZ32'S ***
!!
!!
!! DEFINE PROCESSOR...
!!
DS> ATTACH KA750 HUB KA0 YES YES YES 027FF 0
!!
!! DEFINE MEMORY...
!!
DS> ATTACH MS750 MS0
!!
!! DEFINE UNIBUS ADAPTERS...
!!
DS> ATTACH DW750 HUB DW0
!!
DS> ATTACH LP11 DW0 LPA 777514 0200 04
DS> ATTACH LP25 LPA LPA0 !! *** PRINTER TYPE IS ESTIMATED ***
DS> ATTACH TS11 DW0 MSA0 772520 0224 05
DS> ATTACH UDA50 DW0 DUA 772150 0154 05 02
DS> ATTACH RA81 DUA DUA0
DS> ATTACH RA60 DUA DJA2
DS> ATTACH RX50 DUA DUA3
DS> ATTACH DZ11 DW0 TTA 760100 0300 05 EIA
DS> ATTACH DZ11 DW0 TTB 760110 0310 05 EIA
DS> ATTACH DZ11 DW0 TTC 760120 0320 05 EIA
DS> ATTACH DZ11 DW0 TTD 760130 0330 05 EIA
COMMAND? '''WRITE'''
CONFIGURATION FILE IS NORMALLY READ/WRITTEN TO THE SUPERVISOR CONSOLE MEDIA
VERIFY SUPERVISOR CONSOLE MEDIA LOADED.
VERIFIED? [(Yes), No] '''YES'''
COMMAND? '''EXIT'''
DS>

== See also ==

* [[Running VDS Diagnostics on the SIMH VAX-11/750]]

== External links ==

This page contains condensed information from several DEC manuals, among others:

* [http://bitsavers.org/pdf/dec/vax/diag/EP-EVNDX-25.0_Oct86.txt EVNDX25 VAX DIAGNOSTIC INDEX]
* [https://vt100.net/mirror/hcps/si75fin1.pdf EK-SI75F-IN-001 VAX-11-750 Installation Manual] pdf-page 60ff
* <div id="ref_1">[1] [http://bitsavers.org/pdf/dec/vax/diag/VAX_Diagnostic_Supervisor_Users_Guide_Apr89.pdf AA-FK66A-TE VAX DS Diagnostic Supervisor User's Guide] </div>
* [http://bitsavers.org/pdf/dec/vax/diag/EK-1VAXD-TM-001_VAX_Diagnostic_Design_Guide_Aug79.pdf EK-1VAXD-TM-003 VAX Diagnostic Design Guide]
* [http://bitsavers.org/pdf/dec/vax/diag/AA-FK67A-TE_VAX_Diagnostic_Design_Guide_Apr89.pdf AA-FK67A-TE VAX Diagnostic Design Guide]
* [http://www.bitsavers.org/pdf/dec/vax/vms/1.5/2b/AA-D643A-TE_VAX_VMS_UETP_Users_Guide_Aug78.pdf AA-D643A-TE VAX/VMS UETP User’s Guide]
* [http://www.trailing-edge.com/~shoppa/11780diags/ VAX-11/780 Diagnostic Help Files]
* [https://manx-docs.org/collections/antonio/dec/MDS-2000-01/cd1/VAX/7001ATS1.PDF EK-7001A-TS-001 VAX 7000 Advanced Troubleshooting]

[[Category: VAX]]
[[Category: VAX Software]]
[[Category: VAX Diagnostic Software]]
[[Category: SIMH Tutorials]]
[[Category: VMS Practical Guides]]

VAX Diagnostic Supervisor

2025-11-11T11:00:37Z

Vaxorcist: /* VAX Diagnostic Coding Convention */ MicroVAX I added

VDS - '''VAX Diagnostic Supervisor''' (sometimes abbreviated to VAX/DS) is a set of diagnostic software programs for the [[DEC]] [[VAX]] computers and peripheral devices.

== Intro ==

'''''"At best, a computer is as good as its diagnostic tools!"'''''

That's what they must have thought at DEC when they developed their diagnostic software.

Here we will take a closer look at the VAX Diagnostic Supervisor and also a quick side look at the [[User Environment Test Package]] (UETP).

== Using VDS for simulated VAX Computers ==

You may ask: "What are the VAX diagnostics good for when run on a simulated VAX?"

Yes, many diagnostics do not run on a simulated VAX, but some work very well and are used e.g. for testing the various [[SIMH]] VAX simulators for correct execution of the VAX native mode instructions.

Furthermore you can explore how precise the simulation mimics the real hardware.

If you plan to test your real VAX, you can familiarize yourself with VDS and prepare your diagnosis in SIMH, and SIMH can assist you in preparing and creating a diagnostic kit on media appropriate for your VAX.

Automated testing script for a SIMH VAX-11/750:

SET CLOCK NOCALIBRATE=600K
ATTACH -RQ RQ0 VAX_MINIMUM_DIAGS.dsk
EXPECT "DS> " SEND "ATTACH UDA50 DW0 DUA 772150 154 5 10\r"; GO -Q
EXPECT "DS> " SEND "ATTACH RA81 DUA DUA0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH KA750 CMI KA0 yes yes yes 0 0\r"; GO -Q
EXPECT "DS> " SEND "ATTACH DW750 CMI DW0 8\r"; GO -Q
EXPECT "DS> " SEND "SET LOAD DUA0:[SYSMAINT]\r"; GO -Q
EXPECT "DS> " SEND "SELECT KA0\r"; GO -Q
EXPECT "DS> " SEND "SET FLAGS TRACE\r"; GO -Q
EXPECT "DS> " SEND "RUN EVKAB\r"; GO -Q
BOOT -Q RQ0 /R5:10

== VDS History ==

VDS development began in parallel that to the first [[VAX]] model, the [[VAX-11/780]] in 1977.

VDS was provided soley for the '''''"big VAXen"''''' (i.e. not for the [[MicroVAX]] and [[VAXstation]] computers), with one remarkable exception, the [[MicroVAX I]], resp. [[VAXstation I]].
Each new VAX model received its CPU-specific VDS modules up to the [[VAX 9000]]; only the VAX models of the last two series, [[VAX 7000]] and [[VAX 10000]], were covered by other diagnostic methods.

== Program Levels ==

All VAX diagnostic programs are assigned to a '''level'''. Levels are numbered 1, 2R, 2, 3, 4, and 5. A program’s level indicates its run-time environment.

* '''Level 1''' diagnostic programs run under an operating system. They do not use the VAX/DS. (=> UETP)
* '''Level 2R''' diagnostic programs run under VAX/DS in user mode only.
* '''Level 2''' diagnostic programs run in both user mode and standalone mode, under the control of the VAX/DS.
* '''Level 3''' diagnostic programs run only in standalone mode, under the control of the VAX/DS.
* '''Level 4''' diagnostic programs run in standalone without VAX/DS.
* '''level 5''' diagnostic programs run in [[Writable Control Store|WCS]] or system console, not in VAX main memory. They do not use the VAX/DS.

Only the levels 2R, 2, and 3 are managed by VDS.

== Sections, Tests, Subtests, and Flags ==

All diagnostic programs that run under the VAX/DS are composed of one or more '''sections'''. Each section has a name, and it is possible to specify, by name, which section of the program to execute. A program section can have one of two functions, depending on its design:

* Test a certain major portion of the unit under test.
* Facilitate a certain mode of testing. For example, there might be a quick-verify section, used to give the device a quick (but not thorough) test.

In order to determine the number and names of the sections in a particular diagnostic program, use the <code>SHOW SECTIONS</code> command. However, every program contains a default section called <code>DEFAULT</code>, which will execute automatically if you do not specifically select a section. A section is selected with the <code>/SECTION</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Each section is composed of a set of '''tests'''; each test verifies either a particular function of the hardware or a particular subset of the component logic being tested. The VAX/DS allows you to specify which tests within a section to run. Each test may have some '''subtests'''. Tests are selected with the <code>/TEST</code> qualifier on the <code>RUN</code> or <code>START</code> command.

Two sets of '''flags''' are provided to control certain aspects of a diagnostic program’s execution. These flags may be set or cleared before the diagnostic program is started.

One set of flags is called the '''VAX/DS control flags'''. The flags in this set are interpreted by the VAX/DS and their meanings are the same in all diagnostic programs. The VAX/DS control flags are set with the <code>SET FLAGS</code> command.

The other set of flags is referred to as the '''event flags'''. This set consists of 23 flags whose purposes are defined by the diagnostic programs. The user must read the documentation for specific diagnostic programs to determine if a definition has been assigned to any of the event flags. <code>SET EVENT FLAGS</code> command.

== Some useful VDS commands ==

* <code>'''LOAD''' Exxxx</code> Load diagnostic Exxxx (where "Exxxx" is replaced by the diagnostics name, e.g. EVKAA)
* <code>'''SHOW FLAGS'''</code> Show VDS flags
* <code>'''SHOW TESTS'''</code> Show the available tests of the loaded diagnostic
* <code>'''SHOW SECTIONS'''</code> Show the available sections of the loaded diagnostic
* <code>'''START/TEST='''first:last</code> Start a subset of the loaded diagnostics tests (where "first" is the test number to start with, and -optionally- "last" is the last one to execute)
* <code>'''START/SECTION='''section-name</code> Start a single section of the loaded diagnostic (where "section-name" is the name of the section to run)
* <code>'''START/PASSES='''count</code> Start the loaded diagnostic for "count" passes (where "count" is the number of passes to execute)
* <code>'''RUN''' exxxx'''/TEST='''first:last</code> Run a subset of the diagnostics tests
* <code>'''RUN''' exxxx'''/SECTION='''section-name</code> Run a single section of the diagnostic
* <code>'''RUN''' exxxx'''/PASSES='''count</code> Run the diagnostic for "count" passes

Use a pass count of 0 to run a program continuously. If you do this, the program will run until you type CTRL/C or a failure occurs with the HALT flag set.

== Diagnostic Program Documentation ==

Documentation provided for each diagnostic program includes:

* '''Help file'''
:: The help file is referenced with the HELP command. It contains any operating instructions that may be unique to the diagnostic program. The help file for diagnostic program EVXYZ is EVXYZ.HLP; the help file for the VAX/DS is EVSAA.HLP

* '''Documentation file'''
:: The documentation file provides a detailed description of a diagnostic program's function, run-time requirements, operating instructions, fault detection, and maintenance history, plus explanations of each test’s function and execution flow. The documentation file for diagnostic program EVXYZ is EVXYZ.DOC.

* '''Source Code listings'''
:: Source code listings of the diagnostic programs are available. All VAX/DS diagnostic programs are structured in a standard format. For example, the initialization code for every diagnostic program is always located in the same relative area within the listing. To fully understand the source code listings of a VAX/DS diagnostic program, refer to the VAX Diagnostic Design Guide.

The help file for a diagnostic program is shipped with the diagnostic program. The documentation file and source codelistings are available by ordering a [[Maintenance Documentation Service]] Option on microfiche.

== Diagnostic Scopes ==

There are two diagnostic scopes.

* A CPU-specific scope: '''CPU Cluster Testing'''
* A scope for the identical diagnostic programs for all types of VAX computers: '''Peripheral Diagnostics'''

=== CPU Cluster Testing ===

'''NOTE: The term "CPU cluster" used here means all components belonging to a CPU; there is no connection with the term [[VAXcluster|"VAXcluster" (alternatively: "VMScluster")]].'''

The VAX CPU cluster is tested by a set of programs, existing at several program levels, as follows:

* Level 5
** Console tests
** Processor tests
** Memory tests
* Level 4
** VAX instruction set test (hardcore for VDS)
** Cache and translation buffer tests (VAX-11/750 only)
* Level 3
** Memory tests (if no level 5 test possible)
** Channel adapter tests
** Cluster exerciser

'''NOTE: The term "Channel adapter" used here means bus adapter, e.g. for [[UNIBUS]] or [[MASSBUS]].'''

This set of programs implements the VAX diagnostic strategy by providing a set of building blocks by which a system may be tested, starting with the level 5 basic processor tests and ending with the level 3 cluster exerciser, which is a program meant to exercise all components of the cluster.

=== Peripheral Diagnostics ===

Thorough testing of a peripheral device requires the development of three different diagnostic programs. For each device type the following will typically (but not necessarily) exist:

* A level 3 logic test
* A level 3 function test
* A level 2R function test

This group of programs implements the diagnostic strategy by providing a facility for producing very accurate and detailed identifications of fault conditions via the level 3 programs and by also providing a method by which the device may be tested without bringing down the customer's operating system via the level 2R program.

The level 3 logic test will provide the greatest detail of error resolution, indicating which section of logic is failing. This program will be used by technicians to repair bad logic boards, and will provide very high test coverage. Some devices contain ROM-resident microprograms ("self-tests") that perform logic testing, making a level 3 logic test unnecessary.

The level 3 function test will provide a comprehensive test of all of the device’s functions. This program will be used to determine accurately whether or not a device is operating correctly. This is the definitive function test and provides very high test coverage. Level 3 function tests are usually required even if the device possesses self-testing capabilities, because self-tests generally are not capable of complete detection of function failures.

The level 2R program will typically consist of a subset of the level 3 function test. It will test as much of the device’s functionality as can be tested in the user (VMS) environment. The tests it contains are exact or approximate copies of tests existing in the level 3 program.

A typical sequence of use for these programs, when dealing with a system at a customer site, is as follows:

# The customer (or field service) suspects a fault existing in the device.
# The level 2R program is run to see if the error can be detected without stopping the operating system. If the error is found, go to step 4.
# If the level 2R program cannot identify the fault, the operating system is brought down and the level 3 function test is run.
# The fault is identified and the failing [[Field Replacable Unit|FRU]] is replaced. The operating system is then brought back up.
# The failing FRU is brought back to DIGITAL, where the level 3 logic test, the level 3 function test, or perhaps a module test station is used to identify the failing logic on the FRU. The FRU is repaired.

== VAX Diagnostic Coding Convention ==

VAX diagnostic program names consist of 5 letters and a two-digit version number, e.g.: ECKAL-3.4:

* E = VAX
* C = 11/750
* K = CPU
* A = Supervisor
* L = Unique identifier
* 3 = Major revision
* 4 = Minor Revision

See the following 1986 VAX Diagnostic Coding Convention Table for letter breakdown:

EPXYD-R.P

E = System

E = VAX

P = Processor

B = VAX 8200/8300
D = VAX 8600
S = VAX 11780
T = VAX 11785
C = VAX 11750
N = VAX 11730 and 11725
H = MicroVAX I
V = More than one VAX Processor

X = Device Category

A = Application (CR, LP, A-D, Misc.)
C = Channel Adaptors (MBA, UBA)
D = Communication Devices (DMC, DZ11)
G = CI Adapter
K = CPU
L = Database Files
M = Magnetic Tape (TE, TU, DT)
P = Test Equipment
Q = QIO Device Driver
R = Rotating Memory (RP, RK, RM, RS, RX)
S = System Monitor (Supervisor, Tape Monitor)
T = Terminal (LA36, VT52)
U = Utilities (Script file, Copy, Update)
W = Workstations
X = System Exerciser (EXR/BUSINT)
Z = Media Packages
0-9 = Engineering File

Y = Device Type

Category Application
A = Line Printers, LP, LCP01
B = Card Readers, CR
L = LPA11-K
Category Channel
A = MBA
B = UBA, DWBUA
C = MA780
D = IEC11, IEU11-A, DR70
E = DT07
F = DEC DATAWAY
G = CI780
H = CI750/CI780 MICROCODE VERIFICATION (INTERNAL)
I = TEST BED ADAPTERS
J = NBI ADAPTER
K = CIBCI

Category Communications
A = DZ11,DZ32,DMZ32,DHU11,DMB32
B = DMC
C = Multiple Devices
D = DR11-C
E = DV11
F = DR780,DF11-W
G = DQS11
H = KMC11-B
I = KMS11-B
J = DM11-BA
K = DMS11-BA
L = DMF32 Combo
M = DMC11,DMR11,DMP11
N = DN11
O = CPI32
P = PCL11
R = DR11B,DR11-W,DRE11
S = DRS11/DSS
T = KCT32-A,FEPCM
U = DUP11
X = Multiple Devices
W = UNA
Y = DEBNT

Category Database Files
A = CRD DATABASE FILES
B = SYSTEM EXERCISER DATABASE FILES

Category Magnetic Tape
A = TE16/77, TS11, TU78, TS05
B = TU81,TU80

Category QIO Device Drivers
For this category, the fourth and fifth letters of the code are the device mnemonic.
For example, EVQDB is the QIO device driver for the DB, or RP disk series.

Category Test Equipment
A = CI780 Node Tester
B = NI Tester

Category Rotating Memory
A = Multiple devices
B = RP04/5/6
C = DCL/RP04/5/6
D = RM03/RM05/RM80
E = RK611,RK06,RK07
F = RL02
G = RM80
H = RP07
I = RX02
J = ML11
K = IDC
L = UDA50(RA60,RA80,RA81)
M = RC25
N = RUX50

Category System Monitor
A = Supervisor
B = Autosizer
C = DYDDM

Category Terminals
A = All Terminals
B = Terminal exerciser
C = VS11
D = 11C03-LH Fastek
G = VS70

Category Utility
A = Script File
B = Copy Command file
C = Updating file

Category Workstation
A = VS100

Category Exerciser
B = Exerciser Bus Interaction

D = Fifth character makes the code unique. A through Z and 1 through 9.

R = Revision (MAJOR)
P = Revision (MINOR)

== Distribution of Diagnostic Programs ==

Typically, a VAX computer came with all the necessary diagnostic programs on console media at no additional charge, e.g.:

* VAX-11/780: [[RX01/02 floppy drive|RX01 floppies]]
* VAX-11/750, VAX-11/730, and VAX-11/725: [[TU58 DECtape II|TU58 cartridges]]
* VAX 8600: [[RL01/02 disk drive|RL02 disk pack]]
* VAX 8200, VAX 8250, VAX 8300, and VAX 8350: [[RX50 dual-diskette drive|RX50 floppies]]

Additionally, you could buy larger collections of diagnostic programs on [[magnetic tape]] or [[Removable-pack disk|removable disk packs]].

Extended documentation was available on microfiche at an extra charge.

== VMS User Enviroment Test Package (UETP) ==

From the very beginning of VMS V1.0 there was the '''[[User Enviroment Test Package]]''' (UETP), see: [http://bitsavers.trailing-edge.com/pdf/dec/vax/vms/2.0/AA-D643B-TE_VAX-VMS_2.0_UETP_Users_Guide_198003.pdf VAX/VMS UETP User’s Guide AA-D643A-TE]

Quote from the first UETP manual:

"''The UETP is a collection of tests designed to demonstrate that the hardware and software components of a VAX/VMS system are in working order. DIGITAL software support representatives run the UETP on a newly installed VAX/VMS system as the formal sample procedure.''"

UETP is still used in the latest version of VMS (V9.2-2 for x86 as of this writing).

[https://docs.vmssoftware.com/vsi-openvms-system-manager-s-manual-volume-2-tuning-monitoring-and-complex-systems/#_6017UETP| See here] for the latest VMS UETP manual.

== ULTRIX System Exerciser Package ==

[[ULTRIX]] has got a very similar tool to verify proper hardware operation at the operating system level, the '''[[System Exerciser Package]]'''.

For the earliest reference found so far see the manual: [https://drive.google.com/file/d/1i3LoLAvTQC7dZl-T9X3SsQgg_6s_6TCY/view?usp=sharing ULTRIX-32 2.2 System Exercisers 1987 AA-KS95A-TE]

The MIPS variants of ULTRIX include the System Exerciser Package, too.

== Additional Diagnostic Tools ==

* On-board ROM-based diagnostics (RBDs) / Self-tests
* [[Diagnostic and Utility Protocol|DUP]] for [[Mass Storage Control Protocol|MSCP]] devices

== CPU-specific Supervisors ==

* '''EBSAA''' VAX 8200/8250/8300/8350 & VS8000 Diagnostic Supervisor
* '''ECSAA''' VAX-11/750 DIAGNOSTIC SUPERVISOR
* '''EDSAA''' VAX 8600/8650 Diagnostic Supervisor
* '''EHSAA''' MicroVAX I VDS
* '''EJSAA''' VAX 8820/8830/8840 Diagnostic Supervisor
* '''ELSAA''' VAX 6210/6220/6230/6240/6310/6320/6330/6340/6350/6360 Diagnostic Supervisor
* '''ENSAA''' VAX 725/730 Diagnostic Supervisor
* '''ESSAA''' VAX 780/785 Diagnostic Supervisor
* '''EXSAA''' ???
* '''EZSAA''' VAX 8530/8550/8700/8800/8820N Diagnostic Supervisor
* '''E?SAA''' VAX9000 Diagnostic Supervisor

There is no supervisor for the series of VAX 7000 / VAX 10000 computers (see: [http://www.vaxhaven.com/images/4/4d/EK-7001A-TS-001.pdf VAX 7000 Advanced Troubleshooting EK-7001A-TS-001])

== Set of Diagnostics for a SV-BXTAA VAX-11/750 System ==

A SV-BXTAA VAX-11/750 System consists of:

* [[KA750 CPU|VAX-11/750 CPU]]
* [[MS750 Memory System|MS750 1MB memory]]
* [[DECwriter IV|LA38 printing console terminal]]
* [[RH750 Massbus Adapter]]
* [[RM02/03 disk drive|RM03 MASSBUS disk drive subsystem]]
* [[DZ11 asynchronous serial line interface|DZ11 terminal adapter]]
* [[TS11 Subsystem|TS11 magnetic tape unit]]

The diagnostics set for this system is made of:

* CPU-specific diagnostic main program
** '''ECSAA''' VAX 11750 DIAG SUPERVISOR

* VAX-common automatic sizing program which automatically determines the current system configuration
** '''EVSBA''' VAX AUTOSIZER DIAGNOSTIC

* Set of VAX-11/750 CPU diagnostics
** '''ECKAA''' VAX 11750 UDIAG MON
** '''ECKAB''' VAX 11750 MICRO DPM
** '''ECKAC''' VAX 11750 MICRO MIC
** '''ECKAD''' VAX FP750 MICRODIAG
** '''ECKAF''' VAX KC750 UDIAG
** '''ECKAL''' VAX 11750 CACHE/TB DIAG
** '''ECKAM''' VAX 11750 MEMORY DIAG
** '''ECKAX''' VAX 11750 CLUSTER EXER

* VAX-common instruction set diagnostic
** '''EVKAA''' VAX INSTRUCTION SET TEST

* VAX-11/750 bus diagnostics
** '''ECCAA''' VAX 11750 RH750 DIAG
** '''ECCBA''' VAX 11750 UBI/DW750 DIAG

* Set of VAX-common peripheral diagnostics
** '''EVTAA''' VAX TERMINAL DIAGNOSTIC
** '''EVTBA''' VAX TERMINAL EXERCISER
** '''EVDAA''' VAX DZ11 8 LINE ASYNC MUX
** '''EVMAA''' VAX TM03/TE16/TU45-77 Tape
** '''EVRDA''' VAX RM03/RM05/RM80 DISKLESS
** '''EVRDB''' VAX RM03/RM05 FUNCTIONAL TEST

== Booting the VAX Diagnostic Supervisor ==

The command to boot the VAX Diagnostic Supervisor on a SIMH VAX is:

BOOT RQ0 /R5:10

* <code>RQ0</code> is the device identifier for the MSCP disk, unit 0, where the diagnostics are stored; adjust this according to your requirements.
* <code>/R5:10</code> is the boot flag to boot the Diagnostic Supervisor located in directory <code>DUA0:[SYSMAINT]</code> or <code>DUA0:[SYS0.SYSMAINT]</code>.

For booting the VAX Diagnostic Supervisor on a real VAX refer chapter 2.1 of the "'''VAX DS Diagnostic Supervisor User's Guide'''" [[#ref_1|[1]]]

== Sample run of the VDS EVSBA AUTOSIZER ==

DS> '''LOAD EVSBA.EXE'''
DS> '''SET FLAGS QUICK'''
DS> '''START /SECTION:MANUAL'''

.. Program: EVSBA - AUTOSIZER LEVEL 3, revision 5.1, 3 tests,
at 18:18:28.19.

COMMAND? '''HELP'''

HELP

This is a manual section command. This program creates ATTACH
commands for all devices in the system.
(ATTACH,CHANGE,EXIT,HELP,LIST,READ,SIZE,WRITE) - These commands
control the sizer in manual and selftest mode.
To obtain further information type HELP followed by a topic.
For example;
HELP MANUAL

Additional information available:

ATTACH CHANGE DEFAULT DEVICE EVENT
EXIT HELP LIST MANUAL QUICK
READ SECTION SELFTEST SCRIPT SIZE
SUMMARY WRITE

COMMAND? '''SIZE'''
COMMAND? '''LIST'''
FILE IN MEMORY 'CONFIG.COM'
!! AUTOMATIC SIZING PROGRAM.
!! THIS IS A TOOL AND NOT A DIAGNOSTIC PROGRAM.
!! CONFIGURATION FILE FOR SYSTEM.
!! COMPUTER GENERATED CPU TYPE 2 MICROCODE REV LEVEL = 99
!! NUMERIC VALUES WITH A LEADING ZERO ARE ASSIGNED.
!! FILE VALID ONLY FOR STANDARD HARDWARE CONFIGURATION.
!! TIME IS 15-FEB-1984 18:18:56.85
!!
!! *** QUICK FLAG SET. NO CHECKS MADE FOR TERMINALS ON DZ11/DZ32'S ***
!!
!!
!! DEFINE PROCESSOR...
!!
DS> ATTACH KA750 HUB KA0 YES YES YES 027FF 0
!!
!! DEFINE MEMORY...
!!
DS> ATTACH MS750 MS0
!!
!! DEFINE UNIBUS ADAPTERS...
!!
DS> ATTACH DW750 HUB DW0
!!
DS> ATTACH LP11 DW0 LPA 777514 0200 04
DS> ATTACH LP25 LPA LPA0 !! *** PRINTER TYPE IS ESTIMATED ***
DS> ATTACH TS11 DW0 MSA0 772520 0224 05
DS> ATTACH UDA50 DW0 DUA 772150 0154 05 02
DS> ATTACH RA81 DUA DUA0
DS> ATTACH RA60 DUA DJA2
DS> ATTACH RX50 DUA DUA3
DS> ATTACH DZ11 DW0 TTA 760100 0300 05 EIA
DS> ATTACH DZ11 DW0 TTB 760110 0310 05 EIA
DS> ATTACH DZ11 DW0 TTC 760120 0320 05 EIA
DS> ATTACH DZ11 DW0 TTD 760130 0330 05 EIA
COMMAND? '''WRITE'''
CONFIGURATION FILE IS NORMALLY READ/WRITTEN TO THE SUPERVISOR CONSOLE MEDIA
VERIFY SUPERVISOR CONSOLE MEDIA LOADED.
VERIFIED? [(Yes), No] '''YES'''
COMMAND? '''EXIT'''
DS>

== See also ==

* [[Running VDS Diagnostics on the SIMH VAX-11/750]]

== External links ==

This page contains condensed information from several DEC manuals, among others:

* [http://bitsavers.org/pdf/dec/vax/diag/EP-EVNDX-25.0_Oct86.txt EVNDX25 VAX DIAGNOSTIC INDEX]
* [https://vt100.net/mirror/hcps/si75fin1.pdf EK-SI75F-IN-001 VAX-11-750 Installation Manual] pdf-page 60ff
* <div id="ref_1">[1] [http://bitsavers.org/pdf/dec/vax/diag/VAX_Diagnostic_Supervisor_Users_Guide_Apr89.pdf AA-FK66A-TE VAX DS Diagnostic Supervisor User's Guide] </div>
* [http://bitsavers.org/pdf/dec/vax/diag/EK-1VAXD-TM-001_VAX_Diagnostic_Design_Guide_Aug79.pdf EK-1VAXD-TM-003 VAX Diagnostic Design Guide]
* [http://bitsavers.org/pdf/dec/vax/diag/AA-FK67A-TE_VAX_Diagnostic_Design_Guide_Apr89.pdf AA-FK67A-TE VAX Diagnostic Design Guide]
* [http://www.bitsavers.org/pdf/dec/vax/vms/1.5/2b/AA-D643A-TE_VAX_VMS_UETP_Users_Guide_Aug78.pdf AA-D643A-TE VAX/VMS UETP User’s Guide]
* [http://www.trailing-edge.com/~shoppa/11780diags/ VAX-11/780 Diagnostic Help Files]
* [https://manx-docs.org/collections/antonio/dec/MDS-2000-01/cd1/VAX/7001ATS1.PDF EK-7001A-TS-001 VAX 7000 Advanced Troubleshooting]

[[Category: VAX]]
[[Category: VAX Software]]
[[Category: VAX Diagnostic Software]]
[[Category: SIMH Tutorials]]
[[Category: VMS Practical Guides]]

Low-Level Formatting DEC MFM Disks

2025-11-09T19:06:07Z

Vaxorcist: Changed the introductory sentence wording.

There are several situations in which you may want (or even need) to format a [[DEC]] [[MFM]] disk:

* Testing for bad blocks
* Reformatting from a PC-like low-level format
* Reformatting for use on another type of [[RQDX Series of MFM Disk & Floppy QBUS Controllers|RQDX]] MFM controller
* Reformatting for spoofing another disk model
* ...

Another scenario might be that you want to prepare a foreign MFM disk model as a replacement for a DEC MFM disk.

You can even reformat [[RLL]]-type disks for usage on MFM controllers for the price of loosing some disk space.

== Preparations ==

All you need is:

* A [[MicroVAX 2000]] / [[VAXstation 2000]]

or:

* An [[RQDX1/RQDX2 MFM Disk & Floppy QBUS Controllers|RQDX1, RQDX2]], or [[RQDX3 MFM Disk & Floppy QBUS Controller|RQDX3]] [[QBUS]] MFM controller suitable for your MFM disk, and
* An [[RX50]] Dual Floppy Drive, and
* A [[MicroPDP-11]], or
* A [[MicroVAX I]] / [[VAXstation I]], or
* A [[MicroVAX II]] / [[VAXstation II]], or
* A later [[QBUS]] based [[MicroVAX]] / [[VAXstation]]

== Using a VAXstation 2000 or MicroVAX 2000 and its ROM resident Diagnostics ==

=== Formatting a Known Hard Disk ===

Example of formatting an [[RD32]] hard disk.

Enter the following commands at your MicroVAX 2000 / VAXstation 2000 console prompt:

>>> '''TEST 70'''

VSfmt_QUE_unitno (0-2) ? '''0''' [enter the drive number of the hard disk]

VSfmt_STS_Siz........... '''RD32''' [formatter recognized DUA0 as a RD32]

VSfmt_QUE_SerNbr (0-999999999) '''29042836''' [enter the serial number for the drive]
[or enter a unique number for each unit]

VSfmt_QUE_RUsure (DUAx 1/0) ? '''1''' [where x equals the unit number]
[enter 1 for YES, 0 for NO]

VSfmt_STS_RdMbb.............OK [manufacturer's bad block located]

VSfmt_STS_FMTing............OK [disk formatted OK]

VSfmt_STS_ChkPss............OK [check pass completed OK]

VSfmt_STS_BBRvec := x [x = number of bad blocks revectored]

VSfmt_RES_Succ [disk is successfully formatted]

>>>

=== Formatting an Unknown Hard Disk ===

>>> '''TEST 70'''

VSfmt_QUE_unitno (0-2) ? '''0''' [Enter drive number]

VSfmt_STS_Siz .......... ???? [Formatter does not recognize drive type]

VSfmt_STS_EntUIB [Formatter wants drive details]

[this example is from the VS2000 technical manual]

xbnsiz :=54 [enter the number of transfer blocks]

dbnsiz :=48 [enter the number of diagnostic blocks]

lbnsiz :=83236 [enter the number of logical blocks]

rbnsiz :=200 [enter the number of replacement blocks]

surpun :=6 [enter the number of surfaces per unit]

cylpun :=820 [enter the number of cylinders per unit]

wrtprc :=820 [enter the write precompensation cylinder]

rctsiz :=4 [enter the size of the revectoring control table (RCT)]

rctnbr :=8 [enter the number of copies of the RCT]

secitl :=1 [enter the sector interleave]

stsskw :=2 [enter the surface to surface skew]

ctcskw :=9 [enter the cylinder to cylinder skew]

mediai :=627327008 [enter the MSCP media ID]

* Note this number is not dependent on disk geometry, but is the magic number for VMS to report on the type of disk. *
At this point, the formatter exits the query mode.

The next output to the screen is:
VSfmt_QUE_SerNbr (0-999999999) [enter the serial number for the drive]
[or enter a unique number for each unit]

VSfmt_QUE_RUsure (DUAx 1/0) ? [where x equals the unit number]
[enter 1 for YES, 0 for NO]

The formatter is now running, and the output should look like:

VSfmt_STS_RdMbb.............OK [manufacturer's bad block located]

VSfmt_STS_FMTing............OK [disk formatted OK]

VSfmt_STS_ChkPss............OK [check pass completed OK]

VSfmt_STS_BBRvec := x [x = number of bad blocks revectored]

VSfmt_RES_Succ [disk is successfully formatted]

>>>

== Using a MicroVAX I and the VAX Diagnostic Supervisor ==

Get the [http://xxx.com MicroVAX I diagnostic floppies set images]:

[[Writing Floppy-Fixed Disk and Tape Images to Real Media using VMS | Write <code>BL-T857D-DE MICROVAX I Diagnostics 2(3).RX5</code> onto an RX50 floppy or workalike.]]

Put floppy BL-T857D-DE into RX50 drive 0.

Boot VAX Diagnostic Supervisor (VDS):
B/10 DUA0

Load EHXRQ diagnostic
ATT RQDX1 HUB DUA 772150
ATT RX50 DUA DUA0
SET LOAD DUA0:[SYS0.SYSMAINT]
LOAD EHXRQ

Prepare & start formatting e.g. an RD52:
ATTACH RD52 DUA DUA1
SELECT DUA1
START /SECTION=FORMATTER

== Using a MicroVAX II or later MicroVAX and the MicroVAX Diagnostic Monitor ==

== Using a MicroPDP and the XXDP Diagnostics ==

ZRQBxx RQDX1/2

ZRQCxx RQDX3

PDP11_DiagnosticHandbook_XXDP_1988 mit Text.pdf

DR> STA

CHANGE HW (L) ? Y

# UNITS (D) ? 1

UNIT 0
Enter controller IP address (O) 172150 ?
What unit do you want to format [0-255] (D) 0 ? 1
Would you like to revector a single LBN only [Y/N] (L) N ?
Do you want to use the "AUTOFORMAT" Mode [Y/N] (L) Y ? N

Would you like to use the RCT - Revector known bad blocks [Y/N] (L) N ?

**** WARNING ****

[text about don't proceed if you're just kidding deleted]

Do you wish to continue [Y/N] (L) Y ?

MSCP Controller Model: 19
Microcode Version: 4

Do you want to use manufacturing bad block information [Y/N] (A) N ?

Downline load UIT [Y/N] (A) Y ?

UIT Drive Name
-------------------------------------------------------
0 RD51
1 RD52 part # 30-21721-02 (1 light on front panel)
2 RD52 part # 30-23227-02 (2 lights on front panel)
3 RD53
4 RD31
5 RD54
6 RD32

Enter Unit Identifier Table (UIT) [0-7] (D) ? 5

Continue if bad block information is inaccessible [Y/N] (A) N ? Y

Please type in the serial number [8-10 digits] (A) ? 05388342

Formatting of Drive 1 Begin.

[a long sequences of messages is displayed here, 1 per minute, showing the
progress of formatting and what step is in progress on which block number.]

Format Completed.

00001 Rev LBNs
00000 Bad RBNs
00000 Bad DBNs
00000 Bad XBNs
00001 retired

FCT was not used.

Drive 1 has been formatted successfully.

ZRQC EOP 1
0 TOTAL ERRS

DR>

[[Category: DEC Disk Drives]]
[[Category: MSCP Disk Drives]]
[[Category: DEC Non-removable-media Disks]]
[[Category: ST506 Disk Drives]]

SimH Classic

2025-11-09T11:00:38Z

Vaxorcist: /* See also */ * Link to Category:SIMH Tutorials added

Connect Multiple SIMH Network Instances on one Computer

2025-11-09T10:56:45Z

Vaxorcist: Category:Networking added

It is a known problem that you can run multiple instances of [[SIMH]] simulators on one computer, but cannot connect the network interfaces of those simulators directly.

You can either use multiple computers connected by a LAN to solve this, or do a special network setup.

Unfortunately I can only show you how to do this on Debian [[Linux]], with other Linux distributions it's probably similar. Windows: I don't know, sorry!

You may have to install some packages beforehand one time only (depending on your Debian configuration):

sudo apt install uml-utilities bridge-utils tcpdump

Run the following shell script as root:

#!/bin/sh

# Create four virtual tap network interfaces
tunctl -t tap0
tunctl -t tap1
tunctl -t tap2
tunctl -t tap3

# Create a virtual bridge
brctl addbr br0
brctl setfd br0 0

# Connect the four virtual interfaces to the virtual bridge
brctl addif br0 tap0
brctl addif br0 tap1
brctl addif br0 tap2
brctl addif br0 tap3

# Do a minimal configuration for the virtual interfaces
ifconfig tap0 0.0.0.0
ifconfig tap1 0.0.0.0
ifconfig tap2 0.0.0.0
ifconfig tap3 0.0.0.0

# Activate the virtual bridge
ip link set br0 up

# Activate the virtual interfaces
ifconfig tap0 up
ifconfig tap1 up
ifconfig tap2 up
ifconfig tap3 up

# Show virtual bridge configuration
brctl show

# Show interfaces
ip link

The settings will not survive a reboot.

This setup connects the four virtual interfaces '''tap0''', '''tap1''', '''tap2''', and '''tap3''' among themselves, but neither to the local computer nor to any other connected computers.

You can watch the network traffic on any of the virtual interfaces with the following command (just replace the interface name):

tcpdump -i tap0

You must be root to do this or prepend the command with '''sudo'''.

Use this SIMH command to attach to e.g. virtual interface '''tap0''', e.g.:
attach xq tap:tap0

See the SIMH [https://github.com/simh/simh/blob/master/0readme_ethernet.txt 0readme_ethernet.txt] for more info on the same topic.

[[Category:SIMH Tutorials]]
[[Category:Networking]]

Low-Level Formatting DEC MFM Disks

2025-11-07T08:04:02Z

Vaxorcist: Some categories added

There are several occasions where you possibly want (or even need) to low-level format a [[DEC]] [[MFM]] disk:

* Testing for bad blocks
* Reformatting from a PC-like low-level format
* Reformatting for use on another type of [[RQDX Series of MFM Disk & Floppy QBUS Controllers|RQDX]] MFM controller
* Reformatting for spoofing another disk model
* ...

Another scenario might be that you want to prepare a foreign MFM disk model as a replacement for a DEC MFM disk.

You can even reformat [[RLL]]-type disks for usage on MFM controllers for the price of loosing some disk space.

== Preparations ==

All you need is:

* A [[MicroVAX 2000]] / [[VAXstation 2000]]

or:

* An [[RQDX1/RQDX2 MFM Disk & Floppy QBUS Controllers|RQDX1, RQDX2]], or [[RQDX3 MFM Disk & Floppy QBUS Controller|RQDX3]] [[QBUS]] MFM controller suitable for your MFM disk, and
* An [[RX50]] Dual Floppy Drive, and
* A [[MicroPDP-11]], or
* A [[MicroVAX I]] / [[VAXstation I]], or
* A [[MicroVAX II]] / [[VAXstation II]], or
* A later [[QBUS]] based [[MicroVAX]] / [[VAXstation]]

== Using a VAXstation 2000 or MicroVAX 2000 and its ROM resident Diagnostics ==

=== Formatting a Known Hard Disk ===

Example of formatting an [[RD32]] hard disk.

Enter the following commands at your MicroVAX 2000 / VAXstation 2000 console prompt:

>>> '''TEST 70'''

VSfmt_QUE_unitno (0-2) ? '''0''' [enter the drive number of the hard disk]

VSfmt_STS_Siz........... '''RD32''' [formatter recognized DUA0 as a RD32]

VSfmt_QUE_SerNbr (0-999999999) '''29042836''' [enter the serial number for the drive]
[or enter a unique number for each unit]

VSfmt_QUE_RUsure (DUAx 1/0) ? '''1''' [where x equals the unit number]
[enter 1 for YES, 0 for NO]

VSfmt_STS_RdMbb.............OK [manufacturer's bad block located]

VSfmt_STS_FMTing............OK [disk formatted OK]

VSfmt_STS_ChkPss............OK [check pass completed OK]

VSfmt_STS_BBRvec := x [x = number of bad blocks revectored]

VSfmt_RES_Succ [disk is successfully formatted]

>>>

=== Formatting an Unknown Hard Disk ===

>>> '''TEST 70'''

VSfmt_QUE_unitno (0-2) ? '''0''' [Enter drive number]

VSfmt_STS_Siz .......... ???? [Formatter does not recognize drive type]

VSfmt_STS_EntUIB [Formatter wants drive details]

[this example is from the VS2000 technical manual]

xbnsiz :=54 [enter the number of transfer blocks]

dbnsiz :=48 [enter the number of diagnostic blocks]

lbnsiz :=83236 [enter the number of logical blocks]

rbnsiz :=200 [enter the number of replacement blocks]

surpun :=6 [enter the number of surfaces per unit]

cylpun :=820 [enter the number of cylinders per unit]

wrtprc :=820 [enter the write precompensation cylinder]

rctsiz :=4 [enter the size of the revectoring control table (RCT)]

rctnbr :=8 [enter the number of copies of the RCT]

secitl :=1 [enter the sector interleave]

stsskw :=2 [enter the surface to surface skew]

ctcskw :=9 [enter the cylinder to cylinder skew]

mediai :=627327008 [enter the MSCP media ID]

* Note this number is not dependent on disk geometry, but is the magic number for VMS to report on the type of disk. *
At this point, the formatter exits the query mode.

The next output to the screen is:
VSfmt_QUE_SerNbr (0-999999999) [enter the serial number for the drive]
[or enter a unique number for each unit]

VSfmt_QUE_RUsure (DUAx 1/0) ? [where x equals the unit number]
[enter 1 for YES, 0 for NO]

The formatter is now running, and the output should look like:

VSfmt_STS_RdMbb.............OK [manufacturer's bad block located]

VSfmt_STS_FMTing............OK [disk formatted OK]

VSfmt_STS_ChkPss............OK [check pass completed OK]

VSfmt_STS_BBRvec := x [x = number of bad blocks revectored]

VSfmt_RES_Succ [disk is successfully formatted]

>>>

== Using a MicroVAX I and the VAX Diagnostic Supervisor ==

Get the [http://xxx.com MicroVAX I diagnostic floppies set images]:

[[Writing Floppy-Fixed Disk and Tape Images to Real Media using VMS | Write <code>BL-T857D-DE MICROVAX I Diagnostics 2(3).RX5</code> onto an RX50 floppy or workalike.]]

Put floppy BL-T857D-DE into RX50 drive 0.

Boot VAX Diagnostic Supervisor (VDS):
B/10 DUA0

Load EHXRQ diagnostic
ATT RQDX1 HUB DUA 772150
ATT RX50 DUA DUA0
SET LOAD DUA0:[SYS0.SYSMAINT]
LOAD EHXRQ

Prepare & start formatting e.g. an RD52:
ATTACH RD52 DUA DUA1
SELECT DUA1
START /SECTION=FORMATTER

== Using a MicroVAX II or later MicroVAX and the MicroVAX Diagnostic Monitor ==

== Using a MicroPDP and the XXDP Diagnostics ==

ZRQBxx RQDX1/2

ZRQCxx RQDX3

PDP11_DiagnosticHandbook_XXDP_1988 mit Text.pdf

DR> STA

CHANGE HW (L) ? Y

# UNITS (D) ? 1

UNIT 0
Enter controller IP address (O) 172150 ?
What unit do you want to format [0-255] (D) 0 ? 1
Would you like to revector a single LBN only [Y/N] (L) N ?
Do you want to use the "AUTOFORMAT" Mode [Y/N] (L) Y ? N

Would you like to use the RCT - Revector known bad blocks [Y/N] (L) N ?

**** WARNING ****

[text about don't proceed if you're just kidding deleted]

Do you wish to continue [Y/N] (L) Y ?

MSCP Controller Model: 19
Microcode Version: 4

Do you want to use manufacturing bad block information [Y/N] (A) N ?

Downline load UIT [Y/N] (A) Y ?

UIT Drive Name
-------------------------------------------------------
0 RD51
1 RD52 part # 30-21721-02 (1 light on front panel)
2 RD52 part # 30-23227-02 (2 lights on front panel)
3 RD53
4 RD31
5 RD54
6 RD32

Enter Unit Identifier Table (UIT) [0-7] (D) ? 5

Continue if bad block information is inaccessible [Y/N] (A) N ? Y

Please type in the serial number [8-10 digits] (A) ? 05388342

Formatting of Drive 1 Begin.

[a long sequences of messages is displayed here, 1 per minute, showing the
progress of formatting and what step is in progress on which block number.]

Format Completed.

00001 Rev LBNs
00000 Bad RBNs
00000 Bad DBNs
00000 Bad XBNs
00001 retired

FCT was not used.

Drive 1 has been formatted successfully.

ZRQC EOP 1
0 TOTAL ERRS

DR>

[[Category: DEC Disk Drives]]
[[Category: MSCP Disk Drives]]
[[Category: DEC Non-removable-media Disks]]
[[Category: ST506 Disk Drives]]

RD32

2025-11-07T08:02:11Z

Vaxorcist: MicroVAX 2000 / Some more supporting DEC controllers and links added.

The '''RD32''' was a 42 MB 5.25" half height [[ST506 disk interface|ST506]] disk.

It was a re-labelled [[Seagate]] [[ST-251]].

It is supported by the following [[DEC]] [[MFM]] disk controllers:

* [[QBUS]] [[RQDX3 MFM Disk & Floppy QBUS Controller|RQDX3]]
* [[MicroVAX 2000]] / [[VAXstation 2000]] disk controller
* [[Rainbow 100]] disk controller (with newest firmware only)
* [[Professional 300 Series|Professional 350 / Professional 380]] disk controller (with newest firmware only)

Before using a Seagate ST-251 as an RD32 in a DEC computer, it has to be [[Low-Level Formatting DEC MFM Disks|formatted according to DEC specs]].

{{stub}}

==External links==

* [http://www.bitsavers.org/pdf/dec/brochures/DEC-DiskStorageSolutions.pdf Disk Storage Solutions for Desktop and Deskside Environments] - covers the RD32

[[Category: DEC ST506 Disk Drives]]

Low-Level Formatting DEC MFM Disks

2025-11-07T07:43:35Z

Vaxorcist: /* Formatting a Known Hard Disk */ Link added.

Low-Level Formatting DEC MFM Disks

2025-11-07T07:38:50Z

Vaxorcist: /* Preparations */ Some links added.

There are several occasions where you possibly want (or even need) to low-level format a [[DEC]] [[MFM]] disk:

* Testing for bad blocks
* Reformatting from a PC-like low-level format
* Reformatting for use on another type of [[RQDX Series of MFM Disk & Floppy QBUS Controllers|RQDX]] MFM controller
* Reformatting for spoofing another disk model
* ...

Another scenario might be that you want to prepare a foreign MFM disk model as a replacement for a DEC MFM disk.

You can even reformat [[RLL]]-type disks for usage on MFM controllers for the price of loosing some disk space.

== Preparations ==

All you need is:

* A [[MicroVAX 2000]] / [[VAXstation 2000]]

or:

* An [[RQDX1/RQDX2 MFM Disk & Floppy QBUS Controllers|RQDX1, RQDX2]], or [[RQDX3 MFM Disk & Floppy QBUS Controller|RQDX3]] [[QBUS]] MFM controller suitable for your MFM disk, and
* An [[RX50]] Dual Floppy Drive, and
* A [[MicroPDP-11]], or
* A [[MicroVAX I]] / [[VAXstation I]], or
* A [[MicroVAX II]] / [[VAXstation II]], or
* A later [[QBUS]] based [[MicroVAX]] / [[VAXstation]]

== Using a VAXstation 2000 or MicroVAX 2000 and its ROM resident Diagnostics ==

=== Formatting a Known Hard Disk ===

Example of formatting an RD32 hard disk:
>>> '''TEST 70'''

VSfmt_QUE_unitno (0-2) ? '''0''' [enter the drive number of the hard disk]

VSfmt_STS_Siz........... RD32 [formatter recognized DUA0 as a RD32]

VSfmt_QUE_SerNbr (0-999999999) '''29042836''' [enter the serial number for the drive]
[or enter a unique number for each unit]

VSfmt_QUE_RUsure (DUAx 1/0) ? '''1''' [where x equals the unit number]
[enter 1 for YES, 0 for NO]

VSfmt_STS_RdMbb.............OK [manufacturer's bad block located]

VSfmt_STS_FMTing............OK [disk formatted OK]

VSfmt_STS_ChkPss............OK [check pass completed OK]

VSfmt_STS_BBRvec := x [x = number of bad blocks revectored]

VSfmt_RES_Succ [disk is successfully formatted]

>>>

=== Formatting an Unknown Hard Disk ===

>>> '''TEST 70'''

VSfmt_QUE_unitno (0-2) ? '''0''' [Enter drive number]

VSfmt_STS_Siz .......... ???? [Formatter does not recognize drive type]

VSfmt_STS_EntUIB [Formatter wants drive details]

[this example is from the VS2000 technical manual]

xbnsiz :=54 [enter the number of transfer blocks]

dbnsiz :=48 [enter the number of diagnostic blocks]

lbnsiz :=83236 [enter the number of logical blocks]

rbnsiz :=200 [enter the number of replacement blocks]

surpun :=6 [enter the number of surfaces per unit]

cylpun :=820 [enter the number of cylinders per unit]

wrtprc :=820 [enter the write precompensation cylinder]

rctsiz :=4 [enter the size of the revectoring control table (RCT)]

rctnbr :=8 [enter the number of copies of the RCT]

secitl :=1 [enter the sector interleave]

stsskw :=2 [enter the surface to surface skew]

ctcskw :=9 [enter the cylinder to cylinder skew]

mediai :=627327008 [enter the MSCP media ID]

* Note this number is not dependent on disk geometry, but is the magic number for VMS to report on the type of disk. *
At this point, the formatter exits the query mode.

The next output to the screen is:
VSfmt_QUE_SerNbr (0-999999999) [enter the serial number for the drive]
[or enter a unique number for each unit]

VSfmt_QUE_RUsure (DUAx 1/0) ? [where x equals the unit number]
[enter 1 for YES, 0 for NO]

The formatter is now running, and the output should look like:

VSfmt_STS_RdMbb.............OK [manufacturer's bad block located]

VSfmt_STS_FMTing............OK [disk formatted OK]

VSfmt_STS_ChkPss............OK [check pass completed OK]

VSfmt_STS_BBRvec := x [x = number of bad blocks revectored]

VSfmt_RES_Succ [disk is successfully formatted]

>>>

== Using a MicroVAX I and the VAX Diagnostic Supervisor ==

Get the [http://xxx.com MicroVAX I diagnostic floppies set images]:

[[Writing Floppy-Fixed Disk and Tape Images to Real Media using VMS | Write <code>BL-T857D-DE MICROVAX I Diagnostics 2(3).RX5</code> onto an RX50 floppy or workalike.]]

Put floppy BL-T857D-DE into RX50 drive 0.

Boot VAX Diagnostic Supervisor (VDS):
B/10 DUA0

Load EHXRQ diagnostic
ATT RQDX1 HUB DUA 772150
ATT RX50 DUA DUA0
SET LOAD DUA0:[SYS0.SYSMAINT]
LOAD EHXRQ

Prepare & start formatting e.g. an RD52:
ATTACH RD52 DUA DUA1
SELECT DUA1
START /SECTION=FORMATTER

== Using a MicroVAX II or later MicroVAX and the MicroVAX Diagnostic Monitor ==

== Using a MicroPDP and the XXDP Diagnostics ==

ZRQBxx RQDX1/2

ZRQCxx RQDX3

PDP11_DiagnosticHandbook_XXDP_1988 mit Text.pdf

DR> STA

CHANGE HW (L) ? Y

# UNITS (D) ? 1

UNIT 0
Enter controller IP address (O) 172150 ?
What unit do you want to format [0-255] (D) 0 ? 1
Would you like to revector a single LBN only [Y/N] (L) N ?
Do you want to use the "AUTOFORMAT" Mode [Y/N] (L) Y ? N

Would you like to use the RCT - Revector known bad blocks [Y/N] (L) N ?

**** WARNING ****

[text about don't proceed if you're just kidding deleted]

Do you wish to continue [Y/N] (L) Y ?

MSCP Controller Model: 19
Microcode Version: 4

Do you want to use manufacturing bad block information [Y/N] (A) N ?

Downline load UIT [Y/N] (A) Y ?

UIT Drive Name
-------------------------------------------------------
0 RD51
1 RD52 part # 30-21721-02 (1 light on front panel)
2 RD52 part # 30-23227-02 (2 lights on front panel)
3 RD53
4 RD31
5 RD54
6 RD32

Enter Unit Identifier Table (UIT) [0-7] (D) ? 5

Continue if bad block information is inaccessible [Y/N] (A) N ? Y

Please type in the serial number [8-10 digits] (A) ? 05388342

Formatting of Drive 1 Begin.

[a long sequences of messages is displayed here, 1 per minute, showing the
progress of formatting and what step is in progress on which block number.]

Format Completed.

00001 Rev LBNs
00000 Bad RBNs
00000 Bad DBNs
00000 Bad XBNs
00001 retired

FCT was not used.

Drive 1 has been formatted successfully.

ZRQC EOP 1
0 TOTAL ERRS

DR>

Low-Level Formatting DEC MFM Disks

2025-11-06T21:14:13Z

Vaxorcist: New Page "Low-Level Formatting DEC MFM Disks"

There are several occasions where you possibly want (or even need) to low-level format a [[DEC]] [[MFM]] disk:

* Testing for bad blocks
* Reformatting from a PC-like low-level format
* Reformatting for use on another type of [[RQDX Series of MFM Disk & Floppy QBUS Controllers|RQDX]] MFM controller
* Reformatting for spoofing another disk model
* ...

Another scenario might be that you want to prepare a foreign MFM disk model as a replacement for a DEC MFM disk.

You can even reformat [[RLL]]-type disks for usage on MFM controllers for the price of loosing some disk space.

== Preparations ==

All you need is:

* A MicroVAX 2000 / VAXstation 2000

or:

* An [[RQDX1]], [[RQDX2]], or [[RQDX3]] [[QBUS]] MFM controller suitable for your MFM disk, and
* An [[RX50]] Dual Floppy Drive, and
* A MicroPDP, or
* A MicroVAX I / VAXstation I, or
* A MicroVAX II / VAXstation II, or
* A later QBUS based MicroVAX / VAXstation

== Using a VAXstation 2000 or MicroVAX 2000 and its ROM resident Diagnostics ==

=== Formatting a Known Hard Disk ===

Example of formatting an RD32 hard disk:
>>> '''TEST 70'''

VSfmt_QUE_unitno (0-2) ? '''0''' [enter the drive number of the hard disk]

VSfmt_STS_Siz........... RD32 [formatter recognized DUA0 as a RD32]

VSfmt_QUE_SerNbr (0-999999999) '''29042836''' [enter the serial number for the drive]
[or enter a unique number for each unit]

VSfmt_QUE_RUsure (DUAx 1/0) ? '''1''' [where x equals the unit number]
[enter 1 for YES, 0 for NO]

VSfmt_STS_RdMbb.............OK [manufacturer's bad block located]

VSfmt_STS_FMTing............OK [disk formatted OK]

VSfmt_STS_ChkPss............OK [check pass completed OK]

VSfmt_STS_BBRvec := x [x = number of bad blocks revectored]

VSfmt_RES_Succ [disk is successfully formatted]

>>>

=== Formatting an Unknown Hard Disk ===

>>> '''TEST 70'''

VSfmt_QUE_unitno (0-2) ? '''0''' [Enter drive number]

VSfmt_STS_Siz .......... ???? [Formatter does not recognize drive type]

VSfmt_STS_EntUIB [Formatter wants drive details]

[this example is from the VS2000 technical manual]

xbnsiz :=54 [enter the number of transfer blocks]

dbnsiz :=48 [enter the number of diagnostic blocks]

lbnsiz :=83236 [enter the number of logical blocks]

rbnsiz :=200 [enter the number of replacement blocks]

surpun :=6 [enter the number of surfaces per unit]

cylpun :=820 [enter the number of cylinders per unit]

wrtprc :=820 [enter the write precompensation cylinder]

rctsiz :=4 [enter the size of the revectoring control table (RCT)]

rctnbr :=8 [enter the number of copies of the RCT]

secitl :=1 [enter the sector interleave]

stsskw :=2 [enter the surface to surface skew]

ctcskw :=9 [enter the cylinder to cylinder skew]

mediai :=627327008 [enter the MSCP media ID]

* Note this number is not dependent on disk geometry, but is the magic number for VMS to report on the type of disk. *
At this point, the formatter exits the query mode.

The next output to the screen is:
VSfmt_QUE_SerNbr (0-999999999) [enter the serial number for the drive]
[or enter a unique number for each unit]

VSfmt_QUE_RUsure (DUAx 1/0) ? [where x equals the unit number]
[enter 1 for YES, 0 for NO]

The formatter is now running, and the output should look like:

VSfmt_STS_RdMbb.............OK [manufacturer's bad block located]

VSfmt_STS_FMTing............OK [disk formatted OK]

VSfmt_STS_ChkPss............OK [check pass completed OK]

VSfmt_STS_BBRvec := x [x = number of bad blocks revectored]

VSfmt_RES_Succ [disk is successfully formatted]

>>>

== Using a MicroVAX I and the VAX Diagnostic Supervisor ==

Get the [http://xxx.com MicroVAX I diagnostic floppies set images]:

[[Writing Floppy-Fixed Disk and Tape Images to Real Media using VMS | Write <code>BL-T857D-DE MICROVAX I Diagnostics 2(3).RX5</code> onto an RX50 floppy or workalike.]]

Put floppy BL-T857D-DE into RX50 drive 0.

Boot VAX Diagnostic Supervisor (VDS):
B/10 DUA0

Load EHXRQ diagnostic
ATT RQDX1 HUB DUA 772150
ATT RX50 DUA DUA0
SET LOAD DUA0:[SYS0.SYSMAINT]
LOAD EHXRQ

Prepare & start formatting e.g. an RD52:
ATTACH RD52 DUA DUA1
SELECT DUA1
START /SECTION=FORMATTER

== Using a MicroVAX II or later MicroVAX and the MicroVAX Diagnostic Monitor ==

== Using a MicroPDP and the XXDP Diagnostics ==

ZRQBxx RQDX1/2

ZRQCxx RQDX3

PDP11_DiagnosticHandbook_XXDP_1988 mit Text.pdf

DR> STA

CHANGE HW (L) ? Y

# UNITS (D) ? 1

UNIT 0
Enter controller IP address (O) 172150 ?
What unit do you want to format [0-255] (D) 0 ? 1
Would you like to revector a single LBN only [Y/N] (L) N ?
Do you want to use the "AUTOFORMAT" Mode [Y/N] (L) Y ? N

Would you like to use the RCT - Revector known bad blocks [Y/N] (L) N ?

**** WARNING ****

[text about don't proceed if you're just kidding deleted]

Do you wish to continue [Y/N] (L) Y ?

MSCP Controller Model: 19
Microcode Version: 4

Do you want to use manufacturing bad block information [Y/N] (A) N ?

Downline load UIT [Y/N] (A) Y ?

UIT Drive Name
-------------------------------------------------------
0 RD51
1 RD52 part # 30-21721-02 (1 light on front panel)
2 RD52 part # 30-23227-02 (2 lights on front panel)
3 RD53
4 RD31
5 RD54
6 RD32

Enter Unit Identifier Table (UIT) [0-7] (D) ? 5

Continue if bad block information is inaccessible [Y/N] (A) N ? Y

Please type in the serial number [8-10 digits] (A) ? 05388342

Formatting of Drive 1 Begin.

[a long sequences of messages is displayed here, 1 per minute, showing the
progress of formatting and what step is in progress on which block number.]

Format Completed.

00001 Rev LBNs
00000 Bad RBNs
00000 Bad DBNs
00000 Bad XBNs
00001 retired

FCT was not used.

Drive 1 has been formatted successfully.

ZRQC EOP 1
0 TOTAL ERRS

DR>

Periodic Payment License

2025-11-06T16:05:16Z

Vaxorcist: New page "Periodic Payment License"

[[DEC]]s '''Periodic Payment License''' (PPL) was a kind of software leasing system, which was introduced about 1987.

Instead of buying a relatively expensive traditional '''Paid-Up''' license (with unlimited validity), you could start with a one-time '''Initial License Charge''' and monthly '''Periodic Payment License''' (PPL) fees.

Which of the two options leads to lower overall costs depends on the period of use.

Let's have a look at an example:

Q2001-1P [[VAX 8550]] [[VMS]] INITIAL LICENSE FEE 1 x 3,150 = 3,150
Q2001-JP VAX 8550 VMS MONTHLY PERIODIC PAYMENT LICENSE FEE 41 x 1,134 = 46,494
Total = 49,644

Q2001-UZ VMS PAID-UP LICENSE 49,875

The break-even point is reached after 41 months (three years and five months) of use, from then on the "perpetual" license is cheaper, with depreciation and interest not taken into account.

[[Category: Digital Equipment Corporation]]