Computer History Wiki - User contributions [en]

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

2025-11-09T11:00:38Z

Vaxorcist: /* See also */ * Link to Category:SIMH Tutorials added

'''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]]

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]]

DEC Software-related Order Codes

2025-11-06T13:58:50Z

Vaxorcist: /* Cluster Licensing */ Some corrections and additons ...

DEC Software Media, Software License, Software Service, and Software Manual Order Codes

There are two formats whose use overlaps in time:

* 7-Character Format XXXXX-XX
* 9-Character Format XX-XXXXX-XX

The latter was introduced in 1988 for Software Products and Services for new processors while Software Products and Services for processors already introduced remained in the old 7-Character Format.

== 7-Character Format XXXXX-XX ==

Samples:
*ZYA06-P3 MicroPDP-11 RX33 Formatter Kit
*

'''1st Letter = Type of Software''':
*Y - [[Computer Special Systems]] Software
*Z - Diagnostics
*Q - System and Application Software

'''2nd Letter = Processor Identifier''':
*0 - [[MicroVAX]]/[[VAXserver]] 3500 and 3600
*1 - MicroVAX/VAXserver 3500 and 3600/[[VAXstation]] 3200 and 3500
*2 - [[VAX 8700]] and [[VAX 8550]]
*3 - [[MicroVAX 2000]]
*4 - [[VAXstation II]]
*5 - [[VAX 8200]] and [[VAX 8250]]
*6 - [[VAXmate]]
*7 - [[VAX 8300]] and [[VAX 8350]]
*8 - [[VAXstation 2000]]
*9 - [[VAX 8500]] and [[VAX 8530]]
*A - [[Digital Classified Software]], USA
*B - [[Professional 300 Series]]
*C - [[VAX-11/725]] and [[VAX-11/730]]
*D - [[VAX-11/750]]
*E - [[VAX-11/780]], [[VAX-11/782]], and [[VAX-11/785]]
*F - [[PDP-8]], [[WPS-8]], [[DECmate I]]
*G - Digital Classified Software, Internal
*H - [[DECsystem 10]]
*I - Digital Classified Software, GIA
*J - [[PDP-11]] [[UNIBUS]]-based ([[RT-11]], [[ULTRIX-11]])
*K - [[VAX 8600]] and [[VAX 8650]]
*L - All Models
*M - [[VAX 8800]], [[VAX 8974]], and [[VAX 8978]]
*N - [[MicroVAX I]]
*P - PDP-11 ([[RSTS]])
*Q - [[VAXstation I]]
*R - PDP-11 ([[RSX-11M]]/[[RSX-11M-PLUS]])
*S - Software
*T - [[DECsystem 20]]
*U - Digital Classified Software, Europe
*V - [[Rainbow]]
*W - [[DECmate II]]
*X - Cross prod, and/or no support services
*Y - [[MicroPDP-11]] [[QBUS]]-based
*Z - [[MicroVAX II]]

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''<br>
:Exception: Digital Classified Software, 2nd letter = A, G, I, U

'''6th Letter = Product Type''':
*1 - Dispatch Subscription Service
*2 - Dispatch Subscription
*3 - Self-Maintenance Service
*4 - Source Updates Service
*5 - Startup Service Level I
*6 - Additional Telephone Support Center Contact
*7 - Startup Service Level II
*8 - Basic Service
*9 - DECsupport Service
*A - Single-use License, Binaries, Documentation, Warranty
*B - Startup Service Level III
*C - License and Key, no Support
*D - License only
*E - Source License and Distribution
*F - Source Distribution and Listings / Microfiche
*G - Documentation Only (-GZ)
*H - Distribution and Documentation
*I - Installation Service
*J - PPL - Periodic Payment License ([[VAXcluster]])
*K - Documentation Service
*L - Sources Update
*M - Location-use Source License, Microfiche List
*N - Source Distribution
*P - No License, Binaries only
*Q - Single-use License for VAXcluster Node
*R - No License, Binaries Documentation
*S - DECstart Service
*T - Update
*U - Single-Use License
*V - For Service Delivery Only
*W - Warranty Update / For Service Delivery Only
*X - Single-use Sources License, Sources and Binaries, Documents, Warranty
*Y - Single-use Sources License, Sources and Binaries, Documents
*Z - Defense Acquisition Regulation/NASA Marking, Maintenance Service

'''7th Letter = Software Medium''':
*2 - [[RX180]]
*3 - [[RX50]]
*4 - [[RC25]]
*5 - [[TK50]]
*6 - [[TK25]]
*7 - [[RX33]]
*8 - [[CDROM]]
*9 - ???
*A - [[Magnetic tape|9-Track Tape 6250 BPI]] / [[LINC tape]]
*B - [[Paper Tape]] / [[RX24]]
*C - [[DECtape]] / [[RX23]]
*D - [[Magnetic tape|9-Track Tape 800 BPI 600ft]]
*E - [[RK03]] / [[RK05]]
*F - [[Magnetic tape|7-Track Tape]]
*G - [[TU58]]
*H - [[RL02]]
*I - [[RX31]]
*J - [[RA60]]
*K - [[RP04]]
*L - [[RP06]]
*M - [[Magnetic tape|9-Track Tape 1600 BPI 2400ft]]
*N - [[TU60]]
*P - Cassette Tape ([[QIC]], [[DAT]], ...) / [[Magnetic tape|9 Track Magtape 800 BPI 2400ft]]
*Q - [[RL01]]
*R - [[Microfiche]]
*S - [[ROM]]
*T - [[RK06]]
*V - [[RK07]]
*W - Multimedia
*X - [[RX02]]
*Y - [[RX01]]
*Z - No Hardware Dependency / Paper

== 9-Character Format XX-XXXXX-XX ==

With the advent of [[VMS]] V5 and as new VAX processors were introduced, the Software Products and Services used the new Software Model Number, a 9-character format: '''XX-XXXXX-XX'''.

The new numbering scheme was presented with the DEC U.S. Price List Q3 FY88 (December 1987) and introduced with DEC U.S. Price List Q1 FY89 (July 1988), or somewhere in between. Both schemes existed in parallel, the new one for new software packages and new hardware models.

Two different ways of licensing were introduced together with the new numbering scheme:
* [[VAXcluster|Cluster]] Licensing
* CPU Licensing

=== Cluster and User/Activity Licensing ===

'''Cluster Licenses''' are identified by the letters "'''J'''" and "'''U'''" in the 8th position of the code.

'''User/Activity Licenses''' are identified by the letter "'''P'''" in the 8th position of the code.

'''1st and 2nd Letter'''
*QL - Licenses
*QT - SPS (Software Product Services)
*QA - Media and Documentation Kits
*QB - Packaged Software Components (License/Kit/SPS)

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''

'''6th Letter = CC (Country Code):'''
*A - American English
*E - British English
*G - German
*9 - Language neutral

'''7th Letter = Processor Type'''

*A = VAX Cross-product, Generic
*B = MicroVAX 3500/3600
*C = VAXstation 3200/3500, VAXserver 3500/3600/3602
*D = VAX 6240/8800/8820
*E = VAX 8700/8550/8810
*F = VAX 8600/8650
*G = VAX8530
*H = VAX 8300/8350
*J = VAX 8200/8250
*K = VAX 780/782/785
*L = VAX 750
*M = VAX 725/730
*N = MicroVAX II/MicroVAX I
*P = MicroVAX 2000
*Q = VAXstation II/VAXstation I
*R = VAXstation 2000
*U = VAX8830
*V = VAX 8840. 8S74, B842
*W = PC Software (includes VAXmate)
*x = PDP Cross Product Generic
*2 = VAX6210
*3 = VAX6220
*4 = VAX6230
*5 = VAX8978
*9 = Processor Tier Neutral

'''8th Letter = License Type'''

<tbd>

'''9th Letter = License Information'''

<tbd>

=== CPU Licensing ===

Samples:
*QL-056AF-AA

'''1st and 2nd Letter = Software Product Type'''
* QA - Software documentation, media, and other software kits
* QB - Packaged software components
* QC - Software subassemblies
* QL - Software licenses (DEC processor tier, and platform licenses)
* QM - Software licenses (PC & standalone third-party license agreements)
* QP - Packaged software licenses
* QQ - Country information components
* QR - Assigned software uses
* QS - Professional services project and consulting services
* QT - Software product services
* QU - Software product services
* QW - Cross-functional service packages (CFSP)
* QX - Diagnostic/maintenance tools licenses
* QY - Diagnostic/maintenance tools services
* QZ - Diagnostic/maintenance tools documentation, media, and other hardware information kits
* Q2 - Software application products: license, media & documentation, and SPS
* Q3 - Software application products: license, media & documentation, and SPS

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''

'''6th Letter = Unknown (usually "A" or "G")'''

'''7th Letter = CPU Code:'''
*B - MicroVAX 3500, 3600
*C - VAXstation 3200, 3500, 8000
*D - VAX 8800, 6240, 8820
*E - VAX 8550, 8700, 8810
*F - VAX 8600, 8650
*G - VAX 8530
*H - VAX 8300, 8350
*J - VAX 8200, 11/782
*K - VAX-11/780, 11/785
*L - VAX-11/750
*M - VAX-11/730, 11/725
*N - MicroVAX II
*P - MicroVAX 2000
*Q - VAXstation II
*R - VAXstation 2000
*S - MicroVAX 3300, 3400
*U - VAX 8830, 8842
*V - VAX 8840
*2 - VAX 6210
*3 - VAX 6220
*4 - VAX 6230

'''8th and 9th Letter = Unknown (usually "AA")'''

== External References ==

*AA-5074O-RK System Software Information
*IAS 3.4A SPD
*EE-26108-68-84 DIGITAL Microcomponents Products U.S. Price List October-December 1984
*EE-18587-04-80 PDP-11, VAX-11 Price List April - September 1980
*ED PDP Systems and Options Catalog 1988

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

DEC Software-related Order Codes

2025-11-06T11:23:37Z

Vaxorcist: /* 9-Character Format XX-XXXXX-XX */ Link added

DEC Software Media, Software License, Software Service, and Software Manual Order Codes

There are two formats whose use overlaps in time:

* 7-Character Format XXXXX-XX
* 9-Character Format XX-XXXXX-XX

The latter was introduced in 1988 for Software Products and Services for new processors while Software Products and Services for processors already introduced remained in the old 7-Character Format.

== 7-Character Format XXXXX-XX ==

Samples:
*ZYA06-P3 MicroPDP-11 RX33 Formatter Kit
*

'''1st Letter = Type of Software''':
*Y - [[Computer Special Systems]] Software
*Z - Diagnostics
*Q - System and Application Software

'''2nd Letter = Processor Identifier''':
*0 - [[MicroVAX]]/[[VAXserver]] 3500 and 3600
*1 - MicroVAX/VAXserver 3500 and 3600/[[VAXstation]] 3200 and 3500
*2 - [[VAX 8700]] and [[VAX 8550]]
*3 - [[MicroVAX 2000]]
*4 - [[VAXstation II]]
*5 - [[VAX 8200]] and [[VAX 8250]]
*6 - [[VAXmate]]
*7 - [[VAX 8300]] and [[VAX 8350]]
*8 - [[VAXstation 2000]]
*9 - [[VAX 8500]] and [[VAX 8530]]
*A - [[Digital Classified Software]], USA
*B - [[Professional 300 Series]]
*C - [[VAX-11/725]] and [[VAX-11/730]]
*D - [[VAX-11/750]]
*E - [[VAX-11/780]], [[VAX-11/782]], and [[VAX-11/785]]
*F - [[PDP-8]], [[WPS-8]], [[DECmate I]]
*G - Digital Classified Software, Internal
*H - [[DECsystem 10]]
*I - Digital Classified Software, GIA
*J - [[PDP-11]] [[UNIBUS]]-based ([[RT-11]], [[ULTRIX-11]])
*K - [[VAX 8600]] and [[VAX 8650]]
*L - All Models
*M - [[VAX 8800]], [[VAX 8974]], and [[VAX 8978]]
*N - [[MicroVAX I]]
*P - PDP-11 ([[RSTS]])
*Q - [[VAXstation I]]
*R - PDP-11 ([[RSX-11M]]/[[RSX-11M-PLUS]])
*S - Software
*T - [[DECsystem 20]]
*U - Digital Classified Software, Europe
*V - [[Rainbow]]
*W - [[DECmate II]]
*X - Cross prod, and/or no support services
*Y - [[MicroPDP-11]] [[QBUS]]-based
*Z - [[MicroVAX II]]

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''<br>
:Exception: Digital Classified Software, 2nd letter = A, G, I, U

'''6th Letter = Product Type''':
*1 - Dispatch Subscription Service
*2 - Dispatch Subscription
*3 - Self-Maintenance Service
*4 - Source Updates Service
*5 - Startup Service Level I
*6 - Additional Telephone Support Center Contact
*7 - Startup Service Level II
*8 - Basic Service
*9 - DECsupport Service
*A - Single-use License, Binaries, Documentation, Warranty
*B - Startup Service Level III
*C - License and Key, no Support
*D - License only
*E - Source License and Distribution
*F - Source Distribution and Listings / Microfiche
*G - Documentation Only (-GZ)
*H - Distribution and Documentation
*I - Installation Service
*J - PPL - Periodic Payment License ([[VAXcluster]])
*K - Documentation Service
*L - Sources Update
*M - Location-use Source License, Microfiche List
*N - Source Distribution
*P - No License, Binaries only
*Q - Single-use License for VAXcluster Node
*R - No License, Binaries Documentation
*S - DECstart Service
*T - Update
*U - Single-Use License
*V - For Service Delivery Only
*W - Warranty Update / For Service Delivery Only
*X - Single-use Sources License, Sources and Binaries, Documents, Warranty
*Y - Single-use Sources License, Sources and Binaries, Documents
*Z - Defense Acquisition Regulation/NASA Marking, Maintenance Service

'''7th Letter = Software Medium''':
*2 - [[RX180]]
*3 - [[RX50]]
*4 - [[RC25]]
*5 - [[TK50]]
*6 - [[TK25]]
*7 - [[RX33]]
*8 - [[CDROM]]
*9 - ???
*A - [[Magnetic tape|9-Track Tape 6250 BPI]] / [[LINC tape]]
*B - [[Paper Tape]] / [[RX24]]
*C - [[DECtape]] / [[RX23]]
*D - [[Magnetic tape|9-Track Tape 800 BPI 600ft]]
*E - [[RK03]] / [[RK05]]
*F - [[Magnetic tape|7-Track Tape]]
*G - [[TU58]]
*H - [[RL02]]
*I - [[RX31]]
*J - [[RA60]]
*K - [[RP04]]
*L - [[RP06]]
*M - [[Magnetic tape|9-Track Tape 1600 BPI 2400ft]]
*N - [[TU60]]
*P - Cassette Tape ([[QIC]], [[DAT]], ...) / [[Magnetic tape|9 Track Magtape 800 BPI 2400ft]]
*Q - [[RL01]]
*R - [[Microfiche]]
*S - [[ROM]]
*T - [[RK06]]
*V - [[RK07]]
*W - Multimedia
*X - [[RX02]]
*Y - [[RX01]]
*Z - No Hardware Dependency / Paper

== 9-Character Format XX-XXXXX-XX ==

With the advent of [[VMS]] V5 and as new VAX processors were introduced, the Software Products and Services used the new Software Model Number, a 9-character format: '''XX-XXXXX-XX'''.

The new numbering scheme was presented with the DEC U.S. Price List Q3 FY88 (December 1987) and introduced with DEC U.S. Price List Q1 FY89 (July 1988), or somewhere in between. Both schemes existed in parallel, the new one for new software packages and new hardware models.

Two different ways of licensing were introduced together with the new numbering scheme:
* [[VAXcluster|Cluster]] Licensing
* CPU Licensing

=== Cluster Licensing ===

'''1st and 2nd Letter'''
*QL - Licenses
*QT - SPS (Software Product Services)
*QA - Media and Documentation Kits
*QB - Packaged Software Components (License/Kit/SPS)

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''

'''6th Letter = CC (Country Code):'''
*A - American English
*E - British English
*G - German

'''8th and 9th Letter are dependent on the first two Letters'''

<tbd>

=== CPU Licensing ===

Samples:
*QL-056AF-AA

'''1st and 2nd Letter = Software Product Type'''
* QA - Software documentation, media, and other software kits
* QB - Packaged software components
* QC - Software subassemblies
* QL - Software licenses (DEC processor tier, and platform licenses)
* QM - Software licenses (PC & standalone third-party license agreements)
* QP - Packaged software licenses
* QQ - Country information components
* QR - Assigned software uses
* QS - Professional services project and consulting services
* QT - Software product services
* QU - Software product services
* QW - Cross-functional service packages (CFSP)
* QX - Diagnostic/maintenance tools licenses
* QY - Diagnostic/maintenance tools services
* QZ - Diagnostic/maintenance tools documentation, media, and other hardware information kits
* Q2 - Software application products: license, media & documentation, and SPS
* Q3 - Software application products: license, media & documentation, and SPS

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''

'''6th Letter = Unknown (usually "A" or "G")'''

'''7th Letter = CPU Code:'''
*B - MicroVAX 3500, 3600
*C - VAXstation 3200, 3500, 8000
*D - VAX 8800, 6240, 8820
*E - VAX 8550, 8700, 8810
*F - VAX 8600, 8650
*G - VAX 8530
*H - VAX 8300, 8350
*J - VAX 8200, 11/782
*K - VAX-11/780, 11/785
*L - VAX-11/750
*M - VAX-11/730, 11/725
*N - MicroVAX II
*P - MicroVAX 2000
*Q - VAXstation II
*R - VAXstation 2000
*S - MicroVAX 3300, 3400
*U - VAX 8830, 8842
*V - VAX 8840
*2 - VAX 6210
*3 - VAX 6220
*4 - VAX 6230

'''8th and 9th Letter = Unknown (usually "AA")'''

== External References ==

*AA-5074O-RK System Software Information
*IAS 3.4A SPD
*EE-26108-68-84 DIGITAL Microcomponents Products U.S. Price List October-December 1984
*EE-18587-04-80 PDP-11, VAX-11 Price List April - September 1980
*ED PDP Systems and Options Catalog 1988

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

DEC Software-related Order Codes

2025-11-06T11:20:34Z

Vaxorcist: /* 9-Character Format XX-XXXXX-XX */ Some details added

DEC Software Media, Software License, Software Service, and Software Manual Order Codes

There are two formats whose use overlaps in time:

* 7-Character Format XXXXX-XX
* 9-Character Format XX-XXXXX-XX

The latter was introduced in 1988 for Software Products and Services for new processors while Software Products and Services for processors already introduced remained in the old 7-Character Format.

== 7-Character Format XXXXX-XX ==

Samples:
*ZYA06-P3 MicroPDP-11 RX33 Formatter Kit
*

'''1st Letter = Type of Software''':
*Y - [[Computer Special Systems]] Software
*Z - Diagnostics
*Q - System and Application Software

'''2nd Letter = Processor Identifier''':
*0 - [[MicroVAX]]/[[VAXserver]] 3500 and 3600
*1 - MicroVAX/VAXserver 3500 and 3600/[[VAXstation]] 3200 and 3500
*2 - [[VAX 8700]] and [[VAX 8550]]
*3 - [[MicroVAX 2000]]
*4 - [[VAXstation II]]
*5 - [[VAX 8200]] and [[VAX 8250]]
*6 - [[VAXmate]]
*7 - [[VAX 8300]] and [[VAX 8350]]
*8 - [[VAXstation 2000]]
*9 - [[VAX 8500]] and [[VAX 8530]]
*A - [[Digital Classified Software]], USA
*B - [[Professional 300 Series]]
*C - [[VAX-11/725]] and [[VAX-11/730]]
*D - [[VAX-11/750]]
*E - [[VAX-11/780]], [[VAX-11/782]], and [[VAX-11/785]]
*F - [[PDP-8]], [[WPS-8]], [[DECmate I]]
*G - Digital Classified Software, Internal
*H - [[DECsystem 10]]
*I - Digital Classified Software, GIA
*J - [[PDP-11]] [[UNIBUS]]-based ([[RT-11]], [[ULTRIX-11]])
*K - [[VAX 8600]] and [[VAX 8650]]
*L - All Models
*M - [[VAX 8800]], [[VAX 8974]], and [[VAX 8978]]
*N - [[MicroVAX I]]
*P - PDP-11 ([[RSTS]])
*Q - [[VAXstation I]]
*R - PDP-11 ([[RSX-11M]]/[[RSX-11M-PLUS]])
*S - Software
*T - [[DECsystem 20]]
*U - Digital Classified Software, Europe
*V - [[Rainbow]]
*W - [[DECmate II]]
*X - Cross prod, and/or no support services
*Y - [[MicroPDP-11]] [[QBUS]]-based
*Z - [[MicroVAX II]]

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''<br>
:Exception: Digital Classified Software, 2nd letter = A, G, I, U

'''6th Letter = Product Type''':
*1 - Dispatch Subscription Service
*2 - Dispatch Subscription
*3 - Self-Maintenance Service
*4 - Source Updates Service
*5 - Startup Service Level I
*6 - Additional Telephone Support Center Contact
*7 - Startup Service Level II
*8 - Basic Service
*9 - DECsupport Service
*A - Single-use License, Binaries, Documentation, Warranty
*B - Startup Service Level III
*C - License and Key, no Support
*D - License only
*E - Source License and Distribution
*F - Source Distribution and Listings / Microfiche
*G - Documentation Only (-GZ)
*H - Distribution and Documentation
*I - Installation Service
*J - PPL - Periodic Payment License ([[VAXcluster]])
*K - Documentation Service
*L - Sources Update
*M - Location-use Source License, Microfiche List
*N - Source Distribution
*P - No License, Binaries only
*Q - Single-use License for VAXcluster Node
*R - No License, Binaries Documentation
*S - DECstart Service
*T - Update
*U - Single-Use License
*V - For Service Delivery Only
*W - Warranty Update / For Service Delivery Only
*X - Single-use Sources License, Sources and Binaries, Documents, Warranty
*Y - Single-use Sources License, Sources and Binaries, Documents
*Z - Defense Acquisition Regulation/NASA Marking, Maintenance Service

'''7th Letter = Software Medium''':
*2 - [[RX180]]
*3 - [[RX50]]
*4 - [[RC25]]
*5 - [[TK50]]
*6 - [[TK25]]
*7 - [[RX33]]
*8 - [[CDROM]]
*9 - ???
*A - [[Magnetic tape|9-Track Tape 6250 BPI]] / [[LINC tape]]
*B - [[Paper Tape]] / [[RX24]]
*C - [[DECtape]] / [[RX23]]
*D - [[Magnetic tape|9-Track Tape 800 BPI 600ft]]
*E - [[RK03]] / [[RK05]]
*F - [[Magnetic tape|7-Track Tape]]
*G - [[TU58]]
*H - [[RL02]]
*I - [[RX31]]
*J - [[RA60]]
*K - [[RP04]]
*L - [[RP06]]
*M - [[Magnetic tape|9-Track Tape 1600 BPI 2400ft]]
*N - [[TU60]]
*P - Cassette Tape ([[QIC]], [[DAT]], ...) / [[Magnetic tape|9 Track Magtape 800 BPI 2400ft]]
*Q - [[RL01]]
*R - [[Microfiche]]
*S - [[ROM]]
*T - [[RK06]]
*V - [[RK07]]
*W - Multimedia
*X - [[RX02]]
*Y - [[RX01]]
*Z - No Hardware Dependency / Paper

== 9-Character Format XX-XXXXX-XX ==

With the advent of VMS V5 and as new VAX processors were introduced, the Software Products and Services used the new Software Model Number, a 9-character format: '''XX-XXXXX-XX'''.

The new numbering scheme was presented with the DEC U.S. Price List Q3 FY88 (December 1987) and introduced with DEC U.S. Price List Q1 FY89 (July 1988), or somewhere in between. Both schemes existed in parallel, the new one for new software packages and new hardware models.

Two different ways of licensing were introduced together with the new numbering scheme:
* Cluster Licensing
* CPU Licensing

=== Cluster Licensing ===

'''1st and 2nd Letter'''
*QL - Licenses
*QT - SPS (Software Product Services)
*QA - Media and Documentation Kits
*QB - Packaged Software Components (License/Kit/SPS)

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''

'''6th Letter = CC (Country Code):'''
*A - American English
*E - British English
*G - German

'''8th and 9th Letter are dependent on the first two Letters'''

<tbd>

=== CPU Licensing ===

Samples:
*QL-056AF-AA

'''1st and 2nd Letter = Software Product Type'''
* QA - Software documentation, media, and other software kits
* QB - Packaged software components
* QC - Software subassemblies
* QL - Software licenses (DEC processor tier, and platform licenses)
* QM - Software licenses (PC & standalone third-party license agreements)
* QP - Packaged software licenses
* QQ - Country information components
* QR - Assigned software uses
* QS - Professional services project and consulting services
* QT - Software product services
* QU - Software product services
* QW - Cross-functional service packages (CFSP)
* QX - Diagnostic/maintenance tools licenses
* QY - Diagnostic/maintenance tools services
* QZ - Diagnostic/maintenance tools documentation, media, and other hardware information kits
* Q2 - Software application products: license, media & documentation, and SPS
* Q3 - Software application products: license, media & documentation, and SPS

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''

'''6th Letter = Unknown (usually "A" or "G")'''

'''7th Letter = CPU Code:'''
*B - MicroVAX 3500, 3600
*C - VAXstation 3200, 3500, 8000
*D - VAX 8800, 6240, 8820
*E - VAX 8550, 8700, 8810
*F - VAX 8600, 8650
*G - VAX 8530
*H - VAX 8300, 8350
*J - VAX 8200, 11/782
*K - VAX-11/780, 11/785
*L - VAX-11/750
*M - VAX-11/730, 11/725
*N - MicroVAX II
*P - MicroVAX 2000
*Q - VAXstation II
*R - VAXstation 2000
*S - MicroVAX 3300, 3400
*U - VAX 8830, 8842
*V - VAX 8840
*2 - VAX 6210
*3 - VAX 6220
*4 - VAX 6230

'''8th and 9th Letter = Unknown (usually "AA")'''

== External References ==

*AA-5074O-RK System Software Information
*IAS 3.4A SPD
*EE-26108-68-84 DIGITAL Microcomponents Products U.S. Price List October-December 1984
*EE-18587-04-80 PDP-11, VAX-11 Price List April - September 1980
*ED PDP Systems and Options Catalog 1988

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

DEC Packaged System Nomenclature

2025-11-05T09:31:33Z

Vaxorcist: New page: "DEC Packaged System Nomenclature"

== Introduction ==

One of [[DEC]]’s sales strategies was to sell [[computer]]s and accessories not only individually, but in coordinated combinations, the so-called “'''Packaged Systems'''”.

DEC promoted its Packaged Systems as balanced solutions for customer needs, providing all the components ([[hardware]], [[software]], and [[license]]s) to successfully develop and run a customers applications. Another incentive was that the price for a complete solution was cheaper than if all components had been purchased separately.

But that was only half the truth - some Packaged Systems lacked:
* Sufficient memory
* Service
* Operating system media
* Operating system manuals
* Console terminal

There were other customer specific components that had to be added anyway, e.g.:
* User terminals
* Application software

For DEC, the benefits included better inventory and production planning and improved customer loyalty by making purchases from third-party suppliers less attractive. But there was also a serious disadvantage for customers (which they often only noticed after purchase) - the [[main memory]] of the Packaged Systems was notoriously undersized.

For those interested in DEC computer history and for DEC collectors, the Packaged Systems offer an insight into typical computer configurations of small, medium and large systems.

With DEC's typical thoroughness, a coherent naming system was developed, which was called "'''Packaged System Nomenclature'''".

A nine digit designation ('''XX-XXXXX-XX''') provides information about:

{| class="wikitable" style="text-align: center;
|+ Packaged System Nomenclature
|-
! Digit !! Meaning
|-
| 1 || Memory Type
|-
| 2 || Operating System / License
|-
| - ||
|-
| 3 || Processor
|-
| 4 || Processor
|-
| 5 || System Device
|-
| 6 || Backup/Load Device
|-
| 7 || Revision
|-
| - ||
|-
| 8 || Console Terminal
|-
| 9 || Power/Software Support
|}

== Packaged Systems Examples ==

=== PDP-11 Packages ===

* CM-20JJA-LA:
** C = [[Core]] Memory
** M = QJ628-AE [[RSX-11M]] Single-use License, Binaries, Documentation, Warranty
** 20 = [[PDP-11/04]] CPU
** J = [[RK05]] System Disk
** J = RK05 Load Device
** A = 1st. Revision
** L = [[LA36]] Console Terminal
** A = 120V/60Hz, fully supported

* SX-RXMMA-EN:
** S = [[Solid State]] Memory
** X = QJB56-UZ [[PDP-11/23]] General Purpose Single-use License
** RX = PDP-11/23+
** M = [[RL02]] System Disk
** M = RL02 Load Device
** A = 1st. Revision
** E = No Console Terminal included
** N = 240V/50Hz, license only

=== VAX Packages ===

* SV-BXDBA-CA:
** S = Solid State Memory
** V = QD001-AM [[VAX]]/[[VMS]] License for [[VAX-11/750]]
** BX = VAX-11/750
** D = [[RM05]] System Disk
** B = [[TU77]] Load Device
** A = 1st. Revision
** C = [[LA120]] Console Terminal
** A = 120V/60Hz, fully supported

== Subsequent Package Designations ==

* "PRECONFIGURED SYSTEMS"
* "SYSTEM BUILDING BLOCKS"

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

DEC Software-related Order Codes

2025-11-03T08:53:29Z

Vaxorcist: /* 7-Character Format XXXXX-XX */ Software Medium Code "9" added, meaning unknown

DEC Software Media, Software License, Software Service, and Software Manual Order Codes

There are two formats whose use overlaps in time:

* 7-Character Format XXXXX-XX
* 9-Character Format XX-XXXXX-XX

The latter was introduced in 1988 for Software Products and Services for new processors while Software Products and Services for processors already introduced remained in the old 7-Character Format.

== 7-Character Format XXXXX-XX ==

Samples:
*ZYA06-P3 MicroPDP-11 RX33 Formatter Kit
*

'''1st Letter = Type of Software''':
*Y - [[Computer Special Systems]] Software
*Z - Diagnostics
*Q - System and Application Software

'''2nd Letter = Processor Identifier''':
*0 - [[MicroVAX]]/[[VAXserver]] 3500 and 3600
*1 - MicroVAX/VAXserver 3500 and 3600/[[VAXstation]] 3200 and 3500
*2 - [[VAX 8700]] and [[VAX 8550]]
*3 - [[MicroVAX 2000]]
*4 - [[VAXstation II]]
*5 - [[VAX 8200]] and [[VAX 8250]]
*6 - [[VAXmate]]
*7 - [[VAX 8300]] and [[VAX 8350]]
*8 - [[VAXstation 2000]]
*9 - [[VAX 8500]] and [[VAX 8530]]
*A - [[Digital Classified Software]], USA
*B - [[Professional 300 Series]]
*C - [[VAX-11/725]] and [[VAX-11/730]]
*D - [[VAX-11/750]]
*E - [[VAX-11/780]], [[VAX-11/782]], and [[VAX-11/785]]
*F - [[PDP-8]], [[WPS-8]], [[DECmate I]]
*G - Digital Classified Software, Internal
*H - [[DECsystem 10]]
*I - Digital Classified Software, GIA
*J - [[PDP-11]] [[UNIBUS]]-based ([[RT-11]], [[ULTRIX-11]])
*K - [[VAX 8600]] and [[VAX 8650]]
*L - All Models
*M - [[VAX 8800]], [[VAX 8974]], and [[VAX 8978]]
*N - [[MicroVAX I]]
*P - PDP-11 ([[RSTS]])
*Q - [[VAXstation I]]
*R - PDP-11 ([[RSX-11M]]/[[RSX-11M-PLUS]])
*S - Software
*T - [[DECsystem 20]]
*U - Digital Classified Software, Europe
*V - [[Rainbow]]
*W - [[DECmate II]]
*X - Cross prod, and/or no support services
*Y - [[MicroPDP-11]] [[QBUS]]-based
*Z - [[MicroVAX II]]

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''<br>
:Exception: Digital Classified Software, 2nd letter = A, G, I, U

'''6th Letter = Product Type''':
*1 - Dispatch Subscription Service
*2 - Dispatch Subscription
*3 - Self-Maintenance Service
*4 - Source Updates Service
*5 - Startup Service Level I
*6 - Additional Telephone Support Center Contact
*7 - Startup Service Level II
*8 - Basic Service
*9 - DECsupport Service
*A - Single-use License, Binaries, Documentation, Warranty
*B - Startup Service Level III
*C - License and Key, no Support
*D - License only
*E - Source License and Distribution
*F - Source Distribution and Listings / Microfiche
*G - Documentation Only (-GZ)
*H - Distribution and Documentation
*I - Installation Service
*J - PPL - Periodic Payment License ([[VAXcluster]])
*K - Documentation Service
*L - Sources Update
*M - Location-use Source License, Microfiche List
*N - Source Distribution
*P - No License, Binaries only
*Q - Single-use License for VAXcluster Node
*R - No License, Binaries Documentation
*S - DECstart Service
*T - Update
*U - Single-Use License
*V - For Service Delivery Only
*W - Warranty Update / For Service Delivery Only
*X - Single-use Sources License, Sources and Binaries, Documents, Warranty
*Y - Single-use Sources License, Sources and Binaries, Documents
*Z - Defense Acquisition Regulation/NASA Marking, Maintenance Service

'''7th Letter = Software Medium''':
*2 - [[RX180]]
*3 - [[RX50]]
*4 - [[RC25]]
*5 - [[TK50]]
*6 - [[TK25]]
*7 - [[RX33]]
*8 - [[CDROM]]
*9 - ???
*A - [[Magnetic tape|9-Track Tape 6250 BPI]] / [[LINC tape]]
*B - [[Paper Tape]] / [[RX24]]
*C - [[DECtape]] / [[RX23]]
*D - [[Magnetic tape|9-Track Tape 800 BPI 600ft]]
*E - [[RK03]] / [[RK05]]
*F - [[Magnetic tape|7-Track Tape]]
*G - [[TU58]]
*H - [[RL02]]
*I - [[RX31]]
*J - [[RA60]]
*K - [[RP04]]
*L - [[RP06]]
*M - [[Magnetic tape|9-Track Tape 1600 BPI 2400ft]]
*N - [[TU60]]
*P - Cassette Tape ([[QIC]], [[DAT]], ...) / [[Magnetic tape|9 Track Magtape 800 BPI 2400ft]]
*Q - [[RL01]]
*R - [[Microfiche]]
*S - [[ROM]]
*T - [[RK06]]
*V - [[RK07]]
*W - Multimedia
*X - [[RX02]]
*Y - [[RX01]]
*Z - No Hardware Dependency / Paper

== 9-Character Format XX-XXXXX-XX ==

With the advent of VMS V5 and as new VAX processors were introduced, the Software Products and Services used the new Software Model Number, a 9-character format.

=== Cluster Licensing ===

'''1st and 2nd Letter'''
*QL - Licenses
*QT - SPS (Software Product Services)
*QA - Media and Documentation Kits
*QB - Packaged Software Components (License/Kit/SPS)

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''

'''6th Letter = CC (Country Code):'''
*A - American English
*E - British English
*G - German

'''8th and 9th Letter are dependent on the first two Letters'''

<tbd>

=== CPU Licensing ===

Samples:
*QL-056AF-AA

'''1st and 2nd Letter = Software Product Type'''
* QA - Software documentation, media, and other software kits
* QB - Packaged software components
* QC - Software subassemblies
* QL - Software licenses (DEC processor tier, and platform licenses)
* QM - Software licenses (PC & standalone third-party license agreements)
* QP - Packaged software licenses
* QQ - Country information components
* QR - Assigned software uses
* QS - Professional services project and consulting services
* QT - Software product services
* QU - Software product services
* QW - Cross-functional service packages (CFSP)
* QX - Diagnostic/maintenance tools licenses
* QY - Diagnostic/maintenance tools services
* QZ - Diagnostic/maintenance tools documentation, media, and other hardware information kits
* Q2 - Software application products: license, media & documentation, and SPS
* Q3 - Software application products: license, media & documentation, and SPS

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''

'''6th Letter = Unknown (usually "A" or "G")'''

'''7th Letter = CPU Code:'''
*B - MicroVAX 3500, 3600
*C - VAXstation 3200, 3500, 8000
*D - VAX 8800, 6240, 8820
*E - VAX 8550, 8700, 8810
*F - VAX 8600, 8650
*G - VAX 8530
*H - VAX 8300, 8350
*J - VAX 8200, 11/782
*K - VAX-11/780, 11/785
*L - VAX-11/750
*M - VAX-11/730, 11/725
*N - MicroVAX II
*P - MicroVAX 2000
*Q - VAXstation II
*R - VAXstation 2000
*S - MicroVAX 3300, 3400
*U - VAX 8830, 8842
*V - VAX 8840
*2 - VAX 6210
*3 - VAX 6220
*4 - VAX 6230

'''8th and 9th Letter = Unknown (usually "AA")'''

== External References ==

*AA-5074O-RK System Software Information
*IAS 3.4A SPD
*EE-26108-68-84 DIGITAL Microcomponents Products U.S. Price List October-December 1984
*EE-18587-04-80 PDP-11, VAX-11 Price List April - September 1980
*ED PDP Systems and Options Catalog 1988

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

PDP-11/73

2025-10-31T16:40:30Z

Vaxorcist: /* OS */ Fixed typos and added some more operating systems

[[Image:mpdp73.jpg|right|thumb|200px|PDP-11/73]]
The '''PDP-11/73''' is a high-end [[QBUS]] [[PDP-11]] system. Confusingly, the [[Central Processing Unit|CPU]] board is the [[KDJ11-B]] (M8190), the same as the [[PDP-11/83]] - no [[Digital Equipment Corporation|DEC]] '-11/xx' system seems to use the earlier [[KDJ11-A]] (M8192). (The ''Microcomputer Products Handbook'' does refer to the KDJ11-A as the "LSI-11/73 microcomputer", however.)

The difference between the /73 and /83 is that the latter uses [[Private Memory Interconnect|PMI]] [[main memory]], instead of the QBUS memory of the -11/73.

== OS ==
The PDP-11/73 and PDP-11/83 Micro PDPs ran [[RSX-11M]], [[RSX-11M-Plus]], [[Micro/RSX]], [[ULTRIX-11]], and BSD

== hampage.hu ==
Quoting:
<i>
Introduced in 1984. Successor of the [[PDP-11/23]]. At that time the components were VLSI, and these PDP-11's were marketed as MicroPDP's (this has in fact begun with the PDP-11/23). The PDP-11/73 had a 15MHz [[J-11 chip set]]-based CPU with 22-bit memory management for the 4MB RAM max. Just to make life more complicated, 18 MHz PDP-11/83 CPU boards can also be found in PDP-11/73 systems, as a PDP-11/83 CPU (M8190-A[DE]) with QBUS memory (instead of the PMI memory used in those systems) is called a PDP-/73...

There was no UNIBUS equivalent.</i>(Incorrect. The [[PDP-11/84]] shared the same CPU, and had a [[UNIBUS]].)<i>

The J-11 was manufactured by Harris Semiconductors, and it hasn't been fully completed, it lacked the WCS and CIS options.

A very popular enclosure is displayed to the right: this was the [[BA23 Enclosure|BA23]] standing tower configuration, that had place for a 8x4 backplane, an [[RX50]] floppy or [[TK50]] streaming tape drive and an RDxx hard disk. The BA23 could also be rack-mounted.
</i>
[[Image:pdp11-73.jpg|150px|thumb|left|PDP-11/73 in a different style of box]]

<br clear=all>
{{semi-stub}}

==Further reading==

* ''MicroPDP-11 Systems Owner's Manual'' (EK-MIC11-OM) - This, and the three related MicroPDP-11 manuals below, are not specific to the PDP-11/73, but contain a great deal of material which applies to the MicroPDP-11/73

==External links==

* [http://bitsavers.org/pdf/dec/pdp11/microPDP11/AZ-FI13A-MC_MicroPDP11_Systems_Owners_Manual_Jun86.pdf MicroPDP-11 Systems Owner's Manual] (AZ-FI13A-MC)
* [http://bitsavers.org/pdf/dec/pdp11/microPDP11/EK-MIC11-TM-002_MicroPDP11_Systems_Technical_Manual_Sep85.pdf MicroPDP-11 Systems Technical Manual] (EK-MIC11-TM-002)
* [https://vt100.net/mirror/antonio/ek-mic11-sg-001.pdf MicroPDP-11 Systems Maintenance Guide] (EK-MIC11-SG-001)
* [http://bitsavers.org/pdf/dec/pdp11/handbooks/PDP-11_Systems_Handbook_1987.pdf PDP-11 Systems Handbook]
* [http://bitsavers.informatik.uni-stuttgart.de/pdf/dec/pdp11/handbooks/EB-24944-18_Micro_PDP-11_Handbook_1983-84.pdf PDP-11 Micro/PDP-11 Handbook 1983-84] (EB-24944-18)

{{PDP-11}}

[[Category: QBUS PDP-11s]]

KM11-A Maintenance Set

2025-10-24T07:28:39Z

Vaxorcist: /* Overlays */ Fixed typo

The '''KM11-A Maintenance Set''' (also variously called the '''KM11-A Maintenance Panel''', '''KM11-A Maintenance Console''' and '''KM11-A Maintenance Cards''' in some later [[Digital Equipment Corporation|DEC]] manuals) is a device used to perform maintenance activities on early [[PDP-11]] [[Central Processing Unit|CPUs]] and some early PDP-11 [[peripheral]]s.

As produced by DEC, a KM11 consists of a W131 Maintenance Indicator Module plugged into a W130 Maintenance Connector Module; later a W131 and a W133 Driver Module. The W131 contains an array of 28 lights, three double-throw switches, and a single spring-loaded double-throw switch.

==Overlays==

A variety of overlays, specific to a CPU or peripheral, indicate the meaning of the lights, and the function of the switches, when used with that CPU or peripheral.

The CPUs which can use the KM11-A, and for which overlays exist, are:

* [[KA11 CPU|KA11]]
* [[KB11]] - all models
** [[FP11-B Floating-Point Processor|FP11-B]]/[[FP11-C Floating-Point Processor|FP11-C]] (same inlay as CPU)
* [[KD11-A CPU|KD11-A]]
** [[KT11-D Memory Management|KT11-D]], [[KE11-E Extended Instruction Set|KE11-E]]/[[KE11-F Floating Instruction Set|KE11-F]]
* [[KD11-B CPU|KD11-B]] (2 inlays)

Devices which support the KM11-A, and for which overays exist, are:

* [[RK11-C disk controller|RK11-C]] (2 inlays)
* [[RK11 disk controller#RK11-D|RK11-D]]
* [[TM11 magtape controller|TM11]]
* [[RX01/02 floppy drive|RX01]]

There is also reportedly an overlay for the [[KE11-A Extended Arithmetic Element‎]], but although several KE11-A documents refer to it, no image of it can be found.

==Replicas==

[[Image:ShiresoftKM11.jpg|250px|right|thumb|A replica KM11 from Shiresoft]]

The original DEC KM11-A's are incredibly scarce, but they are also a very powerful diagnostic tool. So, there have been several different projects to produce replicas; see the links below.

==External links==

* [http://www.bitsavers.org/pdf/dec/pdp11/1140/PDP-1140_System_Engr_Drawings_Rev_P_Jun74.pdf PDP-11/40 system engineering drawings] - the KM11 is covered on pp. 123-125 
* [https://www.pdp-11.nl/testtools/km11-info.html Maintenance Board Set] - DEC's original
* Replacements
** [http://www.shiresoft.com/products/km11/KM11%20Replica.html KM11 Replica] - Guy Sotomayor
** [http://www.ubanproductions.com/museum.html Replacement KM11 maintenance board] - Tom Uban
** [http://www.ubanproductions.com/km11x.html How to build a clone of the DEC KM11 maintenance module] - Tony Duell
** [http://retrocmp.com/tools/dec-km11-maintenance-panel DEC KM11] - Jörg Hoppe

[[Category: PDP-11s]]

VAX-11/725

2025-10-19T09:58:46Z

Vaxorcist: Reference to RC25 added

{{InfoboxVAX-Data
| name = VAX-11/725
| Announcement = October 1983
| Codename = Low Cost Nebula
| OS-support-VMS = VMS V3.5 to VMS V5.1
| CPU-module = KA730
| Num-proc = 1
| CPU-technology = Bipolar Schottky
| CPU-cycle = 270ns [[#ref_1|[1]]]
| Instruction-buffer = 4 bytes [[#ref_1|[1]]]
| Translation-buffer = 128 entries [[#ref_1|[1]]]
| WCS = 16K 24-bit words [[#ref_1|[1]]]
| Compatibility-mode = Yes [[#ref_1|[1]]]
| Console-processor = 8085A [[#ref_1|[1]]]
| Console-device = TU58
| Minimum-memory = 1MB
| Maximum-memory = 3MB
| Physical-address-lines = 24 [[#ref_1|[1]]]
| Memory-checking = 7-bit ECC/longword [[#ref_1|[1]]]
| Memory-cycle = 810ns [[#ref_1|[1]]]
| BUS-UNIBUS = 1 @ 1.5MB/s [[#ref_1|[1]]]
| LAN-support = optional
| VUPs = 0.3
}}
The '''VAX-11/725''' is a [[VAX-11/730]] in a smaller enclosure; like the -11/730, it uses a [[UNIBUS]] for its [[input/output|I/O]] [[bus]].

It uses the [[RC25]] dual disk drive as its load and system disks.

{{stub}}

==References==

<div id="ref_1">[1] VAX Hardware Handbook Volume 1 - 1986. </div>
<div id="ref_2">[2] Systems & Options Catalog. European Edition. Spring 1990. </div>

==External links==

* [http://www.bitsavers.org/pdf/dec/vax/handbook/VAX_Hardware_Handbook_Volume_1_1986.pdf VAX Hardware Handbook Volume 1] - the VAX-11/725 is described on pages 1-5–1-8 (pp. 20-23 of the PDF) and covered in detail in Chapter 3 (pp. 132-152)
* [http://www.bitsavers.org/www.computer.museum.uq.edu.au/pdf/AA-M546C-TE%20VAX-11-725%20and%20VAX-11-730%20Software%20Installation%20Guide.pdf VAX-11/725 and VAX-11/730 Software Installation Guide] (AA-M546C-TE)
* [http://www.computinghistory.org.uk/det/42611/VAX-11-725/ VAX-11/725] - image of marketing brochure

{{Nav VAX}}

[[Category: VAX Minicomputers]]
[[Category: VAX-11/7xx Systems]]

Template:Nav VAX

2025-10-19T09:48:20Z

Vaxorcist: VAX-11/725 added

{{PartiallyCollapsibleNavBox
| templateName = Nav VAX
| title = [[VAX]] Computers and Operating Systems
| body = <b>VAX-11/7xx</b> (including VAX 86x0) - [[VAX-11/780]] • [[VAX-11/785]] • [[VAX-11/750]] • [[VAX-11/730]] • [[VAX-11/725]] • [[VAX 8600]] • [[VAX 8650]]

<b>VAX 8000 series</b> (excluding VAX 86x0, above) - [[VAX 82xx/83xx series]] • [[VAX 85xx, 87xx, and 88xx systems|VAX 85xx/87xx/88xx series]]

<b>MicroVAXen</b> (many types also come in [[VAXserver]] and [[VAXstation]] models) - [[MicroVAX I]] • [[MicroVAX II]] <br> [[MicroVAX 2000]] • [[MicroVAX 3100 series|MicroVAX 3100]] • [[MicroVAX 3300/3400]] • [[MicroVAX 3500/3600]] • [[MicroVAX 3800/3900]]

<b>VAXstation Series</b> - [[VAXstation I]] • [[VAXstation II]] <br> [[VAXstation 3100 series|VAXstation 3100]] • [[VAXstation 3200/3500]] • [[VAXstation 3520/3540]] • [[VAXstation 4000 series|VAXstation 4000]] • [[VAXstation 8000]]

<b>Late Model VAXen</b> - [[VAX 4000 series]] • [[VAX 6000 series]] • [[VAX 7000 series]] • [[VAX 9000 series]] • [[VAX 10000 series]]

| cbody = <b>Special Purpose VAXen</b> - [[VAXft series]] • [[rtVAX series]] • [[Infoserver series]]

<b>Clones</b> - [[CM 1700]] • [[TPA-11/580]]

<b>Operating Systems:</b> [[VMS]] • [[VAXELN]] • [[ULTRIX]] • [[BSD on VAX|BSD UNIX]]
}}

Digital Data Communications Message Protocol

2025-10-16T08:01:22Z

Vaxorcist: /* Synchronous DDCMP Controller Capabilities */ Correction: No DDCMP support for DPV11 in VMS

The '''Digital Data Communications Message Protocol''' ('''DDCMP''') is a [[byte]]-oriented [[data communication]] [[protocol]] for use over [[full-duplex]] and [[half-duplex]] point-to-point and multi-drop links; principally using using [[synchronous serial line|synchronous]] or [[asynchronous serial line]]s, although other communication channels (e.g. [[Parallel interface|parallel lines]] using the [[PCL11]] interface under [[RSX-11M]]) were also supported. It used [[cyclic redundancy check|CRCs]] to allow transmission errors to be detected; [[sequence number]]s allow detection of completely lost messages. [[Retransmission]] is used to correct both.

It was originally designed by [[Digital Equipment Corporation|DEC]] for the [[DECnet]] Phase I network [[protocol suite]], in 1974. It was retained in later versions of DECnet, with modifications and extensions.

From 1983 onwards [[serial line]]s (using DDCMP) were step by step superseded by [[Ethernet]], which was superior in terms of speed and flexibility. DDCMP is nevertheless retained in current [[VMS]] DECnet versions, mainly because DDCMP was used still for [[wide area network]]s.

DDCMP usually carried DECnet traffic, one known exception is a late VAX version of the [[ULTRIX]] operating system:

''The [[DMV11]] is supported using TCP/IP and DECnet over full and half duplex point-to-point DDCMP sync lines.''

says: "The ULTRIX Operating System, Version 4.5 [[Software Product Description]] 26.40.32"

==Synchronous DDCMP==

There are Synchronous DDCMP controllers for several buses:

* [[UNIBUS]]
* [[QBUS]]
* [[VAXBI]]

===Synchronous DDCMP Controller Capabilities===
{| class="wikitable" style="text-align:center;"
! Bus !! Controller !! Point-to-Point V3.2 !! Point-to-Point V4.0 !! Tributary !! Control !! VMS Support
|-
| UNIBUS || [[DUP11]] || colspan="2" | X (supported DDCMP versions yet unknown) || - || - || -
|-
| UNIBUS || [[DMC11]] || X || - || - || - || X
|-
| UNIBUS || [[DMR11]] || X || X || - || - || X
|-
| UNIBUS || [[DMP11]] || X || X || X || X || X
|-
| UNIBUS || [[DMF32]] || X || X || X || - || X
|-
| VAXBI || [[DMB32]] || X || X || X || - || X
|-
| VAXBI || [[DSB32]] || colspan="2" | X (supported DDCMP versions yet unknown) || - || - || X
|-
| QBUS || [[DPV11]] || colspan="2" | X (supported DDCMP versions yet unknown) || - || - || -
|-
| QBUS || [[DMV11]] || X || X || X || X || X
|-
| QBUS || [[DSV11]] || ? || X || - || - || using: VAX Wide Area Network Device Drivers Software
|}

===Synchronous DDCMP Configurations===
There are two basic kinds of synchronous DDMCP configurations:
* Point-to-point
* Multipoint

====Synchronous Point-to-Point DDCMP====
----
Point-to-point DDCMP connects exactly two DDCMP devices, either:
* A DMC11 and another arbitrary DDCMP device, using the older version (3.2) of DDCMP
or:
* Two arbitrary DDCMP devices (except for DMC11), using the newer version (4.0) of DDCMP

====Synchronous Multipoint DDCMP====
----
With Multipoint DDCMP, exactly one Multipoint controller (e.g. a DMP11) acts as the control station of a DDCMP multipoint group.

Multiple other DDCMP Tributary controllers (e.g. DMP11, DMF32) are all connected to the control station.

All DDCMP controllers connected in this way constitute a DDCMP multipoint group.

'''Multidrop''' is an established synonym for '''Multipoint'''.

====Synchronous DDCMP Line Protocols====

As of DDCMP version V3.1 there was only '''DDCMP POINT'''; from version 4.0 onwards all variants described below were available.

{| class="wikitable"
! Protocol !! Description
|-
| DDCMP CONTROL || Specifies the line as a multipoint control Station. You can set multiple circuits for CONTROL lines. Each circuit must have a unique physical tributary address.
|-
| DDCMP DMC || Specifies that the line is in DMC emulator mode. DMC is similar to DDCMP POINT protocol, except that DMC uses an older version of DDCMP (Version 3.2). This protocol should be set for the local line when the remote line is a DMC.
|-
| DDCMP POINT || Specifies the line as one end of a point-to-point DDCMP connection. You may specify only one circuit per POINT line.
|-
| DDCMP TRIBUTARY || Specifies that the line is a multipoint tributary end of a DDCMP multipoint group. You may specify only one circuit per TRIBUTARY line.
|}

==Asynchronous DDCMP==
Asynchronous DDCMP uses simple asynchronous serial lines (such as [[DZ11]] or [[DLV11]]), which are mosty used for terminal communication.

This led to the joke calling it '''"Poor Man's DECnet"''', because asynchronous serial line controllers were much cheaper then synchronous serial lines or Ethernet controllers, and many computers already had a spare one available.

The drawback of Asynchronous DDCMP is lower speed and less effectivity.

DECnet-RSX (or DECnet-11M as it was called in the beginning) supported Asynchronous DDCMP at least from Version 2.0 (1979) onwards (see SPD), maybe even right from the start (Infos on DECnet-11M V1.x welcome!).

DECnet/VMS only supported asynchronous DDCMP from version 4.0 onwards, i.e., 1984 at the earliest; it was improved with VMS V4.2 in 1985)

==See also==

* [[Installing and Testing Asynchronous DECnet over DDCMP between two MicroVAX Computers]]

==External links==

* [http://decnet.ipv7.net/docs/dundas/aa-d599a-tc.pdf 'DDCMP Specification Version 4.0'], AA-D599A-TC (1 March 1978)
* [https://www.geeksforgeeks.org/digital-data-communications-message-protocol-ddcmp/ Digital Data Communications Message Protocol (DDCMP)] - Contains a good, detailed description of failure modes

{{semi-stub}}

[[Category: Serial Lines]]
[[Category: Network Protocols]]
[[Category: DECnet]]

Digital Data Communications Message Protocol

2025-10-16T06:42:16Z

Vaxorcist: Fixed typo

The '''Digital Data Communications Message Protocol''' ('''DDCMP''') is a [[byte]]-oriented [[data communication]] [[protocol]] for use over [[full-duplex]] and [[half-duplex]] point-to-point and multi-drop links; principally using using [[synchronous serial line|synchronous]] or [[asynchronous serial line]]s, although other communication channels (e.g. [[Parallel interface|parallel lines]] using the [[PCL11]] interface under [[RSX-11M]]) were also supported. It used [[cyclic redundancy check|CRCs]] to allow transmission errors to be detected; [[sequence number]]s allow detection of completely lost messages. [[Retransmission]] is used to correct both.

It was originally designed by [[Digital Equipment Corporation|DEC]] for the [[DECnet]] Phase I network [[protocol suite]], in 1974. It was retained in later versions of DECnet, with modifications and extensions.

From 1983 onwards [[serial line]]s (using DDCMP) were step by step superseded by [[Ethernet]], which was superior in terms of speed and flexibility. DDCMP is nevertheless retained in current [[VMS]] DECnet versions, mainly because DDCMP was used still for [[wide area network]]s.

DDCMP usually carried DECnet traffic, one known exception is a late VAX version of the [[ULTRIX]] operating system:

''The [[DMV11]] is supported using TCP/IP and DECnet over full and half duplex point-to-point DDCMP sync lines.''

says: "The ULTRIX Operating System, Version 4.5 [[Software Product Description]] 26.40.32"

==Synchronous DDCMP==

There are Synchronous DDCMP controllers for several buses:

* [[UNIBUS]]
* [[QBUS]]
* [[VAXBI]]

===Synchronous DDCMP Controller Capabilities===
{| class="wikitable" style="text-align:center;"
! Bus !! Controller !! Point-to-Point V3.2 !! Point-to-Point V4.0 !! Tributary !! Control !! VMS Support
|-
| UNIBUS || [[DUP11]] || colspan="2" | X (supported DDCMP versions yet unknown) || - || - || -
|-
| UNIBUS || [[DMC11]] || X || - || - || - || X
|-
| UNIBUS || [[DMR11]] || X || X || - || - || X
|-
| UNIBUS || [[DMP11]] || X || X || X || X || X
|-
| UNIBUS || [[DMF32]] || X || X || X || - || X
|-
| VAXBI || [[DMB32]] || X || X || X || - || X
|-
| VAXBI || [[DSB32]] || colspan="2" | X (supported DDCMP versions yet unknown) || - || - || X
|-
| QBUS || [[DPV11]] || colspan="2" | X (supported DDCMP versions yet unknown) || - || - || using: VAX Wide Area Network Device Drivers Software
|-
| QBUS || [[DMV11]] || X || X || X || X || X
|-
| QBUS || [[DSV11]] || ? || X || - || - || using: VAX Wide Area Network Device Drivers Software
|}

===Synchronous DDCMP Configurations===
There are two basic kinds of synchronous DDMCP configurations:
* Point-to-point
* Multipoint

====Synchronous Point-to-Point DDCMP====
----
Point-to-point DDCMP connects exactly two DDCMP devices, either:
* A DMC11 and another arbitrary DDCMP device, using the older version (3.2) of DDCMP
or:
* Two arbitrary DDCMP devices (except for DMC11), using the newer version (4.0) of DDCMP

====Synchronous Multipoint DDCMP====
----
With Multipoint DDCMP, exactly one Multipoint controller (e.g. a DMP11) acts as the control station of a DDCMP multipoint group.

Multiple other DDCMP Tributary controllers (e.g. DMP11, DMF32) are all connected to the control station.

All DDCMP controllers connected in this way constitute a DDCMP multipoint group.

'''Multidrop''' is an established synonym for '''Multipoint'''.

====Synchronous DDCMP Line Protocols====

As of DDCMP version V3.1 there was only '''DDCMP POINT'''; from version 4.0 onwards all variants described below were available.

{| class="wikitable"
! Protocol !! Description
|-
| DDCMP CONTROL || Specifies the line as a multipoint control Station. You can set multiple circuits for CONTROL lines. Each circuit must have a unique physical tributary address.
|-
| DDCMP DMC || Specifies that the line is in DMC emulator mode. DMC is similar to DDCMP POINT protocol, except that DMC uses an older version of DDCMP (Version 3.2). This protocol should be set for the local line when the remote line is a DMC.
|-
| DDCMP POINT || Specifies the line as one end of a point-to-point DDCMP connection. You may specify only one circuit per POINT line.
|-
| DDCMP TRIBUTARY || Specifies that the line is a multipoint tributary end of a DDCMP multipoint group. You may specify only one circuit per TRIBUTARY line.
|}

==Asynchronous DDCMP==
Asynchronous DDCMP uses simple asynchronous serial lines (such as [[DZ11]] or [[DLV11]]), which are mosty used for terminal communication.

This led to the joke calling it '''"Poor Man's DECnet"''', because asynchronous serial line controllers were much cheaper then synchronous serial lines or Ethernet controllers, and many computers already had a spare one available.

The drawback of Asynchronous DDCMP is lower speed and less effectivity.

DECnet-RSX (or DECnet-11M as it was called in the beginning) supported Asynchronous DDCMP at least from Version 2.0 (1979) onwards (see SPD), maybe even right from the start (Infos on DECnet-11M V1.x welcome!).

DECnet/VMS only supported asynchronous DDCMP from version 4.0 onwards, i.e., 1984 at the earliest; it was improved with VMS V4.2 in 1985)

==See also==

* [[Installing and Testing Asynchronous DECnet over DDCMP between two MicroVAX Computers]]

==External links==

* [http://decnet.ipv7.net/docs/dundas/aa-d599a-tc.pdf 'DDCMP Specification Version 4.0'], AA-D599A-TC (1 March 1978)
* [https://www.geeksforgeeks.org/digital-data-communications-message-protocol-ddcmp/ Digital Data Communications Message Protocol (DDCMP)] - Contains a good, detailed description of failure modes

{{semi-stub}}

[[Category: Serial Lines]]
[[Category: Network Protocols]]
[[Category: DECnet]]

DEC Software-related Order Codes

2025-10-13T12:20:51Z

Vaxorcist: /* Cluster Licensing */ another update ...

DEC Software Media, Software License, Software Service, and Software Manual Order Codes

There are two formats whose use overlaps in time:

* 7-Character Format XXXXX-XX
* 9-Character Format XX-XXXXX-XX

The latter was introduced in 1988 for Software Products and Services for new processors while Software Products and Services for processors already introduced remained in the old 7-Character Format.

== 7-Character Format XXXXX-XX ==

Samples:
*ZYA06-P3 MicroPDP-11 RX33 Formatter Kit
*

'''1st Letter = Type of Software''':
*Y - [[Computer Special Systems]] Software
*Z - Diagnostics
*Q - System and Application Software

'''2nd Letter = Processor Identifier''':
*0 - [[MicroVAX]]/[[VAXserver]] 3500 and 3600
*1 - MicroVAX/VAXserver 3500 and 3600/[[VAXstation]] 3200 and 3500
*2 - [[VAX 8700]] and [[VAX 8550]]
*3 - [[MicroVAX 2000]]
*4 - [[VAXstation II]]
*5 - [[VAX 8200]] and [[VAX 8250]]
*6 - [[VAXmate]]
*7 - [[VAX 8300]] and [[VAX 8350]]
*8 - [[VAXstation 2000]]
*9 - [[VAX 8500]] and [[VAX 8530]]
*A - [[Digital Classified Software]], USA
*B - [[Professional 300 Series]]
*C - [[VAX-11/725]] and [[VAX-11/730]]
*D - [[VAX-11/750]]
*E - [[VAX-11/780]], [[VAX-11/782]], and [[VAX-11/785]]
*F - [[PDP-8]], [[WPS-8]], [[DECmate I]]
*G - Digital Classified Software, Internal
*H - [[DECsystem 10]]
*I - Digital Classified Software, GIA
*J - [[PDP-11]] [[UNIBUS]]-based ([[RT-11]], [[ULTRIX-11]])
*K - [[VAX 8600]] and [[VAX 8650]]
*L - All Models
*M - [[VAX 8800]], [[VAX 8974]], and [[VAX 8978]]
*N - [[MicroVAX I]]
*P - PDP-11 ([[RSTS]])
*Q - [[VAXstation I]]
*R - PDP-11 ([[RSX-11M]]/[[RSX-11M-PLUS]])
*S - Software
*T - [[DECsystem 20]]
*U - Digital Classified Software, Europe
*V - [[Rainbow]]
*W - [[DECmate II]]
*X - Cross prod, and/or no support services
*Y - [[MicroPDP-11]] [[QBUS]]-based
*Z - [[MicroVAX II]]

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''<br>
:Exception: Digital Classified Software, 2nd letter = A, G, I, U

'''6th Letter = Product Type''':
*1 - Dispatch Subscription Service
*2 - Dispatch Subscription
*3 - Self-Maintenance Service
*4 - Source Updates Service
*5 - Startup Service Level I
*6 - Additional Telephone Support Center Contact
*7 - Startup Service Level II
*8 - Basic Service
*9 - DECsupport Service
*A - Single-use License, Binaries, Documentation, Warranty
*B - Startup Service Level III
*C - License and Key, no Support
*D - License only
*E - Source License and Distribution
*F - Source Distribution and Listings / Microfiche
*G - Documentation Only (-GZ)
*H - Distribution and Documentation
*I - Installation Service
*J - PPL - Periodic Payment License ([[VAXcluster]])
*K - Documentation Service
*L - Sources Update
*M - Location-use Source License, Microfiche List
*N - Source Distribution
*P - No License, Binaries only
*Q - Single-use License for VAXcluster Node
*R - No License, Binaries Documentation
*S - DECstart Service
*T - Update
*U - Single-Use License
*V - For Service Delivery Only
*W - Warranty Update / For Service Delivery Only
*X - Single-use Sources License, Sources and Binaries, Documents, Warranty
*Y - Single-use Sources License, Sources and Binaries, Documents
*Z - Defense Acquisition Regulation/NASA Marking, Maintenance Service

'''7th Letter = Software Medium''':
*2 - [[RX180]]
*3 - [[RX50]]
*4 - [[RC25]]
*5 - [[TK50]]
*6 - [[TK25]]
*7 - [[RX33]]
*8 - [[CDROM]]
*A - [[Magnetic tape|9-Track Tape 6250 BPI]] / [[LINC tape]]
*B - [[Paper Tape]] / [[RX24]]
*C - [[DECtape]] / [[RX23]]
*D - [[Magnetic tape|9-Track Tape 800 BPI 600ft]]
*E - [[RK03]] / [[RK05]]
*F - [[Magnetic tape|7-Track Tape]]
*G - [[TU58]]
*H - [[RL02]]
*I - [[RX31]]
*J - [[RA60]]
*K - [[RP04]]
*L - [[RP06]]
*M - [[Magnetic tape|9-Track Tape 1600 BPI 2400ft]]
*N - [[TU60]]
*P - Cassette Tape ([[QIC]], [[DAT]], ...) / [[Magnetic tape|9 Track Magtape 800 BPI 2400ft]]
*Q - [[RL01]]
*R - [[Microfiche]]
*S - [[ROM]]
*T - [[RK06]]
*V - [[RK07]]
*W - Multimedia
*X - [[RX02]]
*Y - [[RX01]]
*Z - No Hardware Dependency / Paper

== 9-Character Format XX-XXXXX-XX ==

With the advent of VMS V5 and as new VAX processors were introduced, the Software Products and Services used the new Software Model Number, a 9-character format.

=== Cluster Licensing ===

'''1st and 2nd Letter'''
*QL - Licenses
*QT - SPS (Software Product Services)
*QA - Media and Documentation Kits
*QB - Packaged Software Components (License/Kit/SPS)

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''

'''6th Letter = CC (Country Code):'''
*A - American English
*E - British English
*G - German

'''8th and 9th Letter are dependent on the first two Letters'''

<tbd>

=== CPU Licensing ===

Samples:
*QL-056AF-AA

'''1st and 2nd Letter = Software Product Type'''
* QA - Software documentation, media, and other software kits
* QB - Packaged software components
* QC - Software subassemblies
* QL - Software licenses (DEC processor tier, and platform licenses)
* QM - Software licenses (PC & standalone third-party license agreements)
* QP - Packaged software licenses
* QQ - Country information components
* QR - Assigned software uses
* QS - Professional services project and consulting services
* QT - Software product services
* QU - Software product services
* QW - Cross-functional service packages (CFSP)
* QX - Diagnostic/maintenance tools licenses
* QY - Diagnostic/maintenance tools services
* QZ - Diagnostic/maintenance tools documentation, media, and other hardware information kits
* Q2 - Software application products: license, media & documentation, and SPS
* Q3 - Software application products: license, media & documentation, and SPS

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''

'''6th Letter = Unknown (usually "A" or "G")'''

'''7th Letter = CPU Code:'''
*B - MicroVAX 3500, 3600
*C - VAXstation 3200, 3500, 8000
*D - VAX 8800, 6240, 8820
*E - VAX 8550, 8700, 8810
*F - VAX 8600, 8650
*G - VAX 8530
*H - VAX 8300, 8350
*J - VAX 8200, 11/782
*K - VAX-11/780, 11/785
*L - VAX-11/750
*M - VAX-11/730, 11/725
*N - MicroVAX II
*P - MicroVAX 2000
*Q - VAXstation II
*R - VAXstation 2000
*S - MicroVAX 3300, 3400
*U - VAX 8830, 8842
*V - VAX 8840
*2 - VAX 6210
*3 - VAX 6220
*4 - VAX 6230

'''8th and 9th Letter = Unknown (usually "AA")'''

== External References ==

*AA-5074O-RK System Software Information
*IAS 3.4A SPD
*EE-26108-68-84 DIGITAL Microcomponents Products U.S. Price List October-December 1984
*EE-18587-04-80 PDP-11, VAX-11 Price List April - September 1980
*ED PDP Systems and Options Catalog 1988

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

DEC Software-related Order Codes

2025-10-13T10:31:29Z

Vaxorcist: /* Cluster Licensing */ SPS = Software Product Services

DEC Software Media, Software License, Software Service, and Software Manual Order Codes

There are two formats whose use overlaps in time:

* 7-Character Format XXXXX-XX
* 9-Character Format XX-XXXXX-XX

The latter was introduced in 1988 for Software Products and Services for new processors while Software Products and Services for processors already introduced remained in the old 7-Character Format.

== 7-Character Format XXXXX-XX ==

Samples:
*ZYA06-P3 MicroPDP-11 RX33 Formatter Kit
*

'''1st Letter = Type of Software''':
*Y - [[Computer Special Systems]] Software
*Z - Diagnostics
*Q - System and Application Software

'''2nd Letter = Processor Identifier''':
*0 - [[MicroVAX]]/[[VAXserver]] 3500 and 3600
*1 - MicroVAX/VAXserver 3500 and 3600/[[VAXstation]] 3200 and 3500
*2 - [[VAX 8700]] and [[VAX 8550]]
*3 - [[MicroVAX 2000]]
*4 - [[VAXstation II]]
*5 - [[VAX 8200]] and [[VAX 8250]]
*6 - [[VAXmate]]
*7 - [[VAX 8300]] and [[VAX 8350]]
*8 - [[VAXstation 2000]]
*9 - [[VAX 8500]] and [[VAX 8530]]
*A - [[Digital Classified Software]], USA
*B - [[Professional 300 Series]]
*C - [[VAX-11/725]] and [[VAX-11/730]]
*D - [[VAX-11/750]]
*E - [[VAX-11/780]], [[VAX-11/782]], and [[VAX-11/785]]
*F - [[PDP-8]], [[WPS-8]], [[DECmate I]]
*G - Digital Classified Software, Internal
*H - [[DECsystem 10]]
*I - Digital Classified Software, GIA
*J - [[PDP-11]] [[UNIBUS]]-based ([[RT-11]], [[ULTRIX-11]])
*K - [[VAX 8600]] and [[VAX 8650]]
*L - All Models
*M - [[VAX 8800]], [[VAX 8974]], and [[VAX 8978]]
*N - [[MicroVAX I]]
*P - PDP-11 ([[RSTS]])
*Q - [[VAXstation I]]
*R - PDP-11 ([[RSX-11M]]/[[RSX-11M-PLUS]])
*S - Software
*T - [[DECsystem 20]]
*U - Digital Classified Software, Europe
*V - [[Rainbow]]
*W - [[DECmate II]]
*X - Cross prod, and/or no support services
*Y - [[MicroPDP-11]] [[QBUS]]-based
*Z - [[MicroVAX II]]

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''<br>
:Exception: Digital Classified Software, 2nd letter = A, G, I, U

'''6th Letter = Product Type''':
*1 - Dispatch Subscription Service
*2 - Dispatch Subscription
*3 - Self-Maintenance Service
*4 - Source Updates Service
*5 - Startup Service Level I
*6 - Additional Telephone Support Center Contact
*7 - Startup Service Level II
*8 - Basic Service
*9 - DECsupport Service
*A - Single-use License, Binaries, Documentation, Warranty
*B - Startup Service Level III
*C - License and Key, no Support
*D - License only
*E - Source License and Distribution
*F - Source Distribution and Listings / Microfiche
*G - Documentation Only (-GZ)
*H - Distribution and Documentation
*I - Installation Service
*J - PPL - Periodic Payment License ([[VAXcluster]])
*K - Documentation Service
*L - Sources Update
*M - Location-use Source License, Microfiche List
*N - Source Distribution
*P - No License, Binaries only
*Q - Single-use License for VAXcluster Node
*R - No License, Binaries Documentation
*S - DECstart Service
*T - Update
*U - Single-Use License
*V - For Service Delivery Only
*W - Warranty Update / For Service Delivery Only
*X - Single-use Sources License, Sources and Binaries, Documents, Warranty
*Y - Single-use Sources License, Sources and Binaries, Documents
*Z - Defense Acquisition Regulation/NASA Marking, Maintenance Service

'''7th Letter = Software Medium''':
*2 - [[RX180]]
*3 - [[RX50]]
*4 - [[RC25]]
*5 - [[TK50]]
*6 - [[TK25]]
*7 - [[RX33]]
*8 - [[CDROM]]
*A - [[Magnetic tape|9-Track Tape 6250 BPI]] / [[LINC tape]]
*B - [[Paper Tape]] / [[RX24]]
*C - [[DECtape]] / [[RX23]]
*D - [[Magnetic tape|9-Track Tape 800 BPI 600ft]]
*E - [[RK03]] / [[RK05]]
*F - [[Magnetic tape|7-Track Tape]]
*G - [[TU58]]
*H - [[RL02]]
*I - [[RX31]]
*J - [[RA60]]
*K - [[RP04]]
*L - [[RP06]]
*M - [[Magnetic tape|9-Track Tape 1600 BPI 2400ft]]
*N - [[TU60]]
*P - Cassette Tape ([[QIC]], [[DAT]], ...) / [[Magnetic tape|9 Track Magtape 800 BPI 2400ft]]
*Q - [[RL01]]
*R - [[Microfiche]]
*S - [[ROM]]
*T - [[RK06]]
*V - [[RK07]]
*W - Multimedia
*X - [[RX02]]
*Y - [[RX01]]
*Z - No Hardware Dependency / Paper

== 9-Character Format XX-XXXXX-XX ==

With the advent of VMS V5 and as new VAX processors were introduced, the Software Products and Services used the new Software Model Number, a 9-character format.

=== Cluster Licensing ===

Samples:
*
*

'''1st and 2nd Letter'''
*QL - Licenses
*QT - SPS (Software Product Services)
*QA - Media and Documentation Kits
*QB - Packaged Software Components (License/Kit/SPS)

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''

'''6th and 7th Letter = CC (Country Code):'''
*A9 -
*GA - Germany

'''8th and 9th Letter = Cluster License Points:'''
*JB - 10
*JC - 20
*JD - 50
*JE - 100
*JF - 200
*JG - 300
*JH - 400
*JJ - 600
*JK - 900
*JL - 1200
*JM - 1800
*JN - 2400
*JS - 4800
*JV - 9000

=== CPU Licensing ===

Samples:
*QL-056AF-AA

'''1st and 2nd Letter = Software Product Type'''
* QA - Software documentation, media, and other software kits
* QB - Packaged software components
* QC - Software subassemblies
* QL - Software licenses (DEC processor tier, and platform licenses)
* QM - Software licenses (PC & standalone third-party license agreements)
* QP - Packaged software licenses
* QQ - Country information components
* QR - Assigned software uses
* QS - Professional services project and consulting services
* QT - Software product services
* QU - Software product services
* QW - Cross-functional service packages (CFSP)
* QX - Diagnostic/maintenance tools licenses
* QY - Diagnostic/maintenance tools services
* QZ - Diagnostic/maintenance tools documentation, media, and other hardware information kits
* Q2 - Software application products: license, media & documentation, and SPS
* Q3 - Software application products: license, media & documentation, and SPS

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''

'''6th Letter = Unknown (usually "A" or "G")'''

'''7th Letter = CPU Code:'''
*B - MicroVAX 3500, 3600
*C - VAXstation 3200, 3500, 8000
*D - VAX 8800, 6240, 8820
*E - VAX 8550, 8700, 8810
*F - VAX 8600, 8650
*G - VAX 8530
*H - VAX 8300, 8350
*J - VAX 8200, 11/782
*K - VAX-11/780, 11/785
*L - VAX-11/750
*M - VAX-11/730, 11/725
*N - MicroVAX II
*P - MicroVAX 2000
*Q - VAXstation II
*R - VAXstation 2000
*S - MicroVAX 3300, 3400
*U - VAX 8830, 8842
*V - VAX 8840
*2 - VAX 6210
*3 - VAX 6220
*4 - VAX 6230

'''8th and 9th Letter = Unknown (usually "AA")'''

== External References ==

*AA-5074O-RK System Software Information
*IAS 3.4A SPD
*EE-26108-68-84 DIGITAL Microcomponents Products U.S. Price List October-December 1984
*EE-18587-04-80 PDP-11, VAX-11 Price List April - September 1980
*ED PDP Systems and Options Catalog 1988

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

DEC Software-related Order Codes

2025-10-13T10:19:34Z

Vaxorcist: /* 9-Character Format XX-XXXXX-XX */ 1st & 2nd letter meanings added

DEC Software Media, Software License, Software Service, and Software Manual Order Codes

There are two formats whose use overlaps in time:

* 7-Character Format XXXXX-XX
* 9-Character Format XX-XXXXX-XX

The latter was introduced in 1988 for Software Products and Services for new processors while Software Products and Services for processors already introduced remained in the old 7-Character Format.

== 7-Character Format XXXXX-XX ==

Samples:
*ZYA06-P3 MicroPDP-11 RX33 Formatter Kit
*

'''1st Letter = Type of Software''':
*Y - [[Computer Special Systems]] Software
*Z - Diagnostics
*Q - System and Application Software

'''2nd Letter = Processor Identifier''':
*0 - [[MicroVAX]]/[[VAXserver]] 3500 and 3600
*1 - MicroVAX/VAXserver 3500 and 3600/[[VAXstation]] 3200 and 3500
*2 - [[VAX 8700]] and [[VAX 8550]]
*3 - [[MicroVAX 2000]]
*4 - [[VAXstation II]]
*5 - [[VAX 8200]] and [[VAX 8250]]
*6 - [[VAXmate]]
*7 - [[VAX 8300]] and [[VAX 8350]]
*8 - [[VAXstation 2000]]
*9 - [[VAX 8500]] and [[VAX 8530]]
*A - [[Digital Classified Software]], USA
*B - [[Professional 300 Series]]
*C - [[VAX-11/725]] and [[VAX-11/730]]
*D - [[VAX-11/750]]
*E - [[VAX-11/780]], [[VAX-11/782]], and [[VAX-11/785]]
*F - [[PDP-8]], [[WPS-8]], [[DECmate I]]
*G - Digital Classified Software, Internal
*H - [[DECsystem 10]]
*I - Digital Classified Software, GIA
*J - [[PDP-11]] [[UNIBUS]]-based ([[RT-11]], [[ULTRIX-11]])
*K - [[VAX 8600]] and [[VAX 8650]]
*L - All Models
*M - [[VAX 8800]], [[VAX 8974]], and [[VAX 8978]]
*N - [[MicroVAX I]]
*P - PDP-11 ([[RSTS]])
*Q - [[VAXstation I]]
*R - PDP-11 ([[RSX-11M]]/[[RSX-11M-PLUS]])
*S - Software
*T - [[DECsystem 20]]
*U - Digital Classified Software, Europe
*V - [[Rainbow]]
*W - [[DECmate II]]
*X - Cross prod, and/or no support services
*Y - [[MicroPDP-11]] [[QBUS]]-based
*Z - [[MicroVAX II]]

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''<br>
:Exception: Digital Classified Software, 2nd letter = A, G, I, U

'''6th Letter = Product Type''':
*1 - Dispatch Subscription Service
*2 - Dispatch Subscription
*3 - Self-Maintenance Service
*4 - Source Updates Service
*5 - Startup Service Level I
*6 - Additional Telephone Support Center Contact
*7 - Startup Service Level II
*8 - Basic Service
*9 - DECsupport Service
*A - Single-use License, Binaries, Documentation, Warranty
*B - Startup Service Level III
*C - License and Key, no Support
*D - License only
*E - Source License and Distribution
*F - Source Distribution and Listings / Microfiche
*G - Documentation Only (-GZ)
*H - Distribution and Documentation
*I - Installation Service
*J - PPL - Periodic Payment License ([[VAXcluster]])
*K - Documentation Service
*L - Sources Update
*M - Location-use Source License, Microfiche List
*N - Source Distribution
*P - No License, Binaries only
*Q - Single-use License for VAXcluster Node
*R - No License, Binaries Documentation
*S - DECstart Service
*T - Update
*U - Single-Use License
*V - For Service Delivery Only
*W - Warranty Update / For Service Delivery Only
*X - Single-use Sources License, Sources and Binaries, Documents, Warranty
*Y - Single-use Sources License, Sources and Binaries, Documents
*Z - Defense Acquisition Regulation/NASA Marking, Maintenance Service

'''7th Letter = Software Medium''':
*2 - [[RX180]]
*3 - [[RX50]]
*4 - [[RC25]]
*5 - [[TK50]]
*6 - [[TK25]]
*7 - [[RX33]]
*8 - [[CDROM]]
*A - [[Magnetic tape|9-Track Tape 6250 BPI]] / [[LINC tape]]
*B - [[Paper Tape]] / [[RX24]]
*C - [[DECtape]] / [[RX23]]
*D - [[Magnetic tape|9-Track Tape 800 BPI 600ft]]
*E - [[RK03]] / [[RK05]]
*F - [[Magnetic tape|7-Track Tape]]
*G - [[TU58]]
*H - [[RL02]]
*I - [[RX31]]
*J - [[RA60]]
*K - [[RP04]]
*L - [[RP06]]
*M - [[Magnetic tape|9-Track Tape 1600 BPI 2400ft]]
*N - [[TU60]]
*P - Cassette Tape ([[QIC]], [[DAT]], ...) / [[Magnetic tape|9 Track Magtape 800 BPI 2400ft]]
*Q - [[RL01]]
*R - [[Microfiche]]
*S - [[ROM]]
*T - [[RK06]]
*V - [[RK07]]
*W - Multimedia
*X - [[RX02]]
*Y - [[RX01]]
*Z - No Hardware Dependency / Paper

== 9-Character Format XX-XXXXX-XX ==

With the advent of VMS V5 and as new VAX processors were introduced, the Software Products and Services used the new Software Model Number, a 9-character format.

=== Cluster Licensing ===

Samples:
*
*

'''1st and 2nd Letter'''
*QL - Licenses
*QT - SPS Services
*QA - Media and Documentation Kits
*QB - Packaged Software Components (License/Kit/SPS)

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''

'''6th and 7th Letter = CC (Country Code):'''
*A9 -
*GA - Germany

'''8th and 9th Letter = Cluster License Points:'''
*JB - 10
*JC - 20
*JD - 50
*JE - 100
*JF - 200
*JG - 300
*JH - 400
*JJ - 600
*JK - 900
*JL - 1200
*JM - 1800
*JN - 2400
*JS - 4800
*JV - 9000

=== CPU Licensing ===

Samples:
*QL-056AF-AA

'''1st and 2nd Letter = Software Product Type'''
* QA - Software documentation, media, and other software kits
* QB - Packaged software components
* QC - Software subassemblies
* QL - Software licenses (DEC processor tier, and platform licenses)
* QM - Software licenses (PC & standalone third-party license agreements)
* QP - Packaged software licenses
* QQ - Country information components
* QR - Assigned software uses
* QS - Professional services project and consulting services
* QT - Software product services
* QU - Software product services
* QW - Cross-functional service packages (CFSP)
* QX - Diagnostic/maintenance tools licenses
* QY - Diagnostic/maintenance tools services
* QZ - Diagnostic/maintenance tools documentation, media, and other hardware information kits
* Q2 - Software application products: license, media & documentation, and SPS
* Q3 - Software application products: license, media & documentation, and SPS

'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''

'''6th Letter = Unknown (usually "A" or "G")'''

'''7th Letter = CPU Code:'''
*B - MicroVAX 3500, 3600
*C - VAXstation 3200, 3500, 8000
*D - VAX 8800, 6240, 8820
*E - VAX 8550, 8700, 8810
*F - VAX 8600, 8650
*G - VAX 8530
*H - VAX 8300, 8350
*J - VAX 8200, 11/782
*K - VAX-11/780, 11/785
*L - VAX-11/750
*M - VAX-11/730, 11/725
*N - MicroVAX II
*P - MicroVAX 2000
*Q - VAXstation II
*R - VAXstation 2000
*S - MicroVAX 3300, 3400
*U - VAX 8830, 8842
*V - VAX 8840
*2 - VAX 6210
*3 - VAX 6220
*4 - VAX 6230

'''8th and 9th Letter = Unknown (usually "AA")'''

== External References ==

*AA-5074O-RK System Software Information
*IAS 3.4A SPD
*EE-26108-68-84 DIGITAL Microcomponents Products U.S. Price List October-December 1984
*EE-18587-04-80 PDP-11, VAX-11 Price List April - September 1980
*ED PDP Systems and Options Catalog 1988

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

Talk:MicroVAX I

2025-10-02T07:37:42Z

Vaxorcist: Unable to upload picture

==Spec differences?==

The old content had ram = 1 MB, and year introduced = 1984; not sure which is correct. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 15:36, 29 July 2017 (CEST)

: The MicroVAX I Pocket Service Guide (EK-KD32A_PG-001, Aug 1984) says 3MB if you fill all six slots with memory but in practice you need peripherals, so four slots of memory (2MB) is a practical limit. That's using MSV11-P boards. The Supermicrosystems handbook says that the KD32-AA has a limit of 4MB (which I think is an architectural limit based on the amount of memory possible on the Qbus). MSV11-Q memory boards had more capacity but I don't have an old enough Systems and Options catalogue to know whether they were supported in the uV1. So 1MB is, I think, wrong. 3MB is certainly possible but (in 1984) impractical. 4MB seems quite plausible to me but I don't have a cast iron reference (yet!). As for 1984, the earliest manuals have that date. ComputrWorld June 18 1984 carries a feature on p 58 or so. So announced in 1983 and shipped in 1984 does sound right. Somewhere or other I know there is a write-up of the story behind the uVAX I, but I don't seem to have it to hand. [[User:Antonioc|Antonioc]] ([[User talk:Antonioc|talk]]) 20:58, 29 July 2017 (CEST)

== MSV11-J versions ==

Which versions work in the MicroVAX I? The -JB/-JC apparently have bugs in their QBUS support, so they only work in the [[PDP-11/84]]; the -JD/-JE will work anywhere. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 13:05, 16 June 2022 (CEST)

: The MicroVAX I can only use QBUS memories, or QBUS-compatible memories (like the MSV11-JD/-JE), so the -JB/-JC will most probably NOT work.
: My own MicroVAX I is running with a MSV11-JE 2 MB board in slot 3. [[User:Vaxorcist|Vaxorcist]] ([[User talk:Vaxorcist|talk]]) 14:01, 16 June 2022 (CEST)

:: OK, thanks for confirming that.
:: [http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/hardware/micronotes/numerical/micronote28.txt Micronote 28] does say "[the -JB and -JC] modules can not be used in a Q-bus system due to gate array incompatibilities", which I take to mean 'MSV11-JB/-JC cards don't work on the QBUS'.
:: I recall reading someone's report, which I just tried to search for, but cannot find, that they tried to use a -JB/-JC in a [[PDP-11/83]] (I think), and it damaged the file system. This makes sense, if the problem as is it is described, since in an /83, the CPU will use PMI to talk to the MSV11-J, whereas DMA devices will try and use the QBUS - but in the /84, both CPU and DMA will use PMI (the DMA via the [[KTJ11-B]]). [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 19:09, 16 June 2022 (CEST)

== Unable to upload picture ==

When trying to upload a picture I get the following message:

'''Could not open lock file for "mwstore://local-backend/local-public/4/48/Microvax_I_and_VT100.jpg".'''

At first I thought it might be up to the file name or size, but nothing helped - can you help? [[User:Vaxorcist|Vaxorcist]] ([[User talk:Vaxorcist|talk]]) 07:37, 2 October 2025 (UTC)

MicroVAX I

2025-10-02T07:21:08Z

Vaxorcist: /* Supported Boot Devices */ DEQNA & DELQA removed (because NOT supported for booting)

{{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>

==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]]

ULTRIX-32m

2025-10-02T07:08:55Z

Vaxorcist: The manuals say it's rather ULTRIX-32m than ULTRIX-32M

#Redirect [[ULTRIX]]

ULTRIX

2025-10-01T18:12:25Z

Vaxorcist: /* VAX */ Differences between ULTRIX-32 and ULTRIX-32m added

{{Infobox OS
| image = ultrix40.png
| caption = Logging into an Ultrix 4.0 system
| name = ULTRIX
| creator = [[Digital Equipment Corporation]]
| current version = 4.5 for VAX and DECStation (1995)
| year introduced = ULTRIX-11: 1982, ULTRIX-32: 1984
| type = Multi-tasking, multi-user Unix
| architecture = [[PDP-11]], [[VAX]], [[DECStation]]/[[DECsystem]] ([[RISC]])
}}

'''ULTRIX''' was [[Digital Equipment Corporation|DEC]]'s official [[UNIX]] for [[VAX]], [[PDP-11]] and [[DECStation]]/[[DECsystem]] ([[RISC]]) equipment.

==PDP-11==

'''ULTRIX-11''' was available for the PDP-11 and can be obtained up to version 3.1 from the [[The Unix Heritage Society|TUHS]] archive (below). It will run under [[SIMH]] (and other PDP-11 emulators).

These are the known ULTRIX-11 versions and predecessors:
* 1981: Unix/v7m V2.1
* 1982/83: V7M-11 V1.0 (= ULTRIX-11 V1.0)
* 1984: ULTRIX-11 V2.0
* 1986: ULTRIX-11 V3.0
* 1987: ULTRIX-11 V3.1 (last version)

==VAX==

'''ULTRIX-32''' (from version 4.0 onwards called: '''ULTRIX/VAX''') for the VAX was derived from [[4.2 BSD]] with some influences from [[UNIX System V|SYSV]] and included support for specific DEC technologies. The latest version is 4.5 from 1995. Earlier versions of ULTRIX-32 are available from TUHS. It will run under the VAX simulator in SIMH.

Timeline of the main VAX versions:
* 1984: V1.0
* 1986: V2.0
* 1988: V3.0
* 1990: V4.0

===ULTRIX-32 / ULTRIX-32m===

During the V1.x phase there were special versions of ULTRIX-32 for the [[MicroVAX]] computers called '''ULTRIX-32m''' (similar to the relationship between [[VMS]] and [[MicroVMS]]).

The two types of ULTRIX-32 differed by:
* Distribution media ([[RX50]]/[[TK50]]) instead of 9-track [[magnetic tape]]
* Supported [[bus]] types, e.g. [[QBUS]] (MicroVAX) versus [[UNIBUS]] resp. [[VAX Bus Interconnect|VAXBI]] (VAX)
* Supported [[controller]]s and [[peripheral|peripheral devices]]
* Scope of software tools
* Manuals

The prices were adjusted to the level of MicroVAX software as well.

It is not known whether there were any V2 versions of ULTRIX-32m, too.

==DEC MIPS-based Computers==

ULTRIX/RISC for DECstation and DECsystem computers is not available from TUHS. The latest version is 4.5 from 1995. This version will also run, (Including CDE + X11!) under [[GXemul]].

==Y2K compatibility==

It's been confirmed that 4.0 is NOT Y2K compatible... Not many UNIX from the 1990's or prior are so it's really no surprise...

==Running ULTRIX==

SIMH will run Ultrix. Many simulators -if not all- of supported VAX computers are known to work.

Installation instructions for SIMH can be found at:
* [[Installing ULTRIX-11 V1.0 on SIMH]]
* [[Installing Ultrix V1.1 on SIMH]]
* [[Advanced Installation of Ultrix V2.0 on SIMH]]
* [[Setting Up RIS on ULTRIX V2.0]]
* [[Installing and Configuring an ULTRIX V3.0 DMS Server on a SIMH MicroVAX 3900]]
* [[Installing Ultrix 4.0 on SIMH]]
* [[Installing Ultrix 4.5 on SIMH]]

==See also==

* [[ULTRIX Diskless Mangement Services]]
* [[ULTRIX Remote Console]]

==External links==

* [https://www.tuhs.org/Archive/Distributions/DEC/ DEC] - various ULTRIX distros
** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=Ultrix-3.1 Ultrix-3.1] - PDP-11 version
*** [https://minnie.tuhs.org/cgi-bin/utree.pl?file=Ultrix-3.1/sys/sas/README ULTRIX-11 V3.0 changes to stand-alone system] - useful kernel documentation
* [ftp://ifctfvax.harhan.org/pub/UNIX/thirdparty/Ultrix-32/sources/ Ultrix-32] - Sourcecode for Ultrix-32

{{Nav Unix}}

[[Category: PDP-11 Operating Systems]]
[[Category: VAX Operating Systems]]
[[Category: DEC Operating Systems]]
[[Category: Unix-based OS's]]
[[Category: ULTRIX]]