Ну... в первой попытке слегка напортачил :) Вторая была успешней :)
KA630-A.V1.3
Performing normal system tests.
7..6..5..4..3..
Tests completed.
>>> boo dua1
2..1..0..
VAX/VMS Version V5.5-2 Major version id = 1 Minor version id = 0
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 09-NOV-2020 18:31
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 RD53
Available device DUA1: device type RRD40
Enter "YES" when all needed devices are available: yes
%BACKUP-I-IDENT, Stand-alone BACKUP V5.5-2; the date is 9-NOV-2020 18:35:30.43
$ backup/image dua1:vms2055.b/save_set dua0:
%BACKUP-I-PROCDONE, operation completed. Processing finished at 9-NOV-2020 18:
41:19.62
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:
KA630-A.V1.3
Performing normal system tests.
7..6..5..4..3..
Tests completed.
>>> boo dua0
2..1..0..
VAX/VMS Version BI55-2 Major version id = 1 Minor version id = 0
VAX/VMS V5.5-2 Installation Procedure
Model: MicroVAX II
System device: RD53 - _DUA0:
Free Blocks: 154446
CPU type: 08-01
* Please enter the date and time (DD-MMM-YYYY HH:MM) 09-NOV-2020 18:46
%STDRV-I-STARTUP, VMS startup begun at 9-NOV-2020 18:46:00.46
%%%%%%%%%%% OPCOM 9-NOV-2020 18:46:51.47 %%%%%%%%%%%
Operator _OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 9-NOV-2020 18:46:51.72 %%%%%%%%%%%
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 9-NOV-2020 18:46:52.22 %%%%%%%%%%%
Logfile has been initialized by operator _OPA0:
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
%%%%%%%%%%% OPCOM 9-NOV-2020 18:46:52.25 %%%%%%%%%%%
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
%SET-I-NEWAUDSRV, identification of new audit server process is 00000029
%%%%%%%%%%% OPCOM 9-NOV-2020 18:46:57.00 %%%%%%%%%%%
Message from user AUDIT$SERVER
%AUDSRV-I-NEWSERVERDB, new audit server database created
%%%%%%%%%%% OPCOM 9-NOV-2020 18:47:03.28 %%%%%%%%%%%
Message from user JOB_CONTROL
%JBC-E-OPENERR, error opening SYS$SYSROOT:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 9-NOV-2020 18:47:03.69 %%%%%%%%%%%
Message from user JOB_CONTROL
-RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 9-NOV-2020 18:47:05.19 %%%%%%%%%%%
Message from user AUDIT$SERVER
%AUDSRV-I-REMENABLED, resource monitoring enabled for journal SECURITY
%%%%%%%%%%% OPCOM 9-NOV-2020 18:47:06.21 %%%%%%%%%%%
Message from user AUDIT$SERVER
Security alarm (SECURITY) and security audit (SECURITY), system id: 65534
Auditable event: Audit server starting up
Event time: 9-NOV-2020 18:47:05.18
%LICENSE-F-EMTLDB, license database contains no license records
%%%%%%%%%%% OPCOM 9-NOV-2020 18:47:24.93 %%%%%%%%%%%
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 9-NOV-2020 18:47:32.26 %%%%%%%%%%%
Message from user AUDIT$SERVER
Security alarm (SECURITY) and security audit (SECURITY), system id: 65534
Auditable event: Audit server shutting down
Event time: 9-NOV-2020 18:47:32.12
PID: 00000023
%STDRV-I-STARTUP, VMS startup begun at 9-NOV-2020 18:47:39.46
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 VAXVMSV2055 just press RETURN in response
to the next question.
* Enter the volume label for this system disk [VAXVMSV2055]: TEST01
* Enter name of drive holding the VMS distribution media: DUA1:
* Is the VMS media ready to be mounted? [N] Y
%MOUNT-I-MOUNTED, VMS2055 mounted on _DUA1:
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: 154245 blocks
* Do you want to install the VMS library files? (Y/N) y
Space remaining: 122245 blocks
* Do you want to install the VMS optional files? (Y/N) y
Space remaining: 105745 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: 105745 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) 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 dat
a 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 dat
a base
%UAF-E-RDBADDERRU, unable to add SYSTEST_CLIG value: [000001,000007] to rights d
ata 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-2 Installation Procedure.
Configuring all devices on the system ...
%STDRV-I-STARTUP, VMS startup begun at 9-NOV-2020 19:03:58.75
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 <alternative_system_disk>
************************************************** ******************************
After the system has rebooted you should register any additional
Product Authorization Keys (PAKs) you have, or receive in the
future, 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 19:31:20
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
Loading system software.
2..1..0..
VAX/VMS Version V5.5-2 Major version id = 1 Minor version id = 0
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM)
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 09-NOV-2020 19:32
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 RD53
Available device DUA1: device type RRD40
Enter "YES" when all needed devices are available: YES
%BACKUP-I-IDENT, Stand-alone BACKUP V5.5-2; the date is 9-NOV-2020 19:34:26.97
$
KA630-A.V1.3
Performing normal system tests.
7..6..5..4..3..
Tests completed.
>>> BOO DUA0
2..1..0..
VAX/VMS Version V5.5-2 Major version id = 1 Minor version id = 0
************************************************** *************
VAX/VMS V5.5-2
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 9-NOV-2020 19:38:29.03
The VAX/VMS system is now executing the system startup procedure.
%%%%%%%%%%% OPCOM 9-NOV-2020 19:39:54.46 %%%%%%%%%%%
Operator _OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 9-NOV-2020 19:39:54.60 %%%%%%%%%%%
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 9-NOV-2020 19:39:55.18 %%%%%%%%%%%
Logfile has been initialized by operator _OPA0:
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
%%%%%%%%%%% OPCOM 9-NOV-2020 19:39:55.21 %%%%%%%%%%%
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
%SET-I-NEWAUDSRV, identification of new audit server process is 0000002A
%%%%%%%%%%% OPCOM 9-NOV-2020 19:40:01.96 %%%%%%%%%%%
Message from user AUDIT$SERVER
Security alarm (SECURITY) and security audit (SECURITY), system id: 65534
Auditable event: Audit server starting up
Event time: 9-NOV-2020 19:40:00.53
%%%%%%%%%%% OPCOM 9-NOV-2020 19:40:04.15 %%%%%%%%%%%
Message from user JOB_CONTROL
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 9-NOV-2020 19:40:04.26 %%%%%%%%%%%
Message from user JOB_CONTROL
-RMS-E-FNF, file not found
%LICENSE-F-EMTLDB, license database contains no license records
%%%%%%%%%%% OPCOM 9-NOV-2020 19:40:22.51 %%%%%%%%%%%
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 9-NOV-2020 19:40:26.58 %%%%%%%%%%%
Message from user SYSTEM
Warning: DECdtm log file not found (SYS$JOURNAL:SYSTEM$.LM$JOURNAL)
%RMS-E-FNF, file not found
TP server process waiting
The VAX/VMS system is now executing the site-specific startup commands.
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
9-NOV-2020 19:40:33
SYSTEM job terminated at 9-NOV-2020 19:40:49.91
Accounting information:
Buffered I/O count: 1234 Peak working set size: 653
Direct I/O count: 638 Peak page file size: 3310
Page faults: 3721 Mounted volumes: 0
Charged CPU time: 0 00:01:26.95 Elapsed time: 0 00:02:48.25
Welcome to VAX/VMS V5.5-2
Username: SYSTEM
Password:
User authorization failure
Username: SYSTEM
Password:
%LICENSE-I-NOLICENSE, no license is active for this software product
%LOGIN-S-LOGOPRCON, login allowed from OPA0:
Welcome to VAX/VMS version V5.5-2
1 failure since last successful login
$ HELP SHOW MEME
*INTERRUPT*
$ SHOW MEM
System Memory Resources on 9-NOV-2020 19:44:36.32
SHOW MEMORY Subtopic?
*INTERRUPT*
$
- - - Добавлено - - -
Потом надо было лицухи добавить и в результате система уже на материЦЦо :)
KA630-A.V1.3
Performing normal system tests.
7..6..5..4..3..
Tests completed.
>>> BOO DUA0
2..1..0..
VAX/VMS Version V5.5-2 Major version id = 1 Minor version id = 0
$! Copyright (c) 1992 Digital Equipment Corporation. All rights reserved.
%STDRV-I-STARTUP, VMS startup begun at 9-NOV-2020 20:34:48.79
The VAX/VMS system is now executing the system startup procedure.
%%%%%%%%%%% OPCOM 9-NOV-2020 20:36:13.95 %%%%%%%%%%%
Operator _OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 9-NOV-2020 20:36:14.15 %%%%%%%%%%%
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 9-NOV-2020 20:36:15.00 %%%%%%%%%%%
Logfile has been initialized by operator _OPA0:
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;3
%%%%%%%%%%% OPCOM 9-NOV-2020 20:36:15.02 %%%%%%%%%%%
Operator status for operator SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;3
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%SET-I-NEWAUDSRV, identification of new audit server process is 0000002A
%%%%%%%%%%% OPCOM 9-NOV-2020 20:36:20.44 %%%%%%%%%%%
Message from user AUDIT$SERVER
Security alarm (SECURITY) and security audit (SECURITY), system id: 65534
Auditable event: Audit server starting up
Event time: 9-NOV-2020 20:36:19.08
%%%%%%%%%%% OPCOM 9-NOV-2020 20:36:22.95 %%%%%%%%%%%
Message from user JOB_CONTROL
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 9-NOV-2020 20:36:23.05 %%%%%%%%%%%
Message from user JOB_CONTROL
-RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 9-NOV-2020 20:36:47.85 %%%%%%%%%%%
Message from user SYSTEM
Warning: DECdtm log file not found (SYS$JOURNAL:SYSTEM$.LM$JOURNAL)
%RMS-E-FNF, file not found
TP server process waiting
The VAX/VMS system is now executing the site-specific startup commands.
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
9-NOV-2020 20:36:55
SYSTEM job terminated at 9-NOV-2020 20:37:13.86
Accounting information:
Buffered I/O count: 881 Peak working set size: 669
Direct I/O count: 519 Peak page file size: 3228
Page faults: 2691 Mounted volumes: 0
Charged CPU time: 0 00:01:14.12 Elapsed time: 0 00:02:28.65
Welcome to VAX/VMS V5.5-2
Username: SYSTEM
Password:
Welcome to VAX/VMS version V5.5-2
Last interactive login on Monday, 9-NOV-2020 20:27
$