Установка VAX/VMS V5.5-2H4

VAX

Posted by Unik on 23.02.2022

Понадобилось мне установить в SIMH - VMS версии 5.5. Оказалось что в сети нет лога установки этой ОС поэтому размещаю свой. Хоть это и не по теме блога, но VAX то же интересная система которая является развитием PDP11. Образ установочного диска можно взять здесь и лучше брать сразу V5.5-2H4 с уже установленными патчами.

Конфигурация SIMH для VAX8600 у меня такая:

set cpu 64M
set cpu idle=vms
set cpu model=8650

set rq0 ra92
attach RQ0 rq0-ra92.dsk
set rq1 ra92
;attach RQ1 kits-ra92.dsk
set rq3 cdrom
attach RQ3 -r VMS552h4.iso

set rp disable
set rl disable
set hk disable
set ry disable
set tu disable
set ts disable
set tq disable
set dz disable
set lpt disable

set xu enable
set xu mac=08-00-2b-00-00-0a
attach xu eth4

Сначала нужно загрузиться с CD для того чтобы развернуть бэкап, затем нужно перезагрузить систему и продолжить установку уже с HDD. Вся сложность тут это узнать имя файла бэкапа, в данном случае это - VMS2H4055.B

sim> b rq3
%SIM-INFO: Loading boot code from internal vmb.exe

   VAX/VMS Version V5.5-2H4 Major version id = 1 Minor version id = 0

PLEASE ENTER DATE AND TIME (DD-MMM-YYYY  HH:MM)  23-FEB-2022

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 RD54
Available device  DUA3:                            device type RRD40

Enter "YES" when all needed devices are available: yes

%BACKUP-I-IDENT, Stand-alone BACKUP V5.5-2; the date is 23-FEB-2022 00:02:07.16
$ BACKUP DUA3:VMS2H4055.B/SAVE_SET DUA0:

%BACKUP-I-PROCDONE, operation completed.  Processing finished at 23-FEB-2022 00:02:33.51
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: 
Simulation stopped, PC: 83BD94DF (BBC #3,26C(R3),83BD951C)
sim> boot rq0
%SIM-INFO: Loading boot code from internal vmb.exe

   VAX/VMS Version BI55-2H4 Major version id = 1 Minor version id = 0

PLEASE ENTER DATE AND TIME (DD-MMM-YYYY  HH:MM)  23-FEB-2022 15:20

                VAX/VMS V5.5-2H4 Installation Procedure

                         Model: VAX 8650
                 System device: RA92 - _DUA0:
                   Free Blocks: 2889585
                      CPU type: 04-00

* Please enter the date and time (DD-MMM-YYYY HH:MM) 23-feb-2022 15:20

%STDRV-I-STARTUP, VMS startup begun at 23-FEB-2022 15:20:00.01 %%%%%%%%%%% OPCOM 23-FEB-2022 15:20:00.39 %%%%%%%%%%% Operator _OPA0: has 
been enabled, username SYSTEM

%%%%%%%%%%% OPCOM 23-FEB-2022 15:20:00.39 %%%%%%%%%%% 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 23-FEB-2022 15:20:00.39 %%%%%%%%%%% Logfile has been initialized by operator _OPA0: Logfile is 
SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1

%%%%%%%%%%% OPCOM 23-FEB-2022 15:20:00.40 %%%%%%%%%%% 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

%%%%%%%%%%% OPCOM 23-FEB-2022 15:20:00.44 %%%%%%%%%%% Message from user AUDIT$SERVER %AUDSRV-I-NEWSERVERDB, new audit server database 
created

%%%%%%%%%%% OPCOM 23-FEB-2022 15:20:00.48 %%%%%%%%%%% Message from user AUDIT$SERVER %AUDSRV-I-REMENABLED, resource monitoring enabled for 
journal SECURITY

%%%%%%%%%%% OPCOM 23-FEB-2022 15:20:00.48 %%%%%%%%%%% Message from user AUDIT$SERVER Security alarm (SECURITY) and security audit 
(SECURITY), system id: 65534 Auditable event: Audit server starting up Event time: 23-FEB-2022 15:20:00.48

%SET-I-NEWAUDSRV, identification of new audit server process is 00000029 %%%%%%%%%%% OPCOM 23-FEB-2022 15:20:00.54 %%%%%%%%%%% Message 
from user JOB_CONTROL %JBC-E-OPENERR, error opening SYS$SYSROOT:[SYSEXE]QMAN$MASTER.DAT;

%%%%%%%%%%% OPCOM 23-FEB-2022 15:20:00.54 %%%%%%%%%%% Message from user JOB_CONTROL -RMS-E-FNF, file not found

%LICENSE-F-EMTLDB, license database contains no license records %%%%%%%%%%% OPCOM 23-FEB-2022 15:20:02.75 %%%%%%%%%%% 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...

%%%%%%%%%%% OPCOM 23-FEB-2022 15:20:02.82 %%%%%%%%%%% Message from user AUDIT$SERVER Security alarm (SECURITY) and security audit 
(SECURITY), system id: 65534 Auditable event: Audit server shutting down Event time: 23-FEB-2022 15:20:02.82 PID: 00000023

%STDRV-I-STARTUP, VMS startup begun at 23-FEB-2022 15:20:02.90

    If this system disk is to be used in a 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 may indicate a volume label of 1 to 12 characters in length.  If you
    wish to use the default name of VAXVMS2H4055 just press RETURN in response
    to the next question.

* Enter the volume label for this system disk [VAXVMS2H4055]: 

* Enter name of drive holding the VMS distribution media: DUA3
* Is the VMS media ready to be mounted? [N] Y

%MOUNT-I-MOUNTED, VMS2H4055    mounted on _DUA3:

    Select optional software you wish to have installed.  You can choose to
    install one or more of the following VMS and/or DECwindows components:

        o VMS library                    -  32000 blocks
        o VMS optional                   -  16500 blocks
        o DECwindows device support      -  21400 blocks
        o DECwindows applications        -  12000 blocks
        o DECwindows programming support -  26500 blocks
        o DECwindows example files       -   3500 blocks

    Space remaining:  2889384 blocks

* Do you want to install the VMS library files? (Y/N) Y

    Space remaining:  2857384 blocks

* Do you want to install the VMS optional files? (Y/N) Y

    Space remaining:  2840884 blocks

    You can provide DECwindows support now, or you can use the
    DECW$TAILOR utility to provide or remove DECwindows support
    after the installation.

    NOTE: Some media, TK50s in particular, can be very slow when
    tailoring on files.  You might want to provide DECwindows
    options now and tailor off unwanted files later.

* Do you want to provide optional DECwindows support? (Y/N) N

    The following options will be provided:

        VMS library
        VMS optional

    Space remaining:  2840884 blocks

* Is this correct? (Y/N) Y

    Restoring VMS library save set ...
%BACKUP-I-STARTVERIFY, starting verification pass

    Restoring VMS optional save set ...
%BACKUP-I-STARTVERIFY, starting verification pass

    Creating [VMS$COMMON] directory tree ...

    In a cluster, you can run multiple systems sharing all files except 
    PAGEFILE.SYS, SWAPFILE.SYS, SYSDUMP.DMP and VAXVMSSYS.PAR.

* Will this node be a cluster member? (Y/N) Y

    Now configuring system to be a cluster member ...

What is the node's DECnet node name? SVAX
What is the node's DECnet node address? 1.1
Will the Ethernet be used for cluster communications (Y/N)? Y
Enter this cluster's group number: 1

Enter this cluster's password: 

Re-enter this cluster's password for verification: 

Will SVAX be a disk server (Y/N)? Y
Will SVAX serve RFxx disks [N]? 
Enter a value for SVAX's ALLOCLASS parameter: 1
Does this cluster contain a quorum disk [N]? 

    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.

* Enter password for SYSTEM: 

* Re-enter for verification: 
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for SYSTEM verified

* Enter password for SYSTEST: 

* Re-enter for verification: 
%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-MDFYMSG, user record(s) updated

* Enter password for FIELD: 

* Re-enter for verification: 
%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 data base created
%UAF-I-RDBADDMSGU, identifier DEFAULT value: [000200,000200] added to rights data base
%UAF-I-RDBADDMSGU, identifier FIELD value: [000001,000010] added to rights data base
%UAF-I-RDBADDMSGU, identifier SYSTEM value: [000001,000004] added to rights data base
%UAF-I-RDBADDMSGU, identifier SYSTEST value: [000001,000007] added to rights data base
%UAF-E-RDBADDERRU, unable to add SYSTEST_CLIG value: [000001,000007] to rights data base
-SYSTEM-F-DUPIDENT, duplicate identifier
%UAF-I-NOMODS, no modifications made to system authorization file
%UAF-I-RDBDONEMSG, rights data base modified

    After the installation finishes, you may want to do one or more of the 
    following tasks:

    o DECOMPRESS THE SYSTEM LIBRARIES - For space considerations, many of
      the system libraries are shipped in a data-compressed format.  If you
      have enough disk space, you may decompress them for faster access. To
      data expand the libraries, type:

        $ @SYS$UPDATE:LIBDECOMP.COM

      If you choose not to decompress these libraries you will experience
      slower response with the HELP and LINK commands.

    o BUILD A STANDALONE BACKUP KIT - You can build a standalone backup kit
      using the procedure described in your VMS installation and operations
      guide which is supplied for your VAX computer.

    o TAILOR THE SYSTEM DISK - You may 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.

          VMS tailoring:          $ RUN SYS$UPDATE:VMSTAILOR

          DECwindows tailoring:   $ RUN SYS$UPDATE:DECW$TAILOR

=================================================================
    Continuing with VAX/VMS V5.5-2H4 Installation Procedure.

    Configuring all devices on the system ...
%STDRV-I-STARTUP, VMS startup begun at 23-FEB-2022 15:22:28.27

   You may safely ignore the following NCP error message(s).

%NCP-W-UNRCMP, Unrecognized component , Object

    If you have Product Authorization Keys (PAKs) to register, you may
    register them now.

* Do you want to register any Product Authorization Keys? (Y/N): N

********************************************************************************

    Setting the NOMOVE attribute on critical system files.
    This will take a few minutes...

********************************************************************************

    After completion of this installation, you should set the
    NOMOVE attribute on the critical system files of all
    alternative system disks by executing the command:

        $ @SYS$SYSTEM:SETFILENOMOVE 

********************************************************************************

    After the system has rebooted you must register any Product
    Authorization Keys (PAKs) that you have received with this kit.  
    You may register these PAKs by executing the following procedure:

        $ @SYS$UPDATE:VMSLICENSE

    See the VMS License Management Utility Manual for any additional
    information you may need.

********************************************************************************

    Running AUTOGEN to compute the new SYSGEN parameters ...

%AUTOGEN-I-BEGIN, GETDATA phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.
        You may wish to purge this file.
%AUTOGEN-I-END, GETDATA phase has successfully completed.
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created.
        You may wish to purge this file.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created.
        You may wish to purge this file.
%AUTOGEN-I-END, GENPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, GENFILES phase is beginning.
%SYSGEN-I-EXTENDED, DUA0:[SYS0.SYSEXE]PAGEFILE.SYS;1 extended
%SYSGEN-I-EXTENDED, DUA0:[SYS0.SYSEXE]SWAPFILE.SYS;1 extended
%SYSGEN-I-CREATED, SYS$SYSROOT:[SYSEXE]SYSDUMP.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-JOBQUEDIS, system job queue manager is not running

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

%SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked. %SHUTDOWN-I-STOPUSER, All user processes will now be 
stopped. %SHUTDOWN-I-REMOVE, All installed images will now be removed. %SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted. 
%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 %SIM-INFO: Loading boot code from internal vmb.exe Rebooting...

   VAX/VMS Version V5.5-2H4 Major version id = 1 Minor version id = 0

waiting to form or join a VAXcluster system
%VAXcluster-I-LOADSECDB, loading the cluster security database
%MSCPLOAD-I-LOADMSCP, loading the MSCP disk server
%CNXMAN,  Proposing formation of a VAXcluster
%CNXMAN,  Now a VAXcluster member -- system SVAX
%CNXMAN,  Completing VAXcluster state transition

    ***************************************************************

    VAX/VMS V5.5-2H4

    You have SUCCESSFULLY installed the VMS 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, VMS startup begun at 23-FEB-2022 15:27:18.52 %MSCPLOAD-I-CONFIGSCAN, enabled automatic disk serving 
%MSCPLOAD-I-CONFIGSCAN, enabled automatic disk serving %%%%%%%%%%% OPCOM 23-FEB-2022 15:27:20.31 %%%%%%%%%%% Operator _SVAX$OPA0: has been 
enabled, username SYSTEM

%%%%%%%%%%% OPCOM 23-FEB-2022 15:27:20.32 %%%%%%%%%%% Operator status for operator _SVAX$OPA0: CENTRAL, PRINTER, TAPES, DISKS, DEVICES, 
CARDS, NETWORK, CLUSTER, SECURITY, LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12

%%%%%%%%%%% OPCOM 23-FEB-2022 15:27:20.32 %%%%%%%%%%% Logfile has been initialized by operator _SVAX$OPA0: Logfile is 
SVAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1

%%%%%%%%%%% OPCOM 23-FEB-2022 15:27:20.32 %%%%%%%%%%% Operator status for operator SVAX::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 23-FEB-2022 15:27:20.32 %%%%%%%%%%% 15:27:17.35 Node SVAX (csid 00000000) proposed formation of a VAXcluster

%%%%%%%%%%% OPCOM 23-FEB-2022 15:27:20.33 %%%%%%%%%%% 15:27:17.35 Node SVAX (csid 00010001) is now a VAXcluster member

%%%%%%%%%%% OPCOM 23-FEB-2022 15:27:20.33 %%%%%%%%%%% 15:27:17.35 Node SVAX (csid 00010001) completed VAXcluster state transition

%%%%%%%%%%% OPCOM 23-FEB-2022 15:27:20.45 %%%%%%%%%%% Message from user AUDIT$SERVER on SVAX Security alarm (SECURITY) and security audit 
(SECURITY) on SVAX, system id: 1025 Auditable event: Audit server starting up Event time: 23-FEB-2022 15:27:20.44

%SET-I-NEWAUDSRV, identification of new audit server process is 2020020D %%%%%%%%%%% OPCOM 23-FEB-2022 15:27:20.54 %%%%%%%%%%% Message 
from user JOB_CONTROL on SVAX %JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;

%%%%%%%%%%% OPCOM 23-FEB-2022 15:27:20.54 %%%%%%%%%%% Message from user JOB_CONTROL on SVAX -RMS-E-FNF, file not found

%LICENSE-F-EMTLDB, license database contains no license records %%%%%%%%%%% OPCOM 23-FEB-2022 15:27:23.07 %%%%%%%%%%% Message from user 
SYSTEM on SVAX %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...

%%%%%%%%%%% OPCOM 23-FEB-2022 15:27:23.08 %%%%%%%%%%% Message from user SYSTEM on SVAX %LICENSE-E-NOAUTH, DEC VAXCLUSTER 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 VAXCLUSTER 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...

%%%%%%%%%%%  OPCOM  23-FEB-2022 15:27:23.20  %%%%%%%%%%%
Message from user SYSTEM on SVAX
Warning: DECdtm log file not found (SYS$JOURNAL:SYSTEM$SVAX.LM$JOURNAL)
        %RMS-E-FNF, file not found
        TP server process waiting

%%%%%%%%%%% OPCOM 23-FEB-2022 15:27:23.74 %%%%%%%%%%% Message from user AUDIT$SERVER on SVAX Security alarm (SECURITY) and security audit 
(SECURITY) on SVAX, system id: 1025 Auditable event: Identifier added Event time: 23-FEB-2022 15:27:23.73 PID: 20200204 Username: SYSTEM 
Image name: $1$DUA0:[SYS0.SYSCOMMON.][SYSEXE]AUTHORIZE.EXE Identifier name: SYS$NODE_SVAX Identifier value: %X80010000 New attributes: 
none

%UAF-I-RDBADDMSG, identifier SYS$NODE_SVAX value: %X80010000 added to rights data base
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
  23-FEB-2022 15:27:23
  SYSTEM       job terminated at 23-FEB-2022 15:27:23.99

  Accounting information:
  Buffered I/O count:            1309         Peak working set size:     765
  Direct I/O count:               595         Peak page file size:      3695
  Page faults:                   4641         Mounted volumes:             0
  Charged CPU time:           0 00:00:02.19   Elapsed time:     0 00:00:05.91

        Welcome to VAX/VMS V5.5-2H4

Username: SYSTEM

Password: 
%LICENSE-I-NOLICENSE, no license is active for this software product
%LOGIN-I-NOVAXCLUSTER, DEC VAXCLUSTER license is not active
%LOGIN-S-LOGOPRCON, login allowed from OPA0:
        Welcome to VAX/VMS version V5.5-2H4

 $ CREATE VMS_PAKS.COM
[skip]
Ctrl+Z

 $ @VMS_PAKS.COM

%LICENSE-I-LOADED, DEC VAX-VMS was successfully loaded with 0 units
%LICENSE-I-LOADED, DEC BASIC was successfully loaded with 0 units
%LICENSE-I-LOADED, DEC C was successfully loaded with 0 units
%LICENSE-I-LOADED, DEC COBOL was successfully loaded with 0 units
%LICENSE-I-LOADED, DEC DTR was successfully loaded with 0 units
%LICENSE-I-LOADED, DEC DVNETEND was successfully loaded with 0 units
%LICENSE-I-LOADED, DEC DVNETEXT was successfully loaded with 0 units
%LICENSE-I-LOADED, DEC DVNETRTG was successfully loaded with 0 units
%LICENSE-I-LOADED, DEC FORTRAN was successfully loaded with 0 units
%LICENSE-I-LOADED, DEC MACRO64 was successfully loaded with 0 units
%LICENSE-I-LOADED, DEC OPENVMS-HOBBYIST was successfully loaded with 0 units
%LICENSE-I-LOADED, DEC PASCAL was successfully loaded with 0 units
%LICENSE-I-LOADED, DEC VAXCLUSTER was successfully loaded with 0 units
%LICENSE-I-LOADED, DEC VMSCLUSTER was successfully loaded with 0 units
%LICENSE-I-LOADED, DEC UCX was successfully loaded with 0 units

 $ SHUTDOWN

    SHUTDOWN -- Perform an Orderly System Shutdown
                on node SVAX

%SHUTDOWN-I-OPERATOR, This terminal is now an operator's console. %%%%%%%%%%% OPCOM 23-FEB-2022 15:31:18.95 %%%%%%%%%%% Operator status 
for operator _SVAX$OPA0: CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY, LICENSE, OPER1, OPER2, OPER3, OPER4, 
OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12

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

SHUTDOWN message on SVAX from user SYSTEM at _SVAX$OPA0:   15:31:19
SVAX will shut down in 0 minutes; back up LATER.  Please log off node SVAX.
SHUTDOWN

1 terminal has been notified on SVAX.

%SHUTDOWN-I-STOPUSER, All user processes will now be stopped.
%SHUTDOWN-I-REMOVE, All installed images will now be removed.
%SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted.
%SHUTDOWN-I-STOPAUDIT, stopping the audit server
%%%%%%%%%%%  OPCOM  23-FEB-2022 15:31:19.24  %%%%%%%%%%%
Message from user AUDIT$SERVER on SVAX
Security alarm (SECURITY) and security audit (SECURITY) on SVAX, system id: 1025

Auditable event: Audit server shutting down Event time: 23-FEB-2022 15:31:19.21 PID: 20200213

%%%%%%%%%%% OPCOM 23-FEB-2022 15:31:19.25 %%%%%%%%%%% Message from user SYSTEM on SVAX _SVAX$OPA0:, SVAX shutdown was requested by the 
operator.

%%%%%%%%%%% OPCOM 23-FEB-2022 15:31:19.26 %%%%%%%%%%% Logfile was closed by operator _SVAX$OPA0: Logfile was 
SVAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1

%%%%%%%%%%% OPCOM 23-FEB-2022 15:31:19.27 %%%%%%%%%%% Operator _SVAX$OPA0: has been disabled, username SYSTEM

    SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM

Infinite loop, PC: 80262022 (BRB 80262022)
sim> Q

Как показано выше, после установки лучше сразу установить необходимые лицензии, а вот где их взять не подскажу, у меня они уже давно. В следующей части покажу установку и настройку TCP/IP + DECNET.