This appendix provides a sample installation log for VSI OpenVMS x86-64 V9.2-3 installation.
A.1. Sample Installation LogBelow is the sample installation log.
%%%%%%%%%%% VSI OpenVMS (tm) x86-64 Console %%%%%%%%%%%
_______________________________________________
THE GUEST CONSOLE HAS BEEN SUSPENDED
USE A TERMINAL UTILITY FOR OPA0 ACCESS
_______________________________________________
VSI Primary Kernel SYSBOOT
%SYSBOOT-I-VMTYPE, Booting as a VMware (tm) Guest
VMS Software, Inc. OpenVMS (TM) x86_64 Operating System, V9.2-3
Copyright 2024 VMS Software, Inc.
MDS Mitigation active, variant verw(MD_CLEAR)
%SMP-I-CPUTRN, CPU #1 has joined the active set.
%SMP-I-CPUTRN, CPU #5 has joined the active set.
%SMP-I-CPUTRN, CPU #2 has joined the active set.
%SMP-I-CPUTRN, CPU #3 has joined the active set.
%SMP-I-CPUTRN, CPU #4 has joined the active set.
Installing required known files...
Configuring devices...
%EIA0, Link up: 1000 mbit, 00-0C-29-80-62-C9
****************************************************************
You can install or upgrade the OpenVMS X86-64 operating system
or you can install or upgrade layered products that are included
on the OpenVMS X86-64 distribution media.
You can also execute DCL commands and procedures to perform
"standalone" tasks, such as backing up the system disk.
Please choose one of the following:
1) Upgrade, install or reconfigure OpenVMS X86-64 Version V9.2-3
2) Display layered products that this procedure can install
3) Install or upgrade layered products
4) Show installed products
5) Reconfigure installed products
6) Remove installed products
7) Find, Install or Undo patches; Show or Delete Recovery Data
8) Execute DCL commands and procedures
9) Shut down this system
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/9/?) 1
***********************************************************
This procedure will ask a series of questions.
() - encloses acceptable answers
[] - encloses default answers
Type your response and press the <Return> key. Type:
? - to repeat an explanation
^ - to change prior input (not always possible)
Ctrl/Y - to exit the installation procedure
There are two choices for installation/upgrade:
Initialize - Removes all software and data files that were
previously on the target disk and installs OpenVMS X86-64.
Preserve -- Installs or Upgrades OpenVMS X86-64 on the target disk
and retains all other contents of the target disk.
* Note: You cannot use preserve to install OpenVMS X86-64 on a disk on
which any other operating system is installed. This includes
implementations of OpenVMS for other architectures.
Do you want to INITIALIZE or to PRESERVE? [PRESERVE] init
You must enter the device name for the target disk on which
OpenVMS X86-64 will be installed.
Enter device name for target disk: (? for choices) ?
Device Name Device Type Name Volume Label Size (blocks/xB)
------------ ------------------------- -------------- --------------------
DKA0: VMware Virtual disk
DKA300: VMware Virtual disk
For volume label and device size enter ??
Enter device name for target disk: (? for choices) DKA0
DKA0: is now labeled X86SYS.
Do you want to keep this label? (Yes/No) [Yes]
OpenVMS V9.0 and later requires that the target system disk be
initialized with On-Disk Structure Level 5 (ODS-5).
Hard links can be enabled on ODS-5 disks. WBEM Services for OpenVMS
does not require hard links. (? for more information)
Do you want to enable hard links? (Yes/No/?) y
You have chosen to install OpenVMS X86-64 on a new disk.
The target system disk, DKA0:, will be initialized
with structure level 5 (ODS-5).
Hard links WILL be enabled.
The disk will be labeled X86SYS.
Any data currently on the target system disk will be lost.
Is this OK? (Yes/No) y
Initializing and mounting target....
Creating page file....
Boot options in the EFI Boot Manager boot option menu can provide a
convenient way to boot your system. The installation procedure can
automatically create a new boot option (if none exists) or validate
existing boot options.
Do you want to create or validate boot options? (Yes/No) [Yes]
You must enter a password for the SYSTEM account.
The password must be a minimum of 15 characters in length, and
may not exceed 31 characters. It will be checked and verified.
The system will not accept passwords that can be guessed easily.
The password will not be displayed as you enter it.
Password for SYSTEM account:
Re-enter SYSTEM password for verification:
For your system to operate properly, you must set two parameters:
SCSNODE and SCSSYSTEMID.
SCSNODE can be from 1 to 6 letters or numbers. It must contain at
least one letter.
If you plan to use DECnet, SCSNODE must be the DECnet Phase IV
node name, or the DECnet-Plus (Phase V) node synonym.
If you have multiple OpenVMS systems, the SCSNODE on each system
must be unique.
Enter SCSNODE: ES4002
If you plan to use DECnet, SCSSYSTEMID must be set based on the
DECnet Phase IV address.
Do you plan to use DECnet? (Yes/No) [Yes]
DECnet Phase IV addresses are in the format
DECnet_area_number.DECnet_node_number
DECnet_area_number is a number between 1 and 63.
DECnet_node_number is a number between 1 and 1023.
If you plan to use DECnet WITHOUT Phase IV compatible addresses,
enter 0.0.
Enter DECnet (Phase IV) Address: [1.1] 1.617
SCSSYSTEMID will be set to 1641.
This was calculated as follows:
(DECnet_area_number * 1024) + DECnet_node_number
Configuring the Local Time Zone
TIME ZONE SPECIFICATION -- MAIN Time Zone Menu "*" indicates a menu
0* GMT
1* AFRICA 17) EST 33) IRAN 49) PORTUGAL
2* AMERICA 18) EST5EDT 34) ISRAEL 50) PRC
3* ANTARCTICA 19* ETC 35) JAMAICA 51) PST8PDT
4* ARCTIC 20* EUROPE 36) JAPAN 52) ROC
5* ASIA 21) FACTORY 37) KWAJALEIN 53) ROK
6* ATLANTIC 22) GB-EIRE 38) LIBYA 54) SINGAPORE
7* AUSTRALIA 23) GB 39) MET 55) TURKEY
8* BRAZIL 24) GMT-0 40* MEXICO 56) UCT
9* CANADA 25) GMT 41* MIDEAST 57) UNIVERSAL
10) CET 26) GMT0 42) MST 58* US
11* CHILE 27) GMTPLUS0 43) MST7MDT 59) UTC
12) CST6CDT 28) GREENWICH 44) NAVAJO 60) W-SU
13) CUBA 29) HONGKONG 45) NZ-CHAT 61) WET
14) EET 30) HST 46) NZ 62) ZULU
15) EGYPT 31) ICELAND 47* PACIFIC
16) EIRE 32* INDIAN 48) POLAND
Press "Return" to redisplay, enter "=" to search or "?" for help, or
Select the number above that best represents the desired time zone: 20
EUROPE Time Zone Menu "*" indicates a menu
0* RETURN TO MAIN TIME ZONE MENU
1) AMSTERDAM 18) HELSINKI 35) MOSCOW 52) STOCKHOLM
2) ANDORRA 19) ISLE_OF_MAN 36) NICOSIA 53) TALLINN
3) ASTRAKHAN 20) ISTANBUL 37) OSLO 54) TIRANE
4) ATHENS 21) JERSEY 38) PARIS 55) TIRASPOL
5) BELFAST 22) KALININGRAD 39) PODGORICA 56) ULYANOVSK
6) BELGRADE 23) KIEV 40) POLAND 57) UZHGOROD
7) BERLIN 24) KIROV 41) PORTUGAL 58) VADUZ
8) BRATISLAVA 25) KYIV 42) PRAGUE 59) VATICAN
9) BRUSSELS 26) LISBON 43) RIGA 60) VIENNA
10) BUCHAREST 27) LJUBLJANA 44) ROME 61) VILNIUS
11) BUDAPEST 28) LONDON 45) SAMARA 62) VOLGOGRAD
12) BUSINGEN 29) LUXEMBOURG 46) SAN_MARINO 63) WARSAW
13) CHISINAU 30) MADRID 47) SARAJEVO 64) ZAGREB
14) COPENHAGEN 31) MALTA 48) SARATOV 65) ZAPOROZHYE
15) DUBLIN 32) MARIEHAMN 49) SIMFEROPOL 66) ZURICH
16) GIBRALTAR 33) MINSK 50) SKOPJE
17) GUERNSEY 34) MONACO 51) SOFIA
Press "Return" to redisplay, enter "=" to search or "?" for help, or
Select the number above that best represents the desired time zone: 14
You selected EUROPE / COPENHAGEN as your time zone.
Is this correct? (Yes/No) [YES]: y
Configuring the Time Differential Factor (TDF)
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 respects 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.).
This time zone supports daylight saving time.
Is this time zone currently on daylight saving time? (Yes/No): n
Enter the Time Differential Factor [1:00]:
NEW SYSTEM TIME DIFFERENTIAL FACTOR = 1:00
Is this correct? [Y]:
The target disk of this installation may be set up
to automatically configure the TCP/IP network stack
as a DHCP client, and to start up TCP/IP and SSH when
the system is booted.
If this option is chosen: The TCP/IP and SSH start up
procedures will be run by the operating system provided
start up command procedure that runs SYSTARTUP_VMS.COM.
The TCP/IP and SSH start up procedures will be executed
before SYSTARTUP_VMS.COM is executed.
A DHCP server is required.
Do you want to automatically configure and start up TCP/IP & SSH? (Yes/No) [No]
If you have Product Authorization Keys (PAKs) to register,
you can register them now.
Do you want to register any Product Authorization Keys? (Yes/No) [Yes] n
The following products are part of the OpenVMS installation;
they will be installed along with the OpenVMS operating system:
o Availability Manager (base) for OpenVMS X86-64
o TCP/IP Services for OpenVMS X86-64
o KERBEROS for OpenVMS X86-64
o SSL3 V3.0-15 for OpenVMS X86-64 (based on OpenSSL V3.0.15)
o SSL111 V1.1-1W for OpenVMS X86-64 (based on OpenSSL V1.1.1w)
o OpenSSH for OpenVMS X86-64
o 64-bit PERL for OpenVMS X86-64
You can also install the following optional products along with the
OpenVMS operating system:
o DECwindows Motif for OpenVMS X86-64
o DECnet-Plus for OpenVMS X86-64
o DECnet Phase IV for OpenVMS X86-64
If you want to change your selections, you can do so later in the
installation by answering "NO" to the following question:
"Do you want the defaults for all options?"
Do you want to install DECwindows Motif for OpenVMS X86-64 V1.8-2?
(Yes/No) [Yes]
The DECnet-Plus kit is provided with the OpenVMS operating system kit.
DECnet Phase IV applications are supported by DECnet-Plus.
DECnet Phase IV is also provided as an option.
If you install DECnet-Plus and TCP/IP you can run DECnet
applications over a TCP/IP network. Please refer to the
VSI DECnet-Plus for OpenVMS Planning Guide for information
on running DECnet over TCP/IP.
Do you want to install DECnet-Plus for OpenVMS X86-64 V9.2-G?
(Yes/No) [Yes]
The installation operation can provide brief or detailed descriptions.
In either case, you can request the detailed descriptions by typing ?.
Do you always want detailed descriptions? (Yes/No) [No]
Performing product kit validation of signed kits ...
%PCSI-I-VSIVALPASSED, validation of DMM1:[VMS$COMMON]VSI-X86VMS-VMS-V0902-3-2.PC
ucceeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.DWMOTIF_SUPPORT_X860923_KIT]VSI-X
PORT-V0902-3-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.AVAIL_MAN_BASE_KIT]VSI-X86VMS-AVA
-3-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.TCPIP]VSI-X86VMS-TCPIP-V0600-26-1
1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.SSL3]VSI-X86VMS-SSL3-V0300-15-1.P
succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.KERBEROS]VSI-X86VMS-KERBEROS-V030
SSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.SSL111]VSI-X86VMS-SSL111-V0101-1W
D;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.OPENSSH]VSI-X86VMS-OPENSSH-V0809-
SED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.PERL540]VSI-X86VMS-PERL540-V0540-
ED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.DWMOTIF]VSI-X86VMS-DWMOTIF-V0108-
ED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.DECNET_PLUS]VSI-X86VMS-DECNET_PLU
COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.DECNET_PHASE_IV_X860923_KIT]VSI-X
E_IV-V0902-3-1.PCSI$COMPRESSED;1 succeeded
The following product has been selected:
VSI X86VMS OPENVMS V9.2-3 Platform (product suite)
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.
Configuring VSI X86VMS OPENVMS V9.2-3: OPENVMS and related products Platform
Copyright 2015-2024 VMS Software, Inc.
VMS Software, Inc.
Do you want the defaults for all options? [YES]
Availability Manager (base) for OpenVMS X86-64
TCP/IP Services for OpenVMS X86-64
* Product VSI X86VMS TCPIP V6.0-26 requires a system reboot.
* Product VSI X86VMS AVAIL_MAN_BASE V9.2-3 recommends a system reboot.
Can the system be REBOOTED after the installation completes? [YES]
KERBEROS for OpenVMS X86-64
SSL3 V3.0-15 for OpenVMS X86-64 (based on OpenSSL V3.0.15)
SSL111 V1.1-1W for OpenVMS X86-64 (based on OpenSSL V1.1.1w)
OpenSSH for OpenVMS X86-64
64-bit PERL for OpenVMS X86-64
Do you want to review the options? [NO]
Execution phase starting ...
The following products will be installed to destinations:
VSI X86VMS AVAIL_MAN_BASE V9.2-3 DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS DECNET_PLUS V9.2-G DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS DWMOTIF V1.8-2 DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS DWMOTIF_SUPPORT V9.2-3 DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS KERBEROS V3.3-3 DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS OPENSSH V8.9-1J DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS OPENVMS V9.2-3 DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS PERL540 V5.40-0 DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS SSL111 V1.1-1W DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS SSL3 V3.0-15 DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS TCPIP V6.0-26 DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS VMS V9.2-3 DISK$X86SYS:[VMS$COMMON.]
Portion done: 0%...10%...20%...30%...40%...50%...60%...70%
Restoring STARTUP.NSH file(s)...
No files restored
...80%...90%
%PCSI-I-PRCOUTPUT, output from subprocess follows ...
% - Execute SYS$MANAGER:TCPIP$CONFIG.COM to proceed with configuration of
% VSI TCP/IP Services for OpenVMS.
%
Portion done: 100%
The following products have been installed:
VSI X86VMS AVAIL_MAN_BASE V9.2-3 Layered Product
VSI X86VMS DECNET_PLUS V9.2-G Layered Product
VSI X86VMS DWMOTIF V1.8-2 Layered Product
VSI X86VMS DWMOTIF_SUPPORT V9.2-3 Layered Product
VSI X86VMS KERBEROS V3.3-3 Layered Product
VSI X86VMS OPENSSH V8.9-1J Layered Product
VSI X86VMS OPENVMS V9.2-3 Platform (product suite)
VSI X86VMS PERL540 V5.40-0 Layered Product
VSI X86VMS SSL111 V1.1-1W Layered Product
VSI X86VMS SSL3 V3.0-15 Layered Product
VSI X86VMS TCPIP V6.0-26 Layered Product
VSI X86VMS VMS V9.2-3 Operating System
VSI X86VMS OPENVMS V9.2-3: OPENVMS and related products Platform
VSI X86VMS TCPIP V6.0-26: VSI TCP/IP Services for OpenVMS.
VSI X86VMS SSL3 V3.0-15: SSL3 for OpenVMS X86-64 V3.0-15 (Based on OpenSSL
Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM:
@SYS$STARTUP:SSL3$STARTUP.COM
Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM:
@SYS$STARTUP:SSL3$SHUTDOWN.COM
Review the Installation Guide and Release Notes for post install directi
Review the Installation Guide and Release Notes for post upgrade verific
.
Refer to SYS$HELP:SSL30-15-X86.RELEASE_NOTES for more information.
Check the release notes for current status of the product.
VSI X86VMS KERBEROS V3.3-3
Configure and set up Kerberos
If Kerberos will be run on this system, but has not been
used previously, you need to perform the following steps.
o Run the Kerberos configuration procedure:
@SYS$STARTUP:KRB$CONFIGURE.COM
o Add the following line to SYS$MANAGER:SYSTARTUP_VMS.COM:
$ @SYS$STARTUP:KRB$STARTUP
o Add the following line to SYS$MANAGER:SYLOGIN.COM:
$ @SYS$MANAGER:KRB$SYMBOLS
VSI X86VMS SSL3 V3.0-15: SSL3 for OpenVMS X86-64 V3.0-15 (Based on OpenSSL 3
Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM:
@SYS$STARTUP:SSL3$STARTUP.COM
Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM:
@SYS$STARTUP:SSL3$SHUTDOWN.COM
Review the Installation Guide and Release Notes for post install direction
Review the Installation Guide and Release Notes for post upgrade verificat
Refer to SYS$HELP:SSL30-15-X86.RELEASE_NOTES for more information.
VSI X86VMS SSL111 V1.1-1W: SSL111 for OpenVMS X86-64 V1.1-1W (Based on OpenS
Review the Installation Guide and Release Notes for post install direction
Review the Installation Guide and Release Notes for post upgrade verificat
Refer to SYS$HELP:SSL111-W-X86.RELEASE_NOTES for more information.
VSI X86VMS PERL540 V5.40-0
Post-installation tasks are required for Perl for OpenVMS.
To use the Perl provided with this kit, run the following set-up
command procedure, assuming you installed in SYS$COMMON.
$ @sys$common:[perl-5_40]perl_setup.com
You may wish to put that command in SYS$MANAGER:SYLOGIN.COM to
make Perl available to all users on the system.
Perl includes its own help system called perldoc. Type
$ perldoc perldoc
for the documentation to perldoc itself. Type
$ perldoc perldelta
for the changes that are new in version V5.40-0 of Perl.
There are many Perl-related resources on the web; point your
browser at:
http://www.perl.org
to get started, and thank you for using Perl for OpenVMS.
VSI X86VMS DECNET_PLUS V9.2-G: DECnet-Plus V9.2-G for OpenVMS X86
Release notes are available in SYS$HELP:HPE_DECNET-Plus-V84.RELEASE_NOTES
DECNET_OSI.RELEASE_NOTES
%PCSI-I-SYSTEM_REBOOT, executing reboot procedure ...
Shutdown/reboot deferred when this product is
installed as part of the O/S installation/upgrade
%PCSI-I-SYSTEM_REBOOT, executing reboot procedure ...
Running SYS$UPDATE:SYS$MD.COM to update the memory disk...
Created memory disk DKA0:[VMS$COMMON.SYS$LDR]SYS$MD.DSK;1
- using 188528 blocks in 1 extent with 25683 spare blocks
- mounted on LDM5019: with volume label MD2430435F0A
- contains OpenVMS V9.2-3
%LD-I-UNIT, Allocated device is LDM5020:
%LMFINSTALL-I-SUCCESS, License installed with 6 units, Termination: 4-NOV-2024
The EFI Boot Manager menu includes multiple Boot Options
for DKA0:
Boot Options cannot be created or validated automatically.
Please use the OpenVMS X86-64 Boot Manager to ensure that you
have a valid Boot Option for this system.
You can run the OpenVMS X86-64 Boot Manager by choosing the DCL
option from the main menu and then execute this command:
$$$ @SYS$MANAGER:BOOT_OPTIONS
You can also execute this command from a properly privileged
account after booting your OpenVMS X86-64 system.
The installation is now complete.
When the newly installed system is first booted, a special
startup procedure will be run. This procedure will:
o Configure the system for standalone or OpenVMS Cluster operation.
o Run AUTOGEN to set system parameters.
o Reboot the system with the newly set parameters.
You may shut down now or continue with other operations.
Process X86VMS_INSTALL logged out at 30-OCT-2024 22:03:21.95
Press Return to continue...
****************************************************************
You can install or upgrade the OpenVMS X86-64 operating system
or you can install or upgrade layered products that are included
on the OpenVMS X86-64 distribution media.
You can also execute DCL commands and procedures to perform
"standalone" tasks, such as backing up the system disk.
Please choose one of the following:
1) Upgrade, install or reconfigure OpenVMS X86-64 Version V9.2-3
2) Display layered products that this procedure can install
3) Install or upgrade layered products
4) Show installed products
5) Reconfigure installed products
6) Remove installed products
7) Find, Install or Undo patches; Show or Delete Recovery Data
8) Execute DCL commands and procedures
9) Shut down this system
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/9/?) 9
Shutting down the system
VSI Dump Kernel - Handles Shutdown/Reboot/Crash Dumps
** Error logs not dumped, system disk is write locked.
SYSTEM SHUTDOWN COMPLETE
**** Hit any key to reboot system ****
Restarting the system...
Attempting to start up from:
> EFI Virtual disk (0.0)... unsuccessful.
> EFI Internal Shell (Unsupported option)...
EFI Shell version 2.70 [1.0]
Current running mode 1.1.2
Device mapping table
fs0 :CDRom - Alias cd27a0a0 blk0
PciRoot(0x0)/Pci(0x11,0x0)/Pci(0x3,0x0)/Sata(0x0,0x0,0x0)/CDROM(0x0,0
fs1 :Removable HardDisk - Alias hd19a0b blk1
PciRoot(0x0)/Pci(0x10,0x0)/Scsi(0x0,0x0)/HD(1,GPT,11920D44-970A-11EF-,0x266530,0x3E800)
blk0 :CDRom - Alias cd27a0a0 fs0
PciRoot(0x0)/Pci(0x11,0x0)/Pci(0x3,0x0)/Sata(0x0,0x0,0x0)/CDROM(0x0,0
blk1 :Removable HardDisk - Alias hd19a0b fs1
PciRoot(0x0)/Pci(0x10,0x0)/Scsi(0x0,0x0)/HD(1,GPT,11920D44-970A-11EF-,0x266530,0x3E800)
blk2 :BlockDevice - Alias (null)
PciRoot(0x0)/Pci(0x11,0x0)/Pci(0x3,0x0)/Sata(0x0,0x0,0x0)
blk3 :Removable HardDisk - Alias (null)
PciRoot(0x0)/Pci(0x10,0x0)/Scsi(0x0,0x0)/HD(2,GPT,11920D43-970A-11EF-,0x30,0x266500)
blk4 :Removable HardDisk - Alias (null)
PciRoot(0x0)/Pci(0x10,0x0)/Scsi(0x0,0x0)/HD(3,GPT,11920D44-970A-11EF-,0x2A4D30,0x195B2AF)
blk5 :Removable BlockDevice - Alias (null)
PciRoot(0x0)/Pci(0x10,0x0)/Scsi(0x0,0x0)
Shell> FS1:Removable BlockDevice - Alias (null)
PciRoot(0x0)/Pci(0x10,0x0)/Scsi(0x3,0x0)
fs1:\> cd efi\vms
Press ESC in 2 seconds to skip startup.nsh, any other key to continue.
fs1:\EFI\VMS> vms_bootmgr
Scanning devices and preparing the OpenVMS Boot Manager Build 146...
VSI OpenVMS Boot Manager: V9.2-* Build 146
ENABLED: Symmetric Multi-Processing
ENABLED: Crash Dump Processing
ENABLED: Legacy Serial Port Console for remote COM 1
ENABLED: Using Environment ROM
Checking Required Processor Features: PASSED
VIRTUAL MACHINE GUEST:
VMware (tm) No Mouse support; Use Commands or Arrow Keys
BOOT MANAGER DEVICE: DKA0
DEFAULT BOOT COMMAND: BOOT DKA0 0x00 0x00000000
CONNECT A REMOTE TERMINAL SESSION NOW.
Enter the TERMINAL command for remote connection assistance.
BOOTMGR> DEVICES
BOOTABLE DEVICES:
B = BootMgr Device, V = Default VMS Boot Device. Set BOOTMGR flag for path info
BV DKA0 (HD) = FS0 UEFI: V9_2_3 VMS: X86SYS 14336 MB SCSI Disk
DKB0 (DVD) = FS1 UEFI: V9_2_3 VMS: None 1511 MB SATA DVD
BOOTMGR> BOOT DKA0
Booting...
%%%%%%%%%%% VSI OpenVMS (tm) x86-64 Console %%%%%%%%%%%
_______________________________________________
THE GUEST CONSOLE HAS BEEN SUSPENDED
USE A TERMINAL UTILITY FOR OPA0 ACCESS
_______________________________________________
VSI Primary Kernel SYSBOOT
%SYSBOOT-I-VMTYPE, Booting as a VMware (tm) Guest
VMS Software, Inc. OpenVMS (TM) x86_64 Operating System, V9.2-3
Copyright 2024 VMS Software, Inc.
MDS Mitigation active, variant verw(MD_CLEAR)
%DECnet-I-LOADED, network base image loaded, version = 05.92.07
%DECnet-W-ZEROLEN, length of file is zero -- SYS$SYSROOT:[SYSEXE]NET$CONFIG.DAT
%SMP-I-CPUTRN, CPU #4 has joined the active set.
%SMP-I-CPUTRN, CPU #2 has joined the active set.
%SMP-I-CPUTRN, CPU #1 has joined the active set.
%SMP-I-CPUTRN, CPU #5 has joined the active set.
%SMP-I-CPUTRN, CPU #3 has joined the active set.
Installing required known files...
Configuring devices...
%RUN-S-PROC_ID, identification of created process is 00000024
%STARTUP-E-NOPAGFIL, No page files have been successfully installed.
%SYSTEM-I-BOOTUPGRADE, security auditing disabled
%%%%%%%%%%% OPCOM 30-OCT-2024 23:02:54.88 %%%%%%%%%%%
Operator _ES4002$OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 30-OCT-2024 23:02:54.88 %%%%%%%%%%%
Operator status for operator _ES4002$OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%%%%%%%%%%% OPCOM 30-OCT-2024 23:02:54.91 %%%%%%%%%%%
Logfile has been initialized by operator _ES4002$OPA0:
Logfile is ES4002::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
%%%%%%%%%%% OPCOM 30-OCT-2024 23:02:54.91 %%%%%%%%%%%
Operator status for operator ES4002::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 30-OCT-2024 23:02:55.14 %%%%%%%%%%%
Message from user SYSTEM on ES4002
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 30-OCT-2024 23:02:55.15 %%%%%%%%%%%
Message from user SYSTEM on ES4002
-RMS-E-FNF, file not found
%SYSTEM-I-BOOTUPGRADE, security server not started
%SYSTEM-I-BOOTUPGRADE, ACME server not started
%%%%%%%%%%% OPCOM 30-OCT-2024 23:02:55.31 %%%%%%%%%%%
Message from user SYSTEM on ES4002
TDF-I-SETTDF TDF set new timezone differential
NET$STARTUP, Network not started due to UPGRADE boot
%SYSTEM-I-BOOTUPGRADE, Coordinated Startup not performed
%EIA0, Link up: 1000 mbit, 00-0C-29-80-62-C9
AUTOGEN will now be run to compute the new system parameters. The system
will then shut down and reboot, and the installation or upgrade will be
complete.
After rebooting you can continue with such system management tasks as:
Configuring networking software (TCP/IP Services, DECnet, other)
Using SYS$MANAGER:CLUSTER_CONFIG.COM to create an OpenVMS Cluster
Creating FIELD, SYSTEST and SYSTEST_CLIG accounts if needed
%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, 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, 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-CREATED, SYS$SYSROOT:[SYSEXE]SYS$ERRLOG.DMP;2 created
%SYSGEN-I-CREATED, DKA0:[SYS0.SYSEXE]SYSDUMP.DMP;1 created
Extending DKA0:[SYS0.SYSEXE]SYSDUMP.DMP to 16246490 blocks will take
approximately 80 seconds. Please wait ...
%SYSGEN-I-EXTENDED, DKA0:[SYS0.SYSEXE]SYSDUMP.DMP;1 extended
... done.
******************
%AUTOGEN-W-REPORT, Warnings were detected by AUTOGEN. Please review the
information given in the file SYS$SYSTEM:AGEN$PARAMS.REPORT
******************
%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.
%SYSGEN-W-SETMAX, value set to maximum for parameter GH_EXEC_CODE
%%%%%%%%%%% OPCOM 30-OCT-2024 23:05:54.10 %%%%%%%%%%%
Message from user SYSTEM on ES4002
%SYSGEN-I-WRITECUR, CURRENT system parameters modified by process ID 00000023 in
to file SYS$SYSROOT_MD:[SYSEXE]X86_64VMSSYS.PAR;2
%AUTOGEN-I-SYSGEN, parameters modified
%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
upgrade will be complete.
SHUTDOWN -- Perform an Orderly System Shutdown
on node ES4002
%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 = 0
%SHUTDOWN-I-STOPQUEUES, the queues on this node will now be stopped
%%%%%%%%%%% OPCOM 30-OCT-2024 23:05:54.54 %%%%%%%%%%%
Message from user SYSTEM on ES4002
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 30-OCT-2024 23:05:54.54 %%%%%%%%%%%
Message from user SYSTEM on ES4002
-RMS-E-FNF, file not found
SHUTDOWN message on ES4002 from user SYSTEM at ES4002 Batch 23:05:54
ES4002 will shut down in 0 minutes; back up soon. Please log off node ES4002.
Reboot system with AUTOGENerated parameters
%SHUTDOWN-I-STOPUSER, all user processes will now be stopped
%SHUTDOWN-I-STOPCPU, the secondary processors will now be stopped
%SMP-I-CPUTRN, CPU #1 was removed from the active set.
%SMP-I-CPUTRN, CPU #2 was removed from the active set.
%SMP-I-CPUTRN, CPU #3 was removed from the active set.
%SMP-I-CPUTRN, CPU #4 was removed from the active set.
%SMP-I-CPUTRN, CPU #5 was removed from the active set.
%SHUTDOWN-I-REMOVE, all installed images will now be removed
%SET-I-PSXROOSET, system POSIX root set to SYS$SYSDEVICE:[000000]
%SHUTDOWN-I-DISMOUNT, all volumes will now be dismounted
%%%%%%%%%%% OPCOM 30-OCT-2024 23:05:54.80 %%%%%%%%%%%
Message from user SYSTEM on ES4002
STARTUP, ES4002 shutdown was requested by the operator.
VSI Dump Kernel - Handles Shutdown/Reboot/Crash Dumps
** Dumping error logs to the system disk (ES4002$DKA0:)
** Error logs dumped to ES4002$DKA0:[SYS0.SYSEXE]SYS$ERRLOG.DMP
** (used 36 out of 128 available blocks)
Restarting the system...
Attempting to start up from:
> EFI Virtual disk (0.0)... unsuccessful.
> EFI Internal Shell (Unsupported option)...
EFI Shell version 2.70 [1.0]
Current running mode 1.1.2
Device mapping table
fs0 :CDRom - Alias cd27a0a0 blk0
PciRoot(0x0)/Pci(0x11,0x0)/Pci(0x3,0x0)/Sata(0x0,0x0,0x0)/CDROM(0x0,0
fs1 :Removable HardDisk - Alias hd19a0b blk1
PciRoot(0x0)/Pci(0x10,0x0)/Scsi(0x0,0x0)/HD(1,GPT,11920D44-970A-11EF-,0x266530,0x3E800)
blk0 :CDRom - Alias cd27a0a0 fs0
PciRoot(0x0)/Pci(0x11,0x0)/Pci(0x3,0x0)/Sata(0x0,0x0,0x0)/CDROM(0x0,0
blk1 :Removable HardDisk - Alias hd19a0b fs1
PciRoot(0x0)/Pci(0x10,0x0)/Scsi(0x0,0x0)/HD(1,GPT,11920D44-970A-11EF-,0x266530,0x3E800)
blk2 :BlockDevice - Alias (null)
PciRoot(0x0)/Pci(0x11,0x0)/Pci(0x3,0x0)/Sata(0x0,0x0,0x0)
blk3 :Removable HardDisk - Alias (null)
PciRoot(0x0)/Pci(0x10,0x0)/Scsi(0x0,0x0)/HD(2,GPT,11920D43-970A-11EF-,0x30,0x266500)
blk4 :Removable HardDisk - Alias (null)
PciRoot(0x0)/Pci(0x10,0x0)/Scsi(0x0,0x0)/HD(3,GPT,11920D44-970A-11EF-,0x2A4D30,0x195B2AF)
blk5 :Removable BlockDevice - Alias (null)
PciRoot(0x0)/Pci(0x10,0x0)/Scsi(0x0,0x0)
Shell> :Removable BlockDevice - Alias (null)
Shell> FS1:PciRoot(0x0)/Pci(0x10,0x0)/Scsi(0x3,0x0)
fs1:\> cd efi\vmsconds to skip startup.nsh, any other key to continue.
fs1:\EFI\VMS> vms_bootmgr
Scanning devices and preparing the OpenVMS Boot Manager Build 146...
VSI OpenVMS Boot Manager: V9.2-* Build 146
ENABLED: Symmetric Multi-Processing
ENABLED: Crash Dump Processing
ENABLED: Legacy Serial Port Console for remote COM 1
ENABLED: Using Environment ROM
Checking Required Processor Features: PASSED
VIRTUAL MACHINE GUEST:
VMware (tm) No Mouse support; Use Commands or Arrow Keys
BOOT MANAGER DEVICE: DKA0
DEFAULT BOOT COMMAND: BOOT DKA0 0x00 0x00000000
CONNECT A REMOTE TERMINAL SESSION NOW.
Enter the TERMINAL command for remote connection assistance.
BOOTMGR> DEVICES
BOOTABLE DEVICES:
B = BootMgr Device, V = Default VMS Boot Device. Set BOOTMGR flag for path info
BV DKA0 (HD) = FS0 UEFI: V9_2_3 VMS: X86SYS 14336 MB SCSI Disk
DKB0 (DVD) = FS1 UEFI: V9_2_3 VMS: None 1511 MB SATA DVD
BOOTMGR> BOOT DKA0
Booting...
%%%%%%%%%%% VSI OpenVMS (tm) x86-64 Console %%%%%%%%%%%
_______________________________________________
THE GUEST CONSOLE HAS BEEN SUSPENDED
USE A TERMINAL UTILITY FOR OPA0 ACCESS
_______________________________________________
VSI Primary Kernel SYSBOOT
%SYSBOOT-I-VMTYPE, Booting as a VMware (tm) Guest
VMS Software, Inc. OpenVMS (TM) x86_64 Operating System, V9.2-3
Copyright 2024 VMS Software, Inc.
MDS Mitigation active, variant verw(MD_CLEAR)
%DECnet-I-LOADED, network base image loaded, version = 05.92.07
%DECnet-W-ZEROLEN, length of file is zero -- SYS$SYSROOT:[SYSEXE]NET$CONFIG.DAT
%SMP-I-CPUTRN, CPU #2 has joined the active set.
%SMP-I-CPUTRN, CPU #5 has joined the active set.
%SMP-I-CPUTRN, CPU #4 has joined the active set.
%SMP-I-CPUTRN, CPU #3 has joined the active set.
%SMP-I-CPUTRN, CPU #1 has joined the active set.
%STDRV-I-STARTUP, OpenVMS startup begun at 30-OCT-2024 23:07:31.49
%EIA0, Link up: 1000 mbit, 00-0C-29-80-62-C9
%RUN-S-PROC_ID, identification of created process is 00000404
%RUN-S-PROC_ID, identification of created process is 00000405
%SET-I-NEWAUDSRV, identification of new audit server process is 0000040B
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:33.64 %%%%%%%%%%%
Operator _ES4002$OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:33.64 %%%%%%%%%%%
Operator status for operator _ES4002$OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:33.68 %%%%%%%%%%%
Logfile has been initialized by operator _ES4002$OPA0:
Logfile is ES4002::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;2
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:33.68 %%%%%%%%%%%
Operator status for operator ES4002::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;2
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:33.84 %%%%%%%%%%%
Message from user AUDIT$SERVER on ES4002
%AUDSRV-I-NEWSERVERDB, new audit server database created ( PC 00000000.8001A365)
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:33.87 %%%%%%%%%%%
Message from user SYSTEM on ES4002
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:33.87 %%%%%%%%%%%
Message from user SYSTEM on ES4002
-RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:33.89 %%%%%%%%%%%
Message from user AUDIT$SERVER on ES4002
%AUDSRV-I-REMENABLED, resource monitoring enabled for journal SECURITY
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:33.97 %%%%%%%%%%%
Message from user AUDIT$SERVER on ES4002
%AUDSRV-I-NEWOBJECTDB, new object database created ( PC 00000000.8001FA80)
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:34.12 %%%%%%%%%%%
Message from user SYSTEM on ES4002
%ACME-I-SERVERSTART, ACME_SERVER starting
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:34.15 %%%%%%%%%%%
Message from user SYSTEM on ES4002
%SECSRV-I-SERVERSTARTINGU, security server starting up
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:34.15 %%%%%%%%%%%
Message from user SYSTEM on ES4002
%SECSRV-I-CIACRECLUDB, security server created cluster intrusion database
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:34.15 %%%%%%%%%%%
Message from user SYSTEM on ES4002
%SECSRV-I-CIASTARTINGUP, breakin detection and evasion processing now starting up
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:37.16 %%%%%%%%%%%
Message from user SYSTEM on ES4002
%SECSRV-I-PROXYSTARTINGUP, proxy processing now starting up
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:37.17 %%%%%%%%%%%
Message from user SYSTEM on ES4002
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:42.18 %%%%%%%%%%%
Message from user SYSTEM on ES4002
TDF-I-SETTDF TDF set new timezone differential
Copyright 2023 VMS Software, Inc.
%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
%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
%STARTUP-I-AUDITCONTINUE, audit server initialization complete
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:43.32 %%%%%%%%%%%
Message from user AUDIT$SERVER on ES4002
Security alarm (SECURITY) and security audit (SECURITY) on ES4002, system id: 16
41
Auditable event: Audit server starting up
Event time: 30-OCT-2024 23:07:43.29
PID: 00000403
Username: SYSTEM
The OpenVMS system is now executing the site-specific startup commands.
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:43.65 %%%%%%%%%%%
Message from user AUDIT$SERVER on ES4002
Security alarm (SECURITY) and security audit (SECURITY) on ES4002, system id: 16
41
Auditable event: Identifier added
Event time: 30-OCT-2024 23:07:43.65
PID: 00000403
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: ES4002$DKA0:[SYS0.SYSCOMMON.][SYSEXE]AUTHORIZE.EXE
Identifier name: SYS$NODE_ES4002
Identifier value: %X80010000
Attributes: none
Posix UID: -2
Posix GID: -2 (%XFFFFFFFE)
%UAF-I-RDBADDMSG, identifier SYS$NODE_ES4002 value %X80010000 added to rights da
tabase
%DECW$DEVICE-I-NODEVICE, no graphics devices found.
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:43.77 %%%%%%%%%%%
Message from user AUDIT$SERVER on ES4002
Security alarm (SECURITY) and security audit (SECURITY) on ES4002, system id: 16
41
Auditable event: Identifier added
Event time: 30-OCT-2024 23:07:43.77
PID: 00000403
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: ES4002$DKA0:[SYS0.SYSCOMMON.][SYSEXE]AUTHORIZE.EXE
Identifier name: DECW$WS_QUOTA
Identifier value: %X80010001
Attributes: none
Posix UID: -2
Posix GID: -2 (%XFFFFFFFE)
%UAF-I-RDBADDMSG, identifier DECW$WS_QUOTA value %X80010001 added to rights data
base
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:43.82 %%%%%%%%%%%
Message from user AUDIT$SERVER on ES4002
Security alarm (SECURITY) and security audit (SECURITY) on ES4002, system id: 16
41
Auditable event: Identifier added
Event time: 30-OCT-2024 23:07:43.82
PID: 00000403
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: ES4002$DKA0:[SYS0.SYSCOMMON.][SYSEXE]IMGDMP_RIGHTS.EXE
;1
Identifier name: IMGDMP$READALL
Identifier value: %X90390001
Attributes: none
Posix UID: -2
Posix GID: -2 (%XFFFFFFFE)
%PROCDUMP-I-CREATED, rights identifier IMGDMP$READALL successfully created
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:43.83 %%%%%%%%%%%
Message from user AUDIT$SERVER on ES4002
Security alarm (SECURITY) and security audit (SECURITY) on ES4002, system id: 16
41
Auditable event: Identifier added
Event time: 30-OCT-2024 23:07:43.83
PID: 00000403
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: ES4002$DKA0:[SYS0.SYSCOMMON.][SYSEXE]IMGDMP_RIGHTS.EXE
;1
Identifier name: IMGDMP$PROTECT
Identifier value: %X90390002
Attributes: RESOURCE
Posix UID: -2
Posix GID: -2 (%XFFFFFFFE)
%PROCDUMP-I-CREATED, rights identifier IMGDMP$PROTECT successfully created
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
%RUN-S-PROC_ID, identification of created process is 00000412
%%%%%%%%%%% OPCOM 30-OCT-2024 23:07:43.96 %%%%%%%%%%%
Message from user SYSTEM on ES4002
%SMHANDLER-S-STARTUP, server management event handler startup
SYSTEM job terminated at 30-OCT-2024 23:07:45.93
Accounting information:
Buffered I/O count: 3111 Peak working set size: 13824
Direct I/O count: 1790 Peak virtual size: 279232
Page faults: 4329 Mounted volumes: 0
Charged CPU time: 0 00:00:01.26 Elapsed time: 0 00:00:14.60
Below is the sample upgrade log.
You must enter 1, 2, 3, 4, 5, 6, 7, 8, 9 or ?!
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/9/?) 1
***********************************************************
This procedure will ask a series of questions.
() - encloses acceptable answers
[] - encloses default answers
Type your response and press the <Return> key. Type:
? - to repeat an explanation
^ - to change prior input (not always possible)
Ctrl/Y - to exit the installation procedure
There are two choices for installation/upgrade:
Initialize - Removes all software and data files that were
previously on the target disk and installs OpenVMS X86-64.
Preserve -- Installs or Upgrades OpenVMS X86-64 on the target disk
and retains all other contents of the target disk.
* Note: You cannot use preserve to install OpenVMS X86-64 on a disk on
which any other operating system is installed. This includes
implementations of OpenVMS for other architectures.
Do you want to INITIALIZE or to PRESERVE? [PRESERVE]
You must enter the device name for the target disk on which
OpenVMS X86-64 will be installed.
Enter device name for target disk: (? for choices) ?
Device Name Device Type Name Volume Label Size (blocks/xB)
------------ ------------------------- -------------- --------------------
DKB0: VMware Virtual disk
DKB100: VMware Virtual disk
For volume label and device size enter ??
Enter device name for target disk: (? for choices) dkb0
DKB0: is now labeled 4012SYS.
Do you want to keep this label? (Yes/No) [Yes]
OpenVMS X86-64 will be upgraded on DKB0:.
Boot options in the EFI Boot Manager boot option menu can provide a
convenient way to boot your system. The installation procedure can
automatically create a new boot option (if none exists) or validate
existing boot options.
Do you want to create or validate boot options? (Yes/No) [Yes]
The following products are part of the OpenVMS installation;
if necessary they will be installed or upgraded along with the
OpenVMS operating system.
o Availability Manager (base) for OpenVMS X86-64
o TCP/IP Services for OpenVMS X86-64
o KERBEROS for OpenVMS X86-64
o SSL3 V3.0-15 for OpenVMS X86-64 (based on OpenSSL V3.0.15)
o SSL111 V1.1-1W for OpenVMS X86-64 (based on OpenSSL V1.1.1w)
o OpenSSH for OpenVMS X86-64
o 64-bit PERL for OpenVMS X86-64
If necessary, the following optional products will also be upgraded
along with the OpenVMS operating system.
o DECwindows Motif for OpenVMS X86-64
o DECnet-Plus for OpenVMS X86-64
o DECnet Phase IV for OpenVMS X86-64
If you want to add or delete optional products, you can do so later
in the upgrade by answering "NO" to the following question:
"Do you want the defaults for all options?"
Availability Manager (base) for OpenVMS X86-64
is installed on your system. It will be upgraded.
TCP/IP Services for OpenVMS X86-64
is installed on your system. It will be upgraded.
KERBEROS for OpenVMS X86-64
is installed on your system. It will be upgraded.
SSL3 V3.0-15 for OpenVMS X86-64 (based on OpenSSL V3.0.15)
is installed on your system. It will be upgraded.
SSL111 V1.1-1W for OpenVMS X86-64 (based on OpenSSL V1.1.1w) V1.1-1W
is already installed on your system. An upgrade is not required.
OpenSSH for OpenVMS X86-64
is installed on your system. It will be upgraded.
64-bit PERL for OpenVMS X86-64 is required.
It will be installed.
DECwindows Motif for OpenVMS X86-64
is installed on your system. It will be upgraded.
DECnet-Plus for OpenVMS X86-64
is installed on your system. It will be upgraded.
DECnet Phase IV for OpenVMS X86-64 is not installed on your system.
It will not be installed.
The installation operation can provide brief or detailed descriptions.
In either case, you can request the detailed descriptions by typing ?.
Do you always want detailed descriptions? (Yes/No) [No]
Preserving existing copies of STARTUP.NSH if found...
No STARTUP.NSH files were found in the EFI system partition file
Performing product kit validation of signed kits ...
%PCSI-I-VSIVALPASSED, validation of DMM1:[VMS$COMMON]VSI-X86VMS-VMS-V0902-3-2.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.DWMOTIF_SUPPORT_X860923_KIT]VSI-X86VMS-DWMOTIF_SUPPORT-V0902-3-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.AVAIL_MAN_BASE_KIT]VSI-X86VMS-AVAIL_MAN_BASE-V0902-3-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.TCPIP]VSI-X86VMS-TCPIP-V0600-26-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.SSL3]VSI-X86VMS-SSL3-V0300-15-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.KERBEROS]VSI-X86VMS-KERBEROS-V0303-3-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.SSL111]VSI-X86VMS-SSL111-V0101-1W-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.OPENSSH]VSI-X86VMS-OPENSSH-V0809-1J-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.PERL540]VSI-X86VMS-PERL540-V0540-0-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.DWMOTIF]VSI-X86VMS-DWMOTIF-V0108-2-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.DECNET_PLUS]VSI-X86VMS-DECNET_PLUS-V0902-G-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.DECNET_PHASE_IV_X860923_KIT]VSI-X86VMS-DECNET_PHASE_IV-V0902-3-1.PCSI$COMPRESSED;1 succeeded
The following product has been selected:
VSI X86VMS OPENVMS V9.2-3 Platform (product suite)
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.
Configuring VSI X86VMS OPENVMS V9.2-3: OPENVMS and related products Platform
Copyright 2015-2024 VMS Software, Inc.
VMS Software, Inc.
Do you want the defaults for all options? [YES]
Availability Manager (base) for OpenVMS X86-64
TCP/IP Services for OpenVMS X86-64
* Product VSI X86VMS TCPIP V6.0-26 requires a system reboot.
* Product VSI X86VMS AVAIL_MAN_BASE V9.2-3 recommends a system reboot.
Can the system be REBOOTED after the installation completes? [YES]
KERBEROS for OpenVMS X86-64
SSL3 V3.0-15 for OpenVMS X86-64 (based on OpenSSL V3.0.15)
SSL111 V1.1-1W for OpenVMS X86-64 (based on OpenSSL V1.1.1w)
OpenSSH for OpenVMS X86-64
64-bit PERL for OpenVMS X86-64
Do you want to review the options? [NO]
Execution phase starting ...
The following products will be installed to destinations:
VSI X86VMS AVAIL_MAN_BASE V9.2-3 DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS DECNET_PLUS V9.2-G DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS DWMOTIF V1.8-2 DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS DWMOTIF_SUPPORT V9.2-3 DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS KERBEROS V3.3-3 DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS OPENSSH V8.9-1J DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS OPENVMS V9.2-3 DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS PERL540 V5.40-0 DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS SSL3 V3.0-15 DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS TCPIP V6.0-26 DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS VMS V9.2-3 DISK$4012SYS:[VMS$COMMON.]
The following products will be removed from destinations:
VMSPORTS X86VMS PERL534 T5.34-0 DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS AVAIL_MAN_BASE V9.2-2 DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS DECNET_PLUS V9.2-E DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS DWMOTIF V1.8 DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS DWMOTIF_SUPPORT V9.2-2 DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS KERBEROS V3.3-2A DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS OPENSSH V8.9-1G DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS OPENVMS V9.2-2 DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS SSL3 V3.0-11 DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS TCPIP V6.0-23 DISK$4012SYS:[VMS$COMMON.]
VSI X86VMS VMS V9.2-2 DISK$4012SYS:[VMS$COMMON.]
Portion done: 0%
Device is DISK$4012SYS:[SYS0.SYSCOMMON.SYS$STARTUP], now upgrade remove running.
..
Unless you elect to retain them when prompted,
this utility will delete the following:
- OpenSSH configuration files.
- OpenSSH default OpenVMS accounts (SSH$SSH, SSH$SSHD).
Delete OpenSSH configuration files? [y/n]: [n]
Disabling TCPIP services...
No services found
Deleting SSH$ROOT: directory tree...
SSH$ROOT: directory tree successfully removed
from SYS$SYSDEVICE:[SYS0.SYSCOMMON.OPENSSH]
...10%...20%...30%...40%...50%...60%...70%
Restoring STARTUP.NSH file(s)...
No files restored
...80%...90%
%PCSI-I-PRCOUTPUT, output from subprocess follows ...
% - Execute SYS$MANAGER:TCPIP$CONFIG.COM to proceed with configuration of
% VSI TCP/IP Services for OpenVMS.
%
Portion done: 100%
The following products have been installed:
VSI X86VMS AVAIL_MAN_BASE V9.2-3 Layered Product
VSI X86VMS DECNET_PLUS V9.2-G Layered Product
VSI X86VMS DWMOTIF V1.8-2 Layered Product
VSI X86VMS DWMOTIF_SUPPORT V9.2-3 Layered Product
VSI X86VMS KERBEROS V3.3-3 Layered Product
VSI X86VMS OPENSSH V8.9-1J Layered Product
VSI X86VMS OPENVMS V9.2-3 Platform (product suite)
VSI X86VMS PERL540 V5.40-0 Layered Product
VSI X86VMS SSL3 V3.0-15 Layered Product
VSI X86VMS TCPIP V6.0-26 Layered Product
VSI X86VMS VMS V9.2-3 Operating System
The following products have been removed:
VMSPORTS X86VMS PERL534 T5.34-0 Layered Product
VSI X86VMS AVAIL_MAN_BASE V9.2-2 Layered Product
VSI X86VMS DECNET_PLUS V9.2-E Layered Product
VSI X86VMS DWMOTIF V1.8 Layered Product
VSI X86VMS DWMOTIF_SUPPORT V9.2-2 Layered Product
VSI X86VMS KERBEROS V3.3-2A Layered Product
VSI X86VMS OPENSSH V8.9-1G Layered Product
VSI X86VMS OPENVMS V9.2-2 Platform (product suite)
VSI X86VMS SSL3 V3.0-11 Layered Product
VSI X86VMS TCPIP V6.0-23 Layered Product
VSI X86VMS VMS V9.2-2 Operating System
VSI X86VMS OPENVMS V9.2-3: OPENVMS and related products Platform
VSI X86VMS TCPIP V6.0-26: VSI TCP/IP Services for OpenVMS.
VSI X86VMS SSL3 V3.0-15: SSL3 for OpenVMS X86-64 V3.0-15 (Based on OpenSSL 3.0.15)
Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM:
@SYS$STARTUP:SSL3$STARTUP.COM
Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM:
@SYS$STARTUP:SSL3$SHUTDOWN.COM
Review the Installation Guide and Release Notes for post install directions.
Review the Installation Guide and Release Notes for post upgrade verification suggestions.
Refer to SYS$HELP:SSL30-15-X86.RELEASE_NOTES for more information.
Check the release notes for current status of the product.
VSI X86VMS KERBEROS V3.3-3
Configure and set up Kerberos
If Kerberos will be run on this system, but has not been
used previously, you need to perform the following steps.
o Run the Kerberos configuration procedure:
@SYS$STARTUP:KRB$CONFIGURE.COM
o Add the following line to SYS$MANAGER:SYSTARTUP_VMS.COM:
$ @SYS$STARTUP:KRB$STARTUP
o Add the following line to SYS$MANAGER:SYLOGIN.COM:
$ @SYS$MANAGER:KRB$SYMBOLS
VSI X86VMS SSL3 V3.0-15: SSL3 for OpenVMS X86-64 V3.0-15 (Based on OpenSSL 3.0.15)
Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM:
@SYS$STARTUP:SSL3$STARTUP.COM
Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM:
@SYS$STARTUP:SSL3$SHUTDOWN.COM
Review the Installation Guide and Release Notes for post install directions.
Review the Installation Guide and Release Notes for post upgrade verification suggestions.
Refer to SYS$HELP:SSL30-15-X86.RELEASE_NOTES for more information.
VSI X86VMS PERL540 V5.40-0
Post-installation tasks are required for Perl for OpenVMS.
To use the Perl provided with this kit, run the following set-up
command procedure, assuming you installed in SYS$COMMON.
$ @sys$common:[perl-5_40]perl_setup.com
You may wish to put that command in SYS$MANAGER:SYLOGIN.COM to
make Perl available to all users on the system.
Perl includes its own help system called perldoc. Type
$ perldoc perldoc
for the documentation to perldoc itself. Type
$ perldoc perldelta
for the changes that are new in version V5.40-0 of Perl.
There are many Perl-related resources on the web; point your
browser at:
http://www.perl.org
to get started, and thank you for using Perl for OpenVMS.
VSI X86VMS DECNET_PLUS V9.2-G: DECnet-Plus V9.2-G for OpenVMS X86
Release notes are available in SYS$HELP:HPE_DECNET-Plus-V84.RELEASE_NOTES
and SYS$HELP:VSI_DECNET_OSI.RELEASE_NOTES
%PCSI-I-SYSTEM_REBOOT, executing reboot procedure ...
Shutdown/reboot deferred when this product is
installed as part of the O/S installation/upgrade
%PCSI-I-SYSTEM_REBOOT, executing reboot procedure ...
Running SYS$UPDATE:SYS$MD.COM to update the memory disk...
Created memory disk DKB0:[VMS$COMMON.SYS$LDR]SYS$MD.DSK;2
- using 188560 blocks in 1 extent with 25692 spare blocks
- mounted on LDM5673: with volume label MD2430424F9B
- contains OpenVMS V9.2-3
The EFI Boot Manager menu includes multiple Boot Options
for DKB0:
Boot Options cannot be created or validated automatically.
Please use the OpenVMS X86-64 Boot Manager to ensure that you
have a valid Boot Option for this system.
You can run the OpenVMS X86-64 Boot Manager by choosing the DCL
option from the main menu and then execute this command:
$$$ @SYS$MANAGER:BOOT_OPTIONS
You can also execute this command from a properly privileged
account after booting your OpenVMS X86-64 system.
The upgrade is now complete.
When the newly upgraded system is first booted, a special
startup procedure will be run. This procedure will:
o Run AUTOGEN to set system parameters.
o Reboot the system with the newly set parameters.
You may shut down now or continue with other operations.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4