====== Installation und Einrichtung von OpenVMS 7.3 einer emulierten (Micro-) VAX unter SIMH ======
===== Voraussetzungen =====
* Es sollte sichergestellt werden, dass die Funktionalität für den Ethernet-Support gegeben ist (aktivierte Funktionalität in SIMH, sow eine Bridge auf dem Host-Computer).
* Ein ISO-Image von DECs Installationsmedium OpenVMS 7.3 für VAX.
===== Konfigurationsdatei start.txt für die MicroVAX mit OpenVMS unter SIMH =====
echo
echo SimH 4.0 Configuration file for MicroVAX 3900
echo
echo Host System : DEC MicroVAX 3900
echo Operating System : DEC OpenVMS 7.3
echo Memory : 64 MiB
echo Network config : XQ: Ethernet, 08:00:2b:04:14:06
echo Disks : RQ0: RA92, 1.5 GB
echo : RQ1: RA92, 1,5 GB
echo CDROMs : RQ2: iso file
echo : VAXVMS071.ISO = Installation Disc
echo
load -r ka655x.bin
; NVRAM
attach NVR nvram.bin
; CPU config
set CPU 64m
set CPU conhalt
set CPU idle
; configure console to 7-bit only
;set TTO 7b
;set TTI 7b
; Disk drives
set RQ0 ra92
attach RQ0 rq0-ra92.dsk
set RQ1 ra92
attach RQ1 rq1-ra92.dsk
set RQ2 CDROM
attach rq2 ../install-images/VAXVMS073.ISO
set RQ3 disable
; Tape
set TQ0 disable
set TQ1 disable
set TQ2 disable
set TQ3 disable
; serial port, simulated by Telnet to port 1005
set DZ disable
; printer
;set LPT enable
;attach LPT printer_output.txt
; Disable unused peripherals
set CR disable
set RL disable
set TS disable
; Network interface (08-00-2b is the DEC prefix, the 04-14-06 part is arbitrary)
set XQ MAC=08-00-2b-04-14-06
attach xq tap:tap0
; serial console (launch directly after booting CPU)
;set console telnet=1001
; experimental
;set QVSS en
; boot the system
boot CPU
; Uncomment the line below to enable auto-boot
;dep bdr 0
===== Der erste Start des SIMH Emulators =====
Beim ersten Start kann es einige Zeit dauern, da SimH die Disk-Images erstellen muss (insgesamt ~ 3 GB).
Folgende Ausgabe erscheint auf der Konsole.:
simh@debian:~/MicroVAX3900-OpenVMS$ **../simh-Beta4/BIN/vax start-vax.txt**
MicroVAX 3900 simulator V4.0-0 Current git commit id: beaa1e73
/home/simh/MicroVAX3900-OpenVMS/start-vax.txt-18> attach NVR nvram.bin
NVR: creating new file
NVR: buffering file in memory
/home/simh/MicroVAX3900-OpenVMS/start-vax.txt-31> attach RQ0 rq0-ra92.dsk
RQ0: creating new file: rq0-ra92.dsk
/home/simh/MicroVAX3900-OpenVMS/start-vax.txt-33> attach RQ1 rq1-ra92.dsk
RQ1: creating new file: rq1-ra92.dsk
/home/simh/MicroVAX3900-OpenVMS/start-vax.txt-35> attach rq2 ../install-images/VAXVMS071.ISO
RQ2: '../install-images/VAXVMS071.ISO' Contains ODS2 File system
RQ2: Volume Name: VAXVMS071 Format: DECFILE11B Sectors In Volume: 800000
/home/simh/MicroVAX3900-OpenVMS/start-vax.txt-58> attach xq tap:tap0
Eth: opened OS device tap0
KA655-B V5.3, VMB 2.7
1) Dansk
2) Deutsch (Deutschland/�sterreich)
3) Deutsch (Schweiz)
4) English (United Kingdom)
5) English (United States/Canada)
6) Espa�ol
7) Fran�ais (Canada)
8) Fran�ais (France/Belgique)
9) Fran�ais (Suisse)
10) Italiano
11) Nederlands
12) Norsk
13) Portugu�s
14) Suomi
15) Svenska
(1..15):5
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
Als Erstes wird von der virtuellen Installations-CD gebootet und das aktuelle Datum sowie die aktuelle Uhrzeit wird abgefragt.
>>>boot dua2
(BOOT/R5:0 DUA2
2..
-DUA2
1..0..
%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-W-SYSBOOT Can not map SYSDUMP.DMP on the System Disk
%SYSBOOT-W-SYSBOOT Can not map PAGEFILE.SYS on the System Disk
OpenVMS (TM) VAX Version X7G7 Major version id = 1 Minor version id = 0
%WBM-I-WBMINFO Write Bitmap has successfully completed initialization.
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 27-DEC-2020 17:00
Configuring devices . . .
Now configuring HSC, RF, and MSCP-served devices . . .
Please check the names of the devices which have been configured,
to make sure that ALL remote devices which you intend to use have
been configured.
If any device does not show up, please take action now to make it
available.
Available device DUA0: device type RA92
Available device DUA1: device type RA92
Available device DUA2: device type RRD40
Enter "YES" when all needed devices are available: y
%BACKUP-I-IDENT, Stand-alone BACKUP T7.2; the date is 27-DEC-2020 17:02:11.32
Zurzeit wird ein kleines eigenständiges Betriebssystem ausgeführt, das zum Sichern und Wiederherstellen von Daten verwendet wird. Folgender Befehl muss verwendet werden, um das VMS "Sicherungsset" von der CD-ROM auf die erste Festplatte zu übertragen.
$ backup dua2:vms073.b/save_set dua0:
%BACKUP-I-PROCDONE, operation completed. Processing finished at 27-DEC-2020 17:03:54.24
If you do not want to perform another standalone BACKUP operation,
use the console to halt the system.
If you do want to perform another standalone BACKUP operation,
ensure the standalone application volume is online and ready.
Enter "YES" to continue:
Nun wurde VMS auf die Festplatte kopiert. Nun ist die Emulation mit der Tastenkombination Control-E zu beenden, da zu diesem Zeitpunkt keine weiteren Sicherungssätze mehr wiederhergestellt werden müssen. Das System muss wieder neu gestartet werden, damit der Installationsprozess fortgesetzt werden kann.
===== Boot-Vorgang von OpenVMS von der Installations-CD =====
Simulation stopped, PC: 839ABD40 (MOVL (R5),R4)
sim> boot cpu
Wiederholtes Booten der VAX.
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
Nun wird in Zukunft von der ersten virtuellen Festplatte DUA0 gebootet, deswegen wird als Standardgerät eingerichtet. Wird dies nicht getan, so wird das System automatisch immer zu versuchen von der Netzwerkschnittstelle XQA0 booten zu wollen. Der folgende Startbefehl weist das System an, von dem gerade festgelegten Standardgerät zu starten.
>>>set boot dua0
>>>boot
(BOOT/R5:0 DUA0
2..
-DUA0
1..0..
%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-W-SYSBOOT Can not map SYSDUMP.DMP on the System Disk
%SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk
%SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS
OpenVMS (TM) VAX Version BI73-7G7 Major version id = 1 Minor version id = 0
%WBM-I-WBMINFO Write Bitmap has successfully completed initialization.
OpenVMS VAX V7.3 Installation Procedure
Model: VAXserver 3900 Series
System device: RA92 - _DUA0:
Free Blocks: 2854566
CPU type: 10-01
* Please enter the date and time (DD-MMM-YYYY HH:MM) 27-DEC-2020 17:05
*********************************************************
%SYSTEM-W-TZGMT, your local timezone has defaulted to GMT
%SYSTEM-I-SETTZ, to set your local timezone use:
$ @SYS$MANAGER:UTC$TIME_SETUP.COM
*********************************************************
On MIN or UPGRADE system startup - CLUE is not run.
%%%%%%%%%%% OPCOM 27-DEC-2020 17:05:02.84 %%%%%%%%%%%
Operator _OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 27-DEC-2020 17:05:02.84 %%%%%%%%%%%
Operator status for operator _OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%%%%%%%%%%% OPCOM 27-DEC-2020 17:05:02.90 %%%%%%%%%%%
Logfile has been initialized by operator _OPA0:
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
%%%%%%%%%%% OPCOM 27-DEC-2020 17:05:02.90 %%%%%%%%%%%
Operator status for operator SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%SYSTEM-I-BOOTUPGRADE, security auditing disabled
%%%%%%%%%%% OPCOM 27-DEC-2020 17:05:03.27 %%%%%%%%%%%
Message from user JOB_CONTROL
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 27-DEC-2020 17:05:03.27 %%%%%%%%%%%
Message from user JOB_CONTROL
-RMS-E-FNF, file not found
%LICENSE-F-EMTLDB, license database contains no license records
%SYSTEM-I-BOOTUPGRADE, security server not started
%%%%%%%%%%% OPCOM 27-DEC-2020 17:05:04.60 %%%%%%%%%%%
Message from user SYSTEM
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
Startup processing continuing...
%SET-I-INTSET, login interactive limit = 1, current interactive value = 0
%SET-I-INTSET, login interactive limit = 0, current interactive value = 0
If this system disk is to be used in an OpenVMS Cluster with multiple
system disks, then each system disk must have a unique volume label.
Any nodes having system disks with duplicate volume labels will fail
to boot into the cluster.
You can indicate a volume label of 1 to 12 characters in length. If you
want to use the default name of OVMSVAXSYS, press RETURN in response
to the next question.
Folgend werden die grundlegenden Parameter der Installation abgefragt. Das Startvolume mit der VMS-Installation auf der ersten Festplatte soll erstmal schlicht OpenVMS heißen. Nachdem geprüft ist, ob die Installations-CD auch vorhanden ist, werden die Basiskomponenten installiert.
* Enter the volume label for this system disk [OVMSVAXSYS]: OpenVMS
* Enter name of drive holding the OpenVMS distribution media: dua2
* Is the OpenVMS media ready to be mounted? [N] y
%MOUNT-I-MOUNTED, VAXVMS073 mounted on _DUA2:
Select optional software you want to install. You can install one
or more of the following OpenVMS or DECwindows components:
o OpenVMS library - 52200 blocks
o OpenVMS optional - 19000 blocks
o OpenVMS Help Message - 10400 blocks
o OpenVMS Management Station - 20000 blocks
o DECwindows base support - 4400 blocks
o DECwindows workstation support - 23800 blocks
- 75 dots per inch video fonts - (included)
- 100 dots per inch video fonts - 6200 blocks
o DECnet-Plus networking - 80000 blocks
o DECnet Phase IV networking - 800 blocks
Space remaining on system disk: 2854377 blocks
* Do you want to install the OpenVMS library files? (Y/N) y
Space remaining on system disk: 2802177 blocks
* Do you want to install the OpenVMS optional files? (Y/N) y
Space remaining on system disk: 2783177 blocks
The Help Message utility (MSGHLP) provides online explanations
and user actions for OpenVMS messages in place of the hardcopy
OpenVMS System Messages and Recovery Procedures Reference Manual,
which is now separately orderable.
The MSGHLP database file, MSGHLP$LIBRARY.MSGHLP$DATA,
consumes approximately 10400 blocks and will be
placed by default on your system disk in SYS$COMMON:[SYSHLP]
unless you specify an alternate device when prompted.
* Do you want to install the MSGHLP database? (Y/N) y
You can install this database on your system disk in SYS$COMMON:[SYSHLP]
or on an alternate device. If you specify an alternate device, but no
directory, MSGHLP$LIBRARY.MSGHLP$DATA is placed in [HELP_MESSAGE]. When
prompted, take the default of the system disk or specify an alternate
device using this format:
device:[directory]
* Where do you want to install the MSGHLP database?
[SYS$COMMON:[SYSHLP]] [Return]
Space remaining on system disk: 2772777 blocks
The OpenVMS Management Station is a client-server application that
provides OpenVMS system management capabilities through a client
application on a personal computer (PC) running Microsoft Windows.
The server application runs on OpenVMS systems and is automatically
installed as part of the OpenVMS operating system.
This option provides the files used to install the PC client software.
If you want to use the OpenVMS Management Station, you must install
these optional files on at least one OpenVMS system and then use one or
both of them to install the PC client on one or more PCs. There are two
files: TNT030_I.EXE for Intel systems (Windows 95 and Windows NT), and
TNT030_A.EXE for Alpha Windows NT systems.
The OpenVMS Management Station optional files consume approximately 20000
blocks and will be placed on your system disk in SYS$COMMON:[TNT.CLIENT].
* Do you want to install the optional OpenVMS Management Station files? (Y/N) y
Space remaining on system disk: 2752777 blocks
You can select DECwindows now, or you can use the DECW$TAILOR utility
to provide or remove DECwindows support after the installation.
Some media, TK50s in particular, can be very slow when tailoring on files.
You might want to select DECwindows now and tailor off unwanted files later.
NOTE: This kit does NOT contain full DECwindows.
To obtain full DECwindows, you must also install the separate
layered product, DECwindows Motif for OpenVMS VAX.
V1.2-3 is the minimum version of DECwindows Motif for OpenVMS VAX
that can be used with OpenVMS VAX V7.3.
The DECwindows components provided in this kit requires approximately
34400 blocks, broken down as follows:
o DECwindows base support - 4400 blocks
o DECwindows workstation support - 23800 blocks
- 75 dots per inch video fonts - (included)
- 100 dots per inch video fonts (optional) - 6200 blocks
You must select the DECwindows base support option if
- you plan to run DECwindows software, or
- you are installing this kit on
* a workstation or
* an OpenVMS Cluster that contains workstations, or
- you want to provide font files for Xterminals.
If you are installing this kit on a system that includes Xterminals
and you do NOT select DECwindows base support, then you will have to use
the DECW$TAILOR utility to provide font files.
Es sollen auch alle Komponenten für den Betrieb der grafischen Benutzeroberfläche DECwindows mit Motif installiert werden.
* Do you want the DECwindows base support? (Y/N) y
Space remaining: 2748377 blocks
You must select the DECwindows workstation support option if
- you are installing this kit on
* a workstation or
* an OpenVMS Cluster that contains workstations, or
- you want to provide font files for Xterminals.
If you are installing this kit on a system that includes Xterminals
and you do NOT select DECwindows workstation support, then you will have
to use the DECW$TAILOR utility to provide font files.
* Do you want to install DECwindows workstation support? (Y/N) y
Space remaining: 2724577 blocks
DECwindows workstation support includes the 75 dots per inch video fonts.
All DECwindows applications run with 75 dots per inch video fonts.
By default, most systems startup with 75 dots per inch video fonts.
Certain applications can take advantage of 100 dots per inch video fonts.
For the VAXstation 4000 series machines, 100 dots per inch video fonts
are used by default. If you decide not to install 100 dots per inch
video fonts, you must edit SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM
to force 75 dots per inch video fonts to be the default. Otherwise,
certain applications may not space text properly.
For instructions on how to configure your system with both 75 and 100
dots per inch video fonts, see the installation guide or look at the
template command procedure SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE.
* Do you want 100 dots per inch video fonts installed? (Y/N) y
Space remaining: 2718377 blocks
Beginning with OpenVMS V7.1, the DECnet-Plus kit is provided with
the OpenVMS operating system kit. Compaq strongly recommends that
DECnet users install DECnet-Plus. DECnet Phase IV applications are
supported by DECnet-Plus.
DECnet Phase IV is also provided as an option. Support for DECnet
Phase IV is available through a Prior Version Support Contract.
If you install DECnet-Plus and TCP/IP you can run DECnet
applications over a TCP/IP network. Please see the OpenVMS
Management Guide for information on running DECnet over TCI/IP.
If you plan to install DECnet Phase IV do NOT select DECnet-Plus.
Damit OpenVMS mit dem TCP/IP-Protokoll-Stack funktioniert, ist es nötig DECnet-Plus mitzuinstallieren.
* Do you want to install DECnet-Plus? (Y/N) y
Space remaining on system disk: 2638377 blocks
DECnet Phase IV will not be installed.
The following options will be provided:
OpenVMS library
OpenVMS optional
OpenVMS Help Message
OpenVMS Management Station Software -- PC files
DECwindows base support
DECwindows workstation support with:
- 75 dots per inch video fonts
- 100 dots per inch video fonts
DECnet-Plus
Space remaining on system disk: 2638377 blocks
* Is this correct? (Y/N) y
Restoring OpenVMS library save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring OpenVMS optional save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring OpenVMS Help Message save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring OpenVMS Management Station Software -- PC files
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring DECwindows base support save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring DECwindows workstation support save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring DECwindows 75 dots per inch video fonts save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring DECwindows 100 dots per inch video fonts save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Now registering the OpenVMS operating system in the
POLYCENTER Software Installation product database
The following product will be registered:
DEC VAXVMS VMS V7.3 DISK$VAXVMSV73:[VMS$COMMON.]
The following product has been registered:
DEC VAXVMS VMS V7.3 Transition (registration)
You can now remove the distribution kit from DUA2:.
In an OpenVMS Cluster, you can run multiple systems sharing all files
except PAGEFILE.SYS, SWAPFILE.SYS, SYSDUMP.DMP, and VAXVMSSYS.PAR.
Cluster configuration cannot be done at this time because no network
is present. In order to configure a cluster you must FIRST do one
or both of the following:
o Install DECnet-Plus (or DECnet Phase IV), or
o Execute SYS$STARTUP:LAN$STARTUP.COM by removing the
comment delimiter ("!") from the line
$! @SYS$STARTUP:LAN$STARTUP
in SYS$MANAGER:SYSTARTUP_VMS.COM.
Then configure the cluster by executing the following command:
@ @SYS$MANAGER:CLUSTER_CONFIG
See the OpenVMS System Manager's Manual: Essentials for more information.
* Do you want DECwindows Motif as the default windowing system? (Y/N) y
Now we will ask you for new passwords for the following accounts:
SYSTEM, SYSTEST, FIELD
Passwords must be a minimum of 8 characters in length. All passwords
will be checked and verified. Any passwords that can be guessed easily
will not be accepted.
Bei der Installation von OpenVMS werden drei User-Accounts angelegt. Der Account 'SYSTEM' ist mit dem 'root'-Account unter Unix vergleichbar. Die Accounts 'SYSTEST' und 'FIELD' reichen im Umfang ihrer Privilegien für die meisten Aufgaben aus. Sie sollen für Demonstrationszwecken und Tests genutzt werden. Weitere Accounts lassen sich darüber hinaus auch beliebig anlegen und konfigurieren.
* Enter password for SYSTEM: [Password here]
* Re-enter for verification: [Password here]
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for SYSTEM verified
* Enter password for SYSTEST: [Password here]
* Re-enter for verification: [Password here]
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for SYSTEST verified
The SYSTEST_CLIG account will be disabled. You must re-enable
it before running UETP but do not assign a password.
%UAF-I-PWDLESSMIN, new password is shorter than minimum password length
%UAF-I-MDFYMSG, user record(s) updated
* Enter password for FIELD: [Password here]
* Re-enter for verification: [Password here]
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for FIELD verified
Creating RIGHTS database file, SYS$SYSTEM:RIGHTSLIST.DAT
Ignore any "-SYSTEM-F-DUPIDENT, duplicate identifier" errors.
%UAF-I-RDBCREMSG, rights database created
%UAF-I-RDBADDMSGU, identifier DEFAULT value [000200,000200] added to rights database
%UAF-I-RDBADDMSGU, identifier FIELD value [000001,000010] added to rights database
%UAF-I-RDBADDMSGU, identifier SYSTEM value [000001,000004] added to rights database
%UAF-I-RDBADDMSGU, identifier SYSTEST value [000001,000007] added to rights database
%UAF-E-RDBADDERRU, unable to add SYSTEST_CLIG value [000001,000007] to rights database
-SYSTEM-F-DUPIDENT, duplicate identifier
%UAF-I-NOMODS, no modifications made to system authorization file
%UAF-I-RDBDONEMSG, rights database modified
Creating MODPARAMS.DAT database file, SYS$SYSTEM:MODPARAMS.DAT
Der SCSNODE-Name entspricht dem Hostnamen und die SCSSYSTEMID ist für DECnet nötig.
* Please enter the SCSNODE name: VAX
* Please enter the SCSSYSTEMID: 1300
After the installation finishes, you might want to do one or more of the
following tasks:
o DECOMPRESS THE SYSTEM LIBRARIES - To save space, many of the system
libraries are shipped in a data-compressed format. If you have
enough disk space, you can decompress the libraries for faster access.
To data expand the libraries, type:
$ @SYS$UPDATE:LIBDECOMP.COM
If you do not decompress these libraries, you will experience
slower response to the HELP and LINK commands.
o BUILD A STANDALONE BACKUP KIT - You can build a standalone backup kit
using the procedure described in the "Backup Procedures" chapter of
tye upgrade and installation supplement provided for your VAX computer.
o TAILOR THE SYSTEM DISK - You might want to review the files provided or
not provided during this installation. If you find there are files
you want to remove from the system disk (TAILOR OFF) or files you want
to add (TAILOR ON), use the following utilities to perform the
desired tailoring.
OpenVMS tailoring: $ RUN SYS$UPDATE:VMSTAILOR
DECwindows tailoring: $ RUN SYS$UPDATE:DECW$TAILOR
NOTE: The tailor procedure cannot be used to TAILOR ON or TAILOR OFF
files located on an alternate disk.
=================================================================
Continuing with OpenVMS VAX V7.3 Installation Procedure.
Configuring all devices on the system ...
Da derzeit keine Lizenz für OpenVMS vorhanden ist, kann diese erst einmal nicht registriert werden. Sie kann aber später jederzeit im System registriert werden.
If you have Product Authorization Keys (PAKs) to register, you can
register them now.
* Do you want to register any Product Authorization Keys? (Y/N): n
********************************************************************************
After the system has rebooted you must register any Product
Authorization Keys (PAKs) that you have received with this kit.
You can register these PAKs by executing the following procedure:
$ @SYS$UPDATE:VMSLICENSE
See the OpenVMS License Management Utility Manual for any additional
information you need.
********************************************************************************
Die obligatorische Konfiguration der Zeitzone und ob zur Zeit der Installation die Uhren auf die normale Zeit oder die Sommerzeit gestellt ist. Da zur Zeit der Erstellung dieser Anleitung Dezember ist, muss die Sommerzeit nicht berücksichtigt werden.
%UTC-I-UPDTIME, updating Time Zone information in SYS$COMMON:[SYSEXE]
Configuring the Local Time Zone
TIME ZONE SPECIFICATION -- Main Time Zone Menu
1) Australia 11) GMT 21) Mexico 31) Turkey
2) Brazil 12) Greenwich 22) NZ 32) UCT
3) CET 13) Hong Kong 23) NZ-CHAT 33) US
4) Canada 14) Iceland 24) Navajo 34) UTC
5) Chile 15) Iran 25) PRC 35) Universal
6) Cuba 16) Israel 26) Poland 36) W-SU
7) EET 17) Jamaica 27) ROC 37) WET
8) Egypt 18) Japan 28) ROK 38) Zulu
9) Factory 19) Libya 29) Singapore
10) GB-Eire 20) MET 30) SystemV
0) None of the above
Select the number above that best describes your location: 20
You selected MET as your time zone.
Is this correct? (Yes/No) [YES]: [Return]
Default Time Differential Factor for standard time is 1:00.
Default Time Differential Factor for daylight saving time is 2:00.
The Time Differential Factor (TDF) is the difference between your
system time and Coordinated Universal Time (UTC). UTC is similar
in most repects to Greenwich Mean Time (GMT).
The TDF is expressed as hours and minutes, and should be entered
in the hh:mm format. TDFs for the Americas will be negative
(-3:00, -4:00, etc.); TDFs for Europe, Africa, Asia and Australia
will be positive (1:00, 2:00, etc.).
Is Daylight Savings time in effect? (Yes/No): n
Enter the Time Differential Factor [1:00]: [Return]
NEW SYSTEM TIME DIFFERENTIAL FACTOR = 1:00.
Is this correct? [Y]: [Return]
Es folgt noch die Installation für die Netzwerkkomponenten für die Vernetzung mittels DECnet unter OpenVMS. Wie zu Anfang das gleiche Verfahren mit der Installationsquelle als Laufwerk DUA2 für die virtuelle CD-ROM. Wenn die Installation der DECnet-Komponenten abgeschlossen ist, so wird das System einen Reboot durchführen und mit der Login-Aufforderung ist die Installation abgeschlossen.
DECnet-Plus will now be installed.
Media containing the DECnet-Plus kit must be available.
If you are installing OpenVMS from an Infoserver (DAD1)
or local CD-ROM, there is a DECnet-Plus kit on the CD-ROM.
If you are installing from a cartridge tape (TK50) or
from an open reel tape, you should have a DECnet-Plus kit
on cartidge tape or open reel tape.
An appropriate DECnet-Plus kit may also be available on
the Consolidated Distribution CD-ROM, or you may have a
separate DECnet-Plus kit.
NOTE: You may choose any available media for the
DECnet-Plus kit. It is NOT NECESSARY to use the same
type of media that contained the OpenVMS kit.
If you do not have a DECnet-Plus kit available, or if you
have decided NOT to install/upgrade DECnet-Plus, you can
bypass the DECnet-Plus installation by entering "EXIT"
for the "name of drive holding the DECnet-Plus kit".
* Enter name of drive holding the DECnet-Plus kit: dua2
* Is DUA2: ready to be mounted? [N] y
The following product has been selected:
DEC VAXVMS DECNET_OSI V7.3 Layered Product
Configuration phase starting ...
You will be asked to choose options, if any, for each selected product and for
any products that may be installed to satisfy software dependency requirements.
DEC VAXVMS DECNET_OSI V7.3: DECnet-Plus V7.3 for OpenVMS VAX
Copyright 2001 Compaq Computer Corporation.
Compaq Computer Corporation
This product requires one of two PAKs: DVNETEND or DVNETRTG.
Do you want the defaults for all options? [YES] [Return]
Do you want to review the options? [NO] [Return]
Execution phase starting ...
The following product will be installed to destination:
DEC VAXVMS DECNET_OSI V7.3 DISK$VAXVMSV73:[VMS$COMMON.]
Portion done: 0%...10%...20%...30%...40%...80%...90%...100%
The following product has been installed:
DEC VAXVMS DECNET_OSI V7.3 Layered Product
********************************************************************************
Running AUTOGEN to compute the new SYSTEM parameters ...
%AUTOGEN-I-BEGIN, GETDATA phase is beginning.
%AUTOGEN-I-NEWFILE, Previous contents of SYS$SYSTEM:CLU$PARAMS.DAT have
been copied to SYS$SYSTEM:CLU$PARAMS.OLD. You may wish to purge
SYS$SYSTEM:CLU$PARAMS.OLD.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GETDATA phase has successfully completed.
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GENPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, GENFILES phase is beginning.
%SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]PAGEFILE.SYS;1 extended
%SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]SWAPFILE.SYS;1 extended
%SYSGEN-I-CREATED, SYS$SPECIFIC:[SYSEXE]SYSDUMP.DMP;1 created
%SYSGEN-I-CREATED, DUA0:[SYS0.SYSEXE]ERRORLOG.DMP;1 created
%AUTOGEN-I-REPORT, AUTOGEN has produced some informational messages which
have been stored in the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You may
wish to review the information in that file.
%AUTOGEN-I-END, GENFILES phase has successfully completed.
%AUTOGEN-I-BEGIN, SETPARAMS phase is beginning.
%AUTOGEN-I-END, SETPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, REBOOT phase is beginning.
The system is shutting down to allow the system to boot with the
generated site-specific parameters and installed images.
The system will automatically reboot after the shutdown and the
installation will be complete.
SHUTDOWN -- Perform an Orderly System Shutdown
%SHUTDOWN-I-BOOTCHECK, performing reboot consistency check...
%SHUTDOWN-I-CHECKOK, basic reboot consistency check completed
%SHUTDOWN-I-OPERATOR, this terminal is now an operator's console
%OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running
%SHUTDOWN-I-DISLOGINS, interactive logins will now be disabled
%SET-I-INTSET, login interactive limit = 0, current interactive value = 0
%SHUTDOWN-I-STOPQUEUES, the queues on this node will now be stopped
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
-RMS-E-FNF, file not found
SHUTDOWN message from user SYSTEM at Batch 17:20:37
The system will shut down in 0 minutes; back up SOON. Please log off.
Reboot system with AUTOGENerated parameters
%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
%OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running
%OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running
?06 HLT INST
PC = 8443B709
Loading system software.
(BOOT/R5:0 DUA0
2..
-DUA0
1..0..
%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped
%SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk
%SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS
OpenVMS (TM) VAX Version V7.3 Major version id = 1 Minor version id = 0
%DECnet-I-LOADED, network base image loaded, version = 05.0E.00
%DECnet-W-NOOPEN, could not open SYS$SYSROOT:[SYSEXE]NET$CONFIG.DAT
%WBM-I-WBMINFO Write Bitmap has successfully completed initialization.
*****************************************************************
OpenVMS VAX V7.3
You have SUCCESSFULLY installed the OpenVMS VAX Operating System.
The system is now executing the STARTUP procedure. Please
wait for the completion of STARTUP before logging in to the
system.
*****************************************************************
%STDRV-I-STARTUP, OpenVMS startup begun at 27-DEC-2020 17:21:23.19
%RUN-S-PROC_ID, identification of created process is 00000206
%DCL-S-SPAWNED, process SYSTEM_1 spawned
%%%%%%%%%%% OPCOM 27-DEC-2020 17:21:31.87 %%%%%%%%%%%
Operator _VAX$OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 27-DEC-2020 17:21:31.88 %%%%%%%%%%%
Operator status for operator _VAX$OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%%%%%%%%%%% OPCOM 27-DEC-2020 17:21:31.88 %%%%%%%%%%%
Logfile has been initialized by operator _VAX$OPA0:
Logfile is VAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
%%%%%%%%%%% OPCOM 27-DEC-2020 17:21:31.88 %%%%%%%%%%%
Operator status for operator VAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%%%%%%%%%%% OPCOM 27-DEC-2020 17:21:32.09 %%%%%%%%%%%
Message from user AUDIT$SERVER on VAX
%AUDSRV-I-NEWSERVERDB, new audit server database created
%%%%%%%%%%% OPCOM 27-DEC-2020 17:21:32.22 %%%%%%%%%%%
Message from user AUDIT$SERVER on VAX
%AUDSRV-I-REMENABLED, resource monitoring enabled for journal SECURITY
%%%%%%%%%%% OPCOM 27-DEC-2020 17:21:32.22 %%%%%%%%%%%
Message from user AUDIT$SERVER on VAX
%AUDSRV-I-NEWOBJECTDB, new object database created
%SET-I-NEWAUDSRV, identification of new audit server process is 0000020C
%%%%%%%%%%% OPCOM 27-DEC-2020 17:21:32.42 %%%%%%%%%%%
Message from user JOB_CONTROL on VAX
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 27-DEC-2020 17:21:32.42 %%%%%%%%%%%
Message from user JOB_CONTROL on VAX
-RMS-E-FNF, file not found
%LICENSE-F-EMTLDB, license database contains no license records
%%%%%%%%%%% OPCOM 27-DEC-2020 17:21:33.07 %%%%%%%%%%%
Message from user SYSTEM on VAX
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 27-DEC-2020 17:21:33.08 %%%%%%%%%%%
Message from user SYSTEM on VAX
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 27-DEC-2020 17:21:33.10 %%%%%%%%%%%
Message from user SYSTEM on VAX
%SECSRV-I-CIACRECLUDB, security server created cluster intrusion database
%%%%%%%%%%% OPCOM 27-DEC-2020 17:21:33.14 %%%%%%%%%%%
Message from user SYSTEM on VAX
%SECSRV-I-SERVERSTARTINGU, security server starting up
%%%%%%%%%%% OPCOM 27-DEC-2020 17:21:33.17 %%%%%%%%%%%
Message from user SYSTEM on VAX
%SECSRV-I-CIASTARTINGUP, breakin detection and evasion processing now starting up
Copyright 2000 Compaq Computer Corporation. All rights reserved.
%NET$STARTUP-W-NONETCONFIG, this node has not been configured to run DECnet-Plus for OpenVMS
use SYS$MANAGER:NET$CONFIGURE.COM if you wish to configure DECnet
%NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is OFF
%%%%%%%%%%% OPCOM 27-DEC-2020 17:21:35.72 %%%%%%%%%%%
Message from user SYSTEM on VAX
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
Startup processing continuing...
%DECdtm-F-NODECnet, the TP_SERVER process was not started because either:
o DECnet-Plus is not started or is not configured, or
o The SYS$NODE_FULLNAME logical name is not defined
This could be because when you installed DECnet-Plus and were prompted
for the system's full name, you specified a local name instead of a
DECdns or Domain name.
If you want to use DECdtm services, make sure that DECnet-Plus is started and
configured and that SYS$NODE_FULLNAME is defined, then use the following
command to start the TP_SERVER process:
$ @SYS$STARTUP:DECDTM$STARTUP.COM
%%%%%%%%%%% OPCOM 27-DEC-2020 17:21:36.27 %%%%%%%%%%%
Message from user AUDIT$SERVER on VAX
Security alarm (SECURITY) and security audit (SECURITY) on VAX, system id: 1300
Auditable event: Audit server starting up
Event time: 27-DEC-2020 17:21:36.22
PID: 00000203
Username: SYSTEM
%STARTUP-I-AUDITCONTINUE, audit server initialization complete
The OpenVMS VAX system is now executing the site-specific startup commands.
%%%%%%%%%%% OPCOM 27-DEC-2020 17:21:36.56 %%%%%%%%%%%
Message from user AUDIT$SERVER on VAX
Security alarm (SECURITY) and security audit (SECURITY) on VAX, system id: 1300
Auditable event: Identifier added
Event time: 27-DEC-2020 17:21:36.55
PID: 00000203
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: VAX$DUA0:[SYS0.SYSCOMMON.][SYSEXE]AUTHORIZE.EXE
Identifier name: SYS$NODE_VAX
Identifier value: %X80010000
Attributes: none
%UAF-I-RDBADDMSG, identifier SYS$NODE_VAX value %X80010000 added to rights database
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
SYSTEM job terminated at 27-DEC-2020 17:21:37.10
Accounting information:
Buffered I/O count: 1616 Peak working set size: 1558
Direct I/O count: 610 Peak page file size: 5504
Page faults: 6059 Mounted volumes: 0
Charged CPU time: 0 00:00:11.52 Elapsed time: 0 00:00:15.11
Welcome to OpenVMS (TM) VAX Operating System, Version V7.3
Username:
===== Erster Login und Installation des TCP/IP Protokoll-Stapels =====
Installation des TCP/IP Protokoll-Stapels. Dieser befindet sich auch auf dem Installationsimage von OpenVMS 7.3. Trotzdem muss er wie bei ULTRIX nachträglich installiert werden, weil DEC in der Standardinstallation primär auf ihr eigenes DECnet setzen.
Dazu muss die virtuelle Installations-CD wieder gemountet werden.
$ mount /over=id dua2
%MOUNT-I-WRITELOCK, volume is write locked
%MOUNT-I-MOUNTED, VAXVMS073 mounted on _VAX$DUA2:
Mit dem Befehl "show dev dua2" lässt sich der Status des Laufwerks abrufen.
$ show dev dua2
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
VAX$DUA2: Mounted alloc 0 VAXVMS073 246480 1 1
wrtlck
Auf die oberste Verzeichnisebene des CD-ROM-Laufwerks wechseln und sich den Verzeichnisinhalt ausgeben lassen.
$ set def dua2:[000000]
$ dir
Directory DUA2:[000000]
000000.DIR;1 BACKUP.SYS;1 BADBLK.SYS;1 BADLOG.SYS;1
BITMAP.SYS;1 CONTIN.SYS;1 CORIMG.SYS;1 DCE_VAX030.DIR;1
DECNET_PHASE_IV_VAX073.DIR;1 DECNET_PLUS_VAX073.DIR;1
DECW073.C;1 DECW073.D;1 DECW073.E;1 DECW073.F;1
DOCUMENTATION.DIR;1 DWMOTIF_VAX125.DIR;1 DWMOTIF_VAX126.DIR;1
HELP_MESSAGE.DIR;1 INDEXF.SYS;1 ISL_SCRIPT.ESS;1 KERBEROS_VAX010.DIR;1
KITS.DIR;1 SECURITY.SYS;1 SYS0.DIR;1 SYS1.DIR;1
TCPIP_VAX051.DIR;1 VAX073.DIR;1 VMS073.A;1 VMS073.B;1
VMS073.C;1 VMS073.D;1 VMS073.E;1 VMS073.F;1
VMSI18N_VAX073.DIR;1 VOLSET.SYS;1
Total of 35 files.
In das Unterverzeichnis TCPIP_VAX051 wechseln und wieder sich den Inhalt anzeigen lassen. Die Prozedur wieder auf das Unterverzeichnis KIT.DIR;1 anwenden.
$ set def [TCPIP_VAX051]
$ dir
Directory DUA2:[TCPIP_VAX051]
DOCUMENTATION.DIR;1 KIT.DIR;1
Total of 2 files.
$ set def [.KIT]
$ dir
Directory DUA2:[TCPIP_VAX051.KIT]
DEC-VAXVMS-TCPIP-V0501-15-1.PCSI;1
Total of 1 file.
In diesem Unterverzeichnis befindet sich nun nur eine PCSI-Datei. **PCSI** (für **P**OLYCENTER **S**oftware **I**nstallation **u**tility) ist ein Programm, um unter VMS mehrschichtige Softwareprodukte zu installieren, Entfernen und zu Verwalten. Da sich wie gesagt nur diese eine Datei auf dieser Verzeichnisebene befindet, reicht lediglich ein Stern als Wildcard, um diese mit dem Befehl **product** auszuführen.
$ product install *
The following product has been selected:
DEC VAXVMS TCPIP V5.1-15 Layered Product
Do you want to continue? [YES] [Return]
Configuration phase starting ...
You will be asked to choose options, if any, for each selected product and for
any products that may be installed to satisfy software dependency requirements.
DEC VAXVMS TCPIP V5.1-15: Compaq TCP/IP Services for OpenVMS.
(c) Compaq Computer Corporation 2000. All Rights Reserved.
Compaq Computer Corporation
Compaq TCP/IP Services for OpenVMS offers several license options.
Do you want the defaults for all options? [YES] [Return]
Do you want to review the options? [NO] [Return]
Execution phase starting ...
The following product will be installed to destination:
DEC VAXVMS TCPIP V5.1-15 DISK$OPENVMS:[VMS$COMMON.]
Portion done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%
%PCSI-I-PRCOUTPUT, output from subprocess follows ...
% - HELP has been updated. You may purge SYS$COMMON:[SYSHLP]HELPLIB.HLB
%
%PCSI-I-PRCOUTPUT, output from subprocess follows ...
% TCPIP-W-PCSI_INSTALL
% - Execute SYS$MANAGER:TCPIP$CONFIG.COM to proceed with configuration of
% Compaq TCP/IP Services.
%
Portion done: 100%
The following product has been installed:
DEC VAXVMS TCPIP V5.1-15 Layered Product
DEC VAXVMS TCPIP V5.1-15: Compaq TCP/IP Services for OpenVMS.
Check the release notes for current status of the product.
$
===== Ausführen von DECwindows Motif =====
Auf dem Hostsystem ist dafür das Paket für den Display-Server Xephyr zu installieren.
# apt-get install xserver-xephyr
Auf dem Linux-Host ist dann Xephyr wie folgt zu starten.
$ Xephyr -screen 980x640 -ac -query 192.168.0.11 :3
===== Links =====
* [[https://www.youtube.com/playlist?list=PLV52TizBXn9kLlIMFufybf1FItJauh_Yb|YouTube-Playlist: SimH OpenVMS VAX (Stephen's Machine Room)]]
* https://www.wherry.com/gadgets/retrocomputing/vax-simh.html
* https://wiki.vmssoftware.com/PCSI
* http://www.vaxhaven.com/VaxHaven