Sample Installation and Upgrade Logs¶
Note
Depending on the choices that you make during the installation, as well as your hypervisor of choice, certain parts of your log might look different.
Sample Installation Log¶
_______________________________________________
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, E9.2-4
Copyright 2026 VMS Software, Inc.
MDS Mitigation active, variant verw(MD_CLEAR)
%SMP-I-CPUTRN, CPU #2 has joined the active set.
%SMP-I-CPUTRN, CPU #3 has joined the active set.
%SMP-I-CPUTRN, CPU #7 has joined the active set.
%SMP-I-CPUTRN, CPU #1 has joined the active set.
%SMP-I-CPUTRN, CPU #6 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.
Installing required known files...
Configuring devices...
%EIA0, Link up: 1000 mbit, shared interrupts, 00-50-56-AC-EF-35
****************************************************************
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 E9.2-4
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] INITIALIZE
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)
------------ ------------------------- -------------- --------------------
DKA500: VMware Virtual disk
DKD2: VMware Virtual disk
For volume label and device size enter ??
Enter device name for target disk: (? for choices) DKA500
Enter volume label for target system disk: [X86SYS] X86SYS
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/?) YES
You have chosen to install OpenVMS X86-64 on a new disk.
The target system disk, DKA500:, 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) YES
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] 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: VS6613
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] 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.482
SCSSYSTEMID will be set to 1506.
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]: YES
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): NO
Enter the Time Differential Factor [1:00]: 1:00
NEW SYSTEM TIME DIFFERENTIAL FACTOR = 1:00
Is this correct? [Y]: 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] 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] NO
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-21 for OpenVMS X86-64 (based on OpenSSL V3.0.21)
o OpenSSH for OpenVMS X86-64
o OpenLDAP 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] 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-I?
(Yes/No) [Yes] 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] NO
Performing product kit validation of signed kits ...
%PCSI-I-VSIVALPASSED, validation of DMM1:[VMS$COMMON]VSI-X86VMS-VMS-E0902-4-2.PC
SI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.DWMOTIF_SUPPORT_X860924_KIT]VSI-X
86VMS-DWMOTIF_SUPPORT-E0902-4-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.AVAIL_MAN_BASE_KIT]VSI-X86VMS-AVA
IL_MAN_BASE-E0902-4-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.TCPIP]VSI-X86VMS-TCPIP-V0600-31-1
.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.SSL3]VSI-X86VMS-SSL3-V0300-21-1.P
CSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.KERBEROS]VSI-X86VMS-KERBEROS-V030
3-5A-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.OPENSSH]VSI-X86VMS-OPENSSH-V0909-
2C-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.OPENLDAP]VSI-X86VMS-OPENLDAP-V020
6-6B-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.PERL542]VSI-X86VMS-PERL542-V0542-
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_PLU
S-V0902-I-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.DECNET_PHASE_IV_X860924_KIT]VSI-X
86VMS-DECNET_PHASE_IV-E0902-4-1.PCSI$COMPRESSED;1 succeeded
The following product has been selected:
VSI X86VMS OPENVMS E9.2-4 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 E9.2-4: OPENVMS and related products Platform
Copyright 2015-2026 VMS Software, Inc.
VMS Software, Inc.
Do you want the defaults for all options? [YES] YES
Availability Manager (base) for OpenVMS X86-64
TCP/IP Services for OpenVMS X86-64
* Product VSI X86VMS TCPIP V6.0-31 requires a system reboot.
* Product VSI X86VMS AVAIL_MAN_BASE E9.2-4 recommends a system reboot.
Can the system be REBOOTED after the installation completes? [YES] YES
KERBEROS for OpenVMS X86-64
SSL3 V3.0-21 for OpenVMS X86-64 (based on OpenSSL V3.0.21)
OpenSSH for OpenVMS X86-64
OpenLDAP for OpenVMS X86-64
64-bit PERL for OpenVMS X86-64
Do you want to review the options? [NO] NO
Execution phase starting ...
The following products will be installed to destinations:
VSI X86VMS AVAIL_MAN_BASE E9.2-4 DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS DECNET_PLUS V9.2-I DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS DWMOTIF V1.8-2 DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS DWMOTIF_SUPPORT E9.2-4 DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS KERBEROS V3.3-5A DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS OPENLDAP V2.6-6B DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS OPENSSH V9.9-2C DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS OPENVMS E9.2-4 DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS PERL542 V5.42-0 DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS SSL3 V3.0-21 DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS TCPIP V6.0-31 DISK$X86SYS:[VMS$COMMON.]
VSI X86VMS VMS E9.2-4 DISK$X86SYS:[VMS$COMMON.]
Portion done: 0%...10%...20%...30%...40%...50%...60%
Restoring STARTUP.NSH file(s)...
No files restored
...70%...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 E9.2-4 Layered Product
VSI X86VMS DECNET_PLUS V9.2-I Layered Product
VSI X86VMS DWMOTIF V1.8-2 Layered Product
VSI X86VMS DWMOTIF_SUPPORT E9.2-4 Layered Product
VSI X86VMS KERBEROS V3.3-5A Layered Product
VSI X86VMS OPENLDAP V2.6-6B Layered Product
VSI X86VMS OPENSSH V9.9-2C Layered Product
VSI X86VMS OPENVMS E9.2-4 Platform (product suite)
VSI X86VMS PERL542 V5.42-0 Layered Product
VSI X86VMS SSL3 V3.0-21 Layered Product
VSI X86VMS TCPIP V6.0-31 Layered Product
VSI X86VMS VMS E9.2-4 Operating System
VSI X86VMS OPENVMS E9.2-4: OPENVMS and related products Platform
VSI X86VMS TCPIP V6.0-31: VSI TCP/IP Services for OpenVMS.
VSI X86VMS SSL3 V3.0-21: SSL3 for OpenVMS X86-64 V3.0-21 (Based on OpenSSL 3.0.21)
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-21-X86.RELEASE_NOTES for more information.
Check the release notes for current status of the product.
VSI X86VMS KERBEROS V3.3-5A
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-21: SSL3 for OpenVMS X86-64 V3.0-21 (Based on OpenSSL 3.0.21)
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-21-X86.RELEASE_NOTES for more information.
VSI X86VMS OPENLDAP V2.6-6B: OpenLDAP for OpenVMS X86 V2.6-6B (Based on Open LDAP 2.6.6)
Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM:
@SYS$STARTUP:LDAP$DEFINE_LOGICALS.COM
Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM:
@SYS$STARTUP:LDAP$DEASSIGN_LOGICALS.COM
Verify the OpenLDAP configuration template files.
Refer to SYS$HELP:OPENLDAP0206-6B-X86.RELEASE_NOTES for more information.
Following installation, before the new ACME LDAP agent can be
deployed, the OpenLDAP persona extension must be installed and then
the system must be rebooted (it is not sufficient to simply restart the
ACME server). Follow the post installation instructions provided in the
release notes to complete configuration of the software.
VSI X86VMS PERL542 V5.42-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_42]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.42-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-I: DECnet-Plus V9.2-I 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...
Updating the system memory disk. Please do not interrupt this procedure...
Created memory disk DKA500:[VMS$COMMON.SYS$LDR]SYS$MD.DSK;1
- using 171088 blocks in 1 extent with 18975 spare blocks
- mounted on LDM3034: with volume label MD2623833E6A
- contains OpenVMS E9.2-4
%LD-I-UNIT, Allocated device is LDM3035:
%LMFINSTALL-I-SUCCESS, License installed with 8 units, Termination: 31-AUG-2026
BootOrder Entries: 6, Timeout: Has not been set
[01] Boot0006 <- Current
[02] Boot0001 [03] Boot0002 [04] Boot0003 [05] Boot0004
[06] Boot0000
Validate Boot Options list: Timeout: 0 secs.
________________________________________________________________________
6 EFI Virtual disk (5.0)
DevPath: DKA500 PCI(0x0,0x0,0x10,0x0)/Scsi(5,0)
Options: None
WARNING - Entry 6 validation failed. Repairing...
SUCCESS - Entry in position 6 (Boot0000) was removed.
SUCCESS - Added: DKA500 PCI(0x0,0x0,0x10,0x0)/Scsi(5,0) (Boot0005)
________________________________________________________________________
Validated 6 entries.
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 26-AUG-2026 21:53:54.64
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 E9.2-4
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 VMware Virtual SATA CDROM Drive (0.0)...
Scanning devices and preparing the OpenVMS Boot Manager Build 160...
%VMS_BOOTMGR-I-GRAPHICS, Using Rendered Text Console (1600 x 1200)
VSI OpenVMS Boot Manager: V9.2-* Build 160
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
Identifying devices. This may take a while. COMPLETED
VIRTUAL MACHINE GUEST:
VMware (tm) No Mouse support; Use Commands or Arrow Keys
BOOT MANAGER DEVICE: DKB0
DEFAULT BOOT COMMAND: BOOT DKA500 0x00 0x00000000
AUTOACTION: HALT
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.
V DKA500 (HD) = FS0 UEFI: E9_2_4 VMS: X86SYS 21504 MB SCSI Disk
B DKB0 (DVD) = FS1 UEFI: E9_2_4 VMS: None 1295 MB SATA DVD
BOOTMGR> BOOT DKA500
Booting...
%VMS_BOOTMGR-I-SECBOOT, SYSBOOT signature validated.
%%%%%%%%%%% 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, E9.2-4
Copyright 2026 VMS Software, Inc.
MDS Mitigation active, variant verw(MD_CLEAR)
%DECnet-I-LOADED, network base image loaded, version = 05.92.09
%DECnet-W-ZEROLEN, length of file is zero -- SYS$SYSROOT:[SYSEXE]NET$CONFIG.DAT
%SMP-I-CPUTRN, CPU #7 has joined the active set.
%SMP-I-CPUTRN, CPU #6 has joined the active set.
%SMP-I-CPUTRN, CPU #3 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 #2 has joined the active set.
%SMP-I-CPUTRN, CPU #1 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.
%%%%%%%%%%% OPCOM 27-AUG-2026 11:56:09.08 %%%%%%%%%%%
Operator _VS6613$OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 27-AUG-2026 11:56:09.08 %%%%%%%%%%%
Operator status for operator _VS6613$OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%%%%%%%%%%% OPCOM 27-AUG-2026 11:56:09.09 %%%%%%%%%%%
Logfile has been initialized by operator _VS6613$OPA0:
Logfile is VS6613::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
%%%%%%%%%%% OPCOM 27-AUG-2026 11:56:09.09 %%%%%%%%%%%
Operator status for operator VS6613::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%SYSTEM-I-BOOTUPGRADE, security auditing disabled
%%%%%%%%%%% OPCOM 27-AUG-2026 11:56:09.18 %%%%%%%%%%%
Message from user SYSTEM on VS6613
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 27-AUG-2026 11:56:09.19 %%%%%%%%%%%
Message from user SYSTEM on VS6613
-RMS-E-FNF, file not found
%SYSTEM-I-BOOTUPGRADE, security server not started
%SYSTEM-I-BOOTUPGRADE, ACME server not started
%%%%%%%%%%% OPCOM 27-AUG-2026 11:56:09.31 %%%%%%%%%%%
Message from user SYSTEM on VS6613
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, shared interrupts, 00-50-56-AC-EF-35
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, Created a new version of SYS$SYSTEM:PARAMS.DAT
You may wish to PURGE SYS$SYSTEM:PARAMS.DAT
%AUTOGEN-S-END, GETDATA phase has successfully completed.
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.
%AUTOGEN-I-NEWFILE, Created a new version of SYS$MANAGER:VMSIMAGES.DAT
You may wish to PURGE SYS$MANAGER:VMSIMAGES.DAT
%AUTOGEN-I-NEWFILE, Created a new version of SYS$SYSTEM:SETPARAMS.DAT
You may wish to PURGE SYS$SYSTEM:SETPARAMS.DAT
%AUTOGEN-S-END, GENPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, GENFILES phase is beginning.
Calculations for dump and page files.
-------------------------------------
Errorlog dump file calculations:
A 154 block Errorlog dump file will be created.
%SYSGEN-I-CREATED, SYS$SYSROOT:[SYSEXE]SYS$ERRLOG.DMP;2 created
** WARNING ** - No page files are currently installed.
This may eventually cause a system hang or failure.
Dump file calculations:
Current file is DKA500:[SYS0.SYSEXE]SYSDUMP.DMP
This file does not yet exist and should be created.
Proposed file size is: 78559601 blocks.
Page file calculations:
A PAGEFILE does not currently exist and will not be created.
** WARNING ** - The system disk would have only free
blocks if the dump file were created with 000078559601 blocks.
No dump file modifications were made on device DKA500:.
Dumpfile on device DKA500: will remain at 0 blocks.
Disk Block Utilization: _DKA500: ~5%
Total: 000044040192
Used: 000002524768
Free: 000041525424
******************
%AUTOGEN-W-REPORT, Warnings were detected by AUTOGEN.
Please review the information in: SYS$SYSTEM:AGEN$PARAMS.REPORT
******************
%AUTOGEN-S-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 27-AUG-2026 11:56:24.92 %%%%%%%%%%%
Message from user SYSTEM on VS6613
%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-S-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 VS6613
%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 27-AUG-2026 11:56:25.32 %%%%%%%%%%%
Message from user SYSTEM on VS6613
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 27-AUG-2026 11:56:25.32 %%%%%%%%%%%
Message from user SYSTEM on VS6613
-RMS-E-FNF, file not found
SHUTDOWN message on VS6613 from user SYSTEM at VS6613 Batch 11:56:25
VS6613 will shut down in 0 minutes; back up soon. Please log off node VS6613.
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.
%SMP-I-CPUTRN, CPU #6 was removed from the active set.
%SMP-I-CPUTRN, CPU #7 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 27-AUG-2026 11:56:25.69 %%%%%%%%%%%
Message from user SYSTEM on VS6613
STARTUP, VS6613 shutdown was requested by the operator.
VSI Dump Kernel - Handles Shutdown/Reboot/Crash Dumps
** Dumping error logs to the system disk (VS6613$DKA500:)
** Error logs dumped to VS6613$DKA500:[SYS0.SYSEXE]SYS$ERRLOG.DMP
** (used 36 out of 160 available blocks)
Restarting the system...
Attempting to start up from:
> EFI Virtual disk (0.0)... unsuccessful.
> EFI VMware Virtual SATA CDROM Drive (0.0)...
Scanning devices and preparing the OpenVMS Boot Manager Build 160...
VSI OpenVMS Boot Manager: V9.2-* Build 160
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
Identifying devices. This may take a while. COMPLETED
VIRTUAL MACHINE GUEST:
VMware (tm) No Mouse support; Use Commands or Arrow Keys
BOOT MANAGER DEVICE: DKB0
DEFAULT BOOT COMMAND: BOOT DKA500 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.
V DKA500 (HD) = FS0 UEFI: E9_2_4 VMS: X86SYS 21504 MB SCSI Disk
B DKB0 (DVD) = FS1 UEFI: E9_2_4 VMS: None 1295 MB SATA DVD
BOOTMGR> BOOT
Booting...
%VMS_BOOTMGR-I-SECBOOT, SYSBOOT signature validated.
%%%%%%%%%%% 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, E9.2-4
Copyright 2026 VMS Software, Inc.
MDS Mitigation active, variant verw(MD_CLEAR)
%DECnet-I-LOADED, network base image loaded, version = 05.92.09
%DECnet-W-ZEROLEN, length of file is zero -- SYS$SYSROOT:[SYSEXE]NET$CONFIG.DAT
%SMP-I-CPUTRN, CPU #3 has joined the active set.
%SMP-I-CPUTRN, CPU #6 has joined the active set.
%SMP-I-CPUTRN, CPU #7 has joined the active set.
%SMP-I-CPUTRN, CPU #4 has joined the active set.
%SMP-I-CPUTRN, CPU #2 has joined the active set.
%SMP-I-CPUTRN, CPU #5 has joined the active set.
%SMP-I-CPUTRN, CPU #1 has joined the active set.
%STDRV-I-STARTUP, OpenVMS startup begun at 27-AUG-2026 12:57:09.07
%EIA0, Link up: 1000 mbit, shared interrupts, 00-50-56-AC-EF-35
%RUN-S-PROC_ID, identification of created process is 00000804
%RUN-S-PROC_ID, identification of created process is 00000805
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:16.51 %%%%%%%%%%%
Operator _VS6613$OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:16.51 %%%%%%%%%%%
Operator status for operator _VS6613$OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:16.53 %%%%%%%%%%%
Logfile has been initialized by operator _VS6613$OPA0:
Logfile is VS6613::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;2
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:16.53 %%%%%%%%%%%
Operator status for operator VS6613::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
%SET-I-NEWAUDSRV, identification of new audit server process is 0000080B
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:16.57 %%%%%%%%%%%
Message from user AUDIT$SERVER on VS6613
%AUDSRV-I-NEWSERVERDB, new audit server database created ( PC 00000000.8000C7A9)
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:16.58 %%%%%%%%%%%
Message from user SYSTEM on VS6613
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:16.58 %%%%%%%%%%%
Message from user SYSTEM on VS6613
-RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:16.59 %%%%%%%%%%%
Message from user AUDIT$SERVER on VS6613
%AUDSRV-I-REMENABLED, resource monitoring enabled for journal SECURITY
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:16.60 %%%%%%%%%%%
Message from user AUDIT$SERVER on VS6613
%AUDSRV-I-NEWOBJECTDB, new object database created ( PC 00000000.8000F4CD)
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:16.66 %%%%%%%%%%%
Message from user SYSTEM on VS6613
%SECSRV-I-SERVERSTARTINGU, security server starting up
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:16.66 %%%%%%%%%%%
Message from user SYSTEM on VS6613
%SECSRV-I-CIACRECLUDB, security server created cluster intrusion database
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:16.67 %%%%%%%%%%%
Message from user SYSTEM on VS6613
%SECSRV-I-CIASTARTINGUP, breakin detection and evasion processing now starting u
p
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:16.68 %%%%%%%%%%%
Message from user SYSTEM on VS6613
%ACME-I-SERVERSTART, ACME_SERVER starting
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:19.67 %%%%%%%%%%%
Message from user SYSTEM on VS6613
%SECSRV-I-PROXYSTARTINGUP, proxy processing now starting up
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:19.68 %%%%%%%%%%%
Message from user SYSTEM on VS6613
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:24.77 %%%%%%%%%%%
Message from user SYSTEM on VS6613
TDF-I-SETTDF TDF set new timezone differential
Copyright 2026 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 27-AUG-2026 12:57:25.65 %%%%%%%%%%%
Message from user AUDIT$SERVER on VS6613
Security alarm (SECURITY) and security audit (SECURITY) on VS6613, system id: 15
06
Auditable event: Audit server starting up
Event time: 27-AUG-2026 12:57:25.64
PID: 00000803
Username: SYSTEM
The OpenVMS system is now executing the site-specific startup commands.
%UAF-I-RDBADDMSG, identifier SYS$NODE_VS6613 value %X80010000 added to rights da
tabase
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:25.97 %%%%%%%%%%%
Message from user AUDIT$SERVER on VS6613
Security alarm (SECURITY) and security audit (SECURITY) on VS6613, system id: 15
06
Auditable event: Identifier added
Event time: 27-AUG-2026 12:57:25.96
PID: 00000803
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: VS6613$DKA500:[SYS0.SYSCOMMON.][SYSEXE]AUTHORIZE.EXE
Identifier name: SYS$NODE_VS6613
Identifier value: %X80010000
Attributes: none
Posix UID: -2
Posix GID: -2 (%XFFFFFFFE)
%DECW$DEVICE-I-NODEVICE, no graphics devices found.
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:26.04 %%%%%%%%%%%
Message from user AUDIT$SERVER on VS6613
Security alarm (SECURITY) and security audit (SECURITY) on VS6613, system id: 15
06
Auditable event: Identifier added
Event time: 27-AUG-2026 12:57:26.04
PID: 00000803
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: VS6613$DKA500:[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 27-AUG-2026 12:57:26.07 %%%%%%%%%%%
Message from user AUDIT$SERVER on VS6613
Security alarm (SECURITY) and security audit (SECURITY) on VS6613, system id: 15
06
Auditable event: Identifier added
Event time: 27-AUG-2026 12:57:26.07
PID: 00000803
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: VS6613$DKA500:[SYS0.SYSCOMMON.][SYSEXE]IMGDMP_RIGHTS.E
XE;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
%PROCDUMP-I-CREATED, rights identifier IMGDMP$PROTECT successfully created
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:26.09 %%%%%%%%%%%
Message from user AUDIT$SERVER on VS6613
Security alarm (SECURITY) and security audit (SECURITY) on VS6613, system id: 15
06
Auditable event: Identifier added
Event time: 27-AUG-2026 12:57:26.09
PID: 00000803
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: VS6613$DKA500:[SYS0.SYSCOMMON.][SYSEXE]IMGDMP_RIGHTS.E
XE;1
Identifier name: IMGDMP$PROTECT
Identifier value: %X90390002
Attributes: RESOURCE
Posix UID: -2
Posix GID: -2 (%XFFFFFFFE)
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
%RUN-S-PROC_ID, identification of created process is 00000812
%%%%%%%%%%% OPCOM 27-AUG-2026 12:57:26.25 %%%%%%%%%%%
Message from user SYSTEM on VS6613
%SMHANDLER-S-STARTUP, server management event handler startup
SYSTEM job terminated at 27-AUG-2026 12:57:28.24
Accounting information:
Buffered I/O count: 3093 Peak working set size: 13616
Direct I/O count: 4594 Peak virtual size: 258032
Page faults: 3778 Mounted volumes: 0
Charged CPU time: 0 00:00:03.84 Elapsed time: 0 00:00:19.40
Welcome to OpenVMS (TM) x86_64 Operating System, Version E9.2-4Sample Upgrade Log¶
VSI OpenVMS Boot Manager: V9.2-* Build 160
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
Identifying devices. This may take a while. COMPLETED
VIRTUAL MACHINE GUEST:
VMware (tm) No Mouse support; Use Commands or Arrow Keys
BOOT MANAGER DEVICE: DKB0
DEFAULT BOOT COMMAND: BOOT DKB100 0x00 0x00000001
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.
V DKB100 (HD) = FS0 UEFI: V9_2_3 VMS: X86SYS1 18432 MB SATA Disk
B DKB0 (DVD) = FS1 UEFI: E9_2_4 VMS: None 1295 MB SATA DVD
BOOTMGR> BOOT DKB0
Booting...
%VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
%VMS_BOOTMGR-I-INSTALL, Extracting ISO file size from Primary Volume Descriptor...
100%
%VMS_BOOTMGR-I-SECBOOT, SYSBOOT signature validated.
%%%%%%%%%%% 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
SYSBOOT> CONTINUE
VMS Software, Inc. OpenVMS (TM) x86_64 Operating System, E9.2-4
Copyright 2026 VMS Software, Inc.
MDS Mitigation active, variant verw(MD_CLEAR)
%SMP-I-CPUTRN, CPU #4 has joined the active set.
%SMP-I-CPUTRN, CPU #2 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.
%SMP-I-CPUTRN, CPU #1 has joined the active set.
Installing required known files...
Configuring devices...
%EIA0, Link up: 10 gbit, 00-50-56-AC-3D-77
****************************************************************
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 E9.2-4
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] 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)
------------ ------------------------- -------------- --------------------
DKB100: ATA VMware Virtual
DKB200: ATA VMware Virtual
For volume label and device size enter ??
Enter device name for target disk: (? for choices) DKB100
The target system has recovery data from PRODUCT INSTALL
operations which used the /SAVE_RECOVERY_DATA qualifier.
This data must be deleted to continue the OpenVMS upgrade.
Please examine the following display.
If you want to delete this data and continue the OpenVMS upgrade,
answer YES to the question "Do you want to continue?"
If you do not want to delete this data, answer NO. A NO answer
will preserve the recovery data and abort the OpenVMS upgrade.
The following patch recovery data has been selected:
RECOVERY DATA SET 001 created 19-AUG-2026 16:31:17.95
-------------------------------------- --------------------------------------
PATCH APPLIED TO
-------------------------------------- --------------------------------------
VSI X86VMS VMS923X_BOOTMGR V1.0 VSI X86VMS VMS V9.2-3
-------------------------------------- --------------------------------------
RECOVERY DATA SET 002 created 19-AUG-2026 16:30:52.59
-------------------------------------- --------------------------------------
PATCH APPLIED TO
-------------------------------------- --------------------------------------
VSI X86VMS VMS923X_PCSI V1.0 VSI X86VMS VMS V9.2-3
-------------------------------------- --------------------------------------
* If you continue, recovery data for the patches listed above will be deleted.
* The deletion of recovery data does not affect the installation status of
* patches applied to products that are not participating in this operation.
* However, continuing with this operation will prevent you from uninstalling
* these patches at a future time by use of the PRODUCT UNDO PATCH command.
Do you want to continue? [YES] YES
Deleting RECOVERY DATA SET 002 ...
Deleting RECOVERY DATA SET 001 ...
DKB100: is now labeled X86SYS1.
Do you want to keep this label? (Yes/No) [Yes] YES
OpenVMS X86-64 will be upgraded on DKB100:.
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] NO
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-21 for OpenVMS X86-64 (based on OpenSSL V3.0.21)
o OpenSSH for OpenVMS X86-64
o OpenLDAP 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-21 for OpenVMS X86-64 (based on OpenSSL V3.0.21)
is installed on your system. It will be upgraded.
OpenSSH for OpenVMS X86-64
is installed on your system. It will be upgraded.
OpenLDAP for OpenVMS X86-64 is required.
It will be installed.
64-bit PERL for OpenVMS X86-64 is required.
It will be installed.
DECwindows Motif for OpenVMS X86-64 V1.8-2
is already installed on your system. An upgrade is not required.
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] 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-E0902-4-2.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.DWMOTIF_SUPPORT_X860924_KIT]VSI-X86VMS-DWMOTIF_SUPPORT-E0902-4-1.PCSI$COMPRESSED;1 su
cceeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.AVAIL_MAN_BASE_KIT]VSI-X86VMS-AVAIL_MAN_BASE-E0902-4-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.TCPIP]VSI-X86VMS-TCPIP-V0600-31-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.SSL3]VSI-X86VMS-SSL3-V0300-21-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.KERBEROS]VSI-X86VMS-KERBEROS-V0303-5A-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.OPENSSH]VSI-X86VMS-OPENSSH-V0909-2C-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.OPENLDAP]VSI-X86VMS-OPENLDAP-V0206-6B-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.PERL542]VSI-X86VMS-PERL542-V0542-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-I-1.PCSI$COMPRESSED;1 succeeded
%PCSI-I-VSIVALPASSED, validation of DMM1:[KITS.DECNET_PHASE_IV_X860924_KIT]VSI-X86VMS-DECNET_PHASE_IV-E0902-4-1.PCSI$COMPRESSED;1 su
cceeded
The following product has been selected:
VSI X86VMS OPENVMS E9.2-4 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 E9.2-4: OPENVMS and related products Platform
Copyright 2015-2026 VMS Software, Inc.
VMS Software, Inc.
Do you want the defaults for all options? [YES] YES
Availability Manager (base) for OpenVMS X86-64
TCP/IP Services for OpenVMS X86-64
* Product VSI X86VMS TCPIP V6.0-31 requires a system reboot.
* Product VSI X86VMS AVAIL_MAN_BASE E9.2-4 recommends a system reboot.
Can the system be REBOOTED after the installation completes? [YES] YES
KERBEROS for OpenVMS X86-64
SSL3 V3.0-21 for OpenVMS X86-64 (based on OpenSSL V3.0.21)
OpenSSH for OpenVMS X86-64
OpenLDAP for OpenVMS X86-64
64-bit PERL for OpenVMS X86-64
Do you want to review the options? [NO] NO
Execution phase starting ...
The following products will be installed to destinations:
VSI X86VMS AVAIL_MAN_BASE E9.2-4 DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS DECNET_PLUS V9.2-I DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS DWMOTIF_SUPPORT E9.2-4 DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS KERBEROS V3.3-5A DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS OPENLDAP V2.6-6B DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS OPENSSH V9.9-2C DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS OPENVMS E9.2-4 DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS PERL542 V5.42-0 DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS SSL3 V3.0-21 DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS TCPIP V6.0-31 DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS VMS E9.2-4 DISK$X86SYS1:[VMS$COMMON.]
The following products will be removed from destinations:
VSI X86VMS AVAIL_MAN_BASE V9.2-3 DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS DECNET_PLUS V9.2-G DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS DWMOTIF_SUPPORT V9.2-3 DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS KERBEROS V3.3-3 DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS OPENSSH V8.9-1J DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS OPENVMS V9.2-3 DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS PERL540 V5.40-0 DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS SSL111 V1.1-1W DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS SSL3 V3.0-15 DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS TCPIP V6.0-26 DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS VMS V9.2-3 DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS VMS923X_BOOTMGR V1.0 DISK$X86SYS1:[VMS$COMMON.]
VSI X86VMS VMS923X_PCSI V1.0 DISK$X86SYS1:[VMS$COMMON.]
Portion done: 0%
Backup OpenSSH configuration files? [y/n]: [y] YES
...The configuration files were backed up
in pcsi$destination:[sys0.syscommon.ssh$safety]*.*;
SSH$ROOT: directory tree successfully removed
from AG4002$DKB100:[SYS0.SYSCOMMON.OPENSSH]
...10%...20%...30%...40%...50%...60%...70%...80%
Restoring STARTUP.NSH file(s)...
No files restored
...90%...100%
The following products have been installed:
VSI X86VMS AVAIL_MAN_BASE E9.2-4 Layered Product
VSI X86VMS DECNET_PLUS V9.2-I Layered Product
VSI X86VMS DWMOTIF_SUPPORT E9.2-4 Layered Product
VSI X86VMS KERBEROS V3.3-5A Layered Product
VSI X86VMS OPENLDAP V2.6-6B Layered Product
VSI X86VMS OPENSSH V9.9-2C Layered Product
VSI X86VMS OPENVMS E9.2-4 Platform (product suite)
VSI X86VMS PERL542 V5.42-0 Layered Product
VSI X86VMS SSL3 V3.0-21 Layered Product
VSI X86VMS TCPIP V6.0-31 Layered Product
VSI X86VMS VMS E9.2-4 Operating System
The following products have been removed:
VSI X86VMS AVAIL_MAN_BASE V9.2-3 Layered Product
VSI X86VMS DECNET_PLUS V9.2-G 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 VMS923X_BOOTMGR V1.0 Patch (maintenance update)
VSI X86VMS VMS923X_PCSI V1.0 Patch (maintenance update)
VSI X86VMS OPENVMS E9.2-4: OPENVMS and related products Platform
VSI X86VMS TCPIP V6.0-31: VSI TCP/IP Services for OpenVMS.
VSI X86VMS SSL3 V3.0-21: SSL3 for OpenVMS X86-64 V3.0-21 (Based on OpenSSL 3.0.21)
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-21-X86.RELEASE_NOTES for more information.
Check the release notes for current status of the product.
VSI X86VMS KERBEROS V3.3-5A
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-21: SSL3 for OpenVMS X86-64 V3.0-21 (Based on OpenSSL 3.0.21)
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-21-X86.RELEASE_NOTES for more information.
VSI X86VMS OPENLDAP V2.6-6B: OpenLDAP for OpenVMS X86 V2.6-6B (Based on OpenLDAP 2.6.6)
Insert the following lines in SYS$MANAGER:SYSTARTUP_VMS.COM:
@SYS$STARTUP:LDAP$DEFINE_LOGICALS.COM
Insert the following lines in SYS$MANAGER:SYSHUTDWN.COM:
@SYS$STARTUP:LDAP$DEASSIGN_LOGICALS.COM
Verify the OpenLDAP configuration template files.
Refer to SYS$HELP:OPENLDAP0206-6B-X86.RELEASE_NOTES for more information.
Following installation, before the new ACME LDAP agent can be
deployed, the OpenLDAP persona extension must be installed and then
the system must be rebooted (it is not sufficient to simply restart the
ACME server). Follow the post installation instructions provided in the
release notes to complete configuration of the software.
VSI X86VMS PERL542 V5.42-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_42]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.42-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-I: DECnet-Plus V9.2-I 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...
Updating the system memory disk. Please do not interrupt this procedure...
Created memory disk DKB100:[VMS$COMMON.SYS$LDR]SYS$MD.DSK;2
- using 171088 blocks in 1 extent with 18969 spare blocks
- mounted on LDM2995: with volume label MD26235442DB
- contains OpenVMS E9.2-4
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.
Process X86VMS_INSTALL logged out at 23-AUG-2026 23:03:21.23
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 E9.2-4
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...
Shell> FS1:
fs1:\> cd efi\vms
fs1:\EFI\VMS> vms_bootmgr.efi
Scanning devices and preparing the OpenVMS Boot Manager Build 160...
VSI OpenVMS Boot Manager: V9.2-* Build 160
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
Identifying devices. This may take a while. COMPLETED
VIRTUAL MACHINE GUEST:
VMware (tm) No Mouse support; Use Commands or Arrow Keys
BOOT MANAGER DEVICE: DKB0
DEFAULT BOOT COMMAND: BOOT DKB100 0x00 0x00000001
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.
V DKB100 (HD) = FS0 UEFI: E9_2_4 VMS: X86SYS1 18432 MB SATA Disk
B DKB0 (DVD) = FS1 UEFI: E9_2_4 VMS: None 1295 MB SATA DVD
BOOTMGR> BOOT DKB100
Booting...
%VMS_BOOTMGR-I-SECBOOT, SYSBOOT signature validated.
%%%%%%%%%%% 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
SYSBOOT> CONTINUE
VMS Software, Inc. OpenVMS (TM) x86_64 Operating System, E9.2-4
Copyright 2026 VMS Software, Inc.
MDS Mitigation active, variant verw(MD_CLEAR)
%DECnet-I-LOADED, network base image loaded, version = 05.92.09
%SMP-I-CPUTRN, CPU #2 has joined the active set.
%SMP-I-CPUTRN, CPU #1 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 #5 has joined the active set.
Installing required known files...
Configuring devices...
%RUN-S-PROC_ID, identification of created process is 00000404
%STARTUP-E-NOPAGFIL, No page files have been successfully installed.
%%%%%%%%%%% OPCOM 24-AUG-2026 14:05:19.24 %%%%%%%%%%%
Operator _AG4002$OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 24-AUG-2026 14:05:19.24 %%%%%%%%%%%
Operator status for operator _AG4002$OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%%%%%%%%%%% OPCOM 24-AUG-2026 14:05:19.25 %%%%%%%%%%%
Logfile has been initialized by operator _AG4002$OPA0:
Logfile is AG4002::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;6
%%%%%%%%%%% OPCOM 24-AUG-2026 14:05:19.25 %%%%%%%%%%%
Operator status for operator AG4002::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;6
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%SYSTEM-I-BOOTUPGRADE, security auditing disabled
%%%%%%%%%%% OPCOM 24-AUG-2026 14:05:19.29 %%%%%%%%%%%
Message from user SYSTEM on AG4002
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 24-AUG-2026 14:05:19.29 %%%%%%%%%%%
Message from user SYSTEM on AG4002
-RMS-E-FNF, file not found
%SYSTEM-I-BOOTUPGRADE, security server not started
%SYSTEM-I-BOOTUPGRADE, ACME server not started
%%%%%%%%%%% OPCOM 24-AUG-2026 14:05:19.44 %%%%%%%%%%%
Message from user SYSTEM on AG4002
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: 10 gbit, 00-50-56-AC-3D-77
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, Created a new version of SYS$SYSTEM:PARAMS.DAT
You may wish to PURGE SYS$SYSTEM:PARAMS.DAT
%AUTOGEN-S-END, GETDATA phase has successfully completed.
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.
%AUTOGEN-I-NEWFILE, Created a new version of SYS$MANAGER:VMSIMAGES.DAT
You may wish to PURGE SYS$MANAGER:VMSIMAGES.DAT
%AUTOGEN-I-NEWFILE, Created a new version of SYS$SYSTEM:SETPARAMS.DAT
You may wish to PURGE SYS$SYSTEM:SETPARAMS.DAT
%AUTOGEN-S-END, GENPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, GENFILES phase is beginning.
Calculations for dump and page files.
-------------------------------------
Errorlog dump file calculations:
A 122 block Errorlog dump file will be created.
%SYSGEN-I-CREATED, SYS$SYSROOT:[SYSEXE]SYS$ERRLOG.DMP;3 created
** WARNING ** - No page files are currently installed.
This may eventually cause a system hang or failure.
Dump file calculations:
Current file is DKB100:[SYS0.SYSEXE]SYSDUMP.DMP
Current file size is 12052186 blocks.
Page file calculations:
A PAGEFILE does not currently exist and will not be created.
Creating incremental 200000 block file...
%SYSGEN-I-CREATED, DKB100:[SYS0.SYSEXE]SYSDUMP.DMP;2 created
%SYSGEN-I-EXTENDED, DKB100:[SYS0.SYSEXE]SYSDUMP.DMP;2 extended
Disk Block Utilization: _DKB100: ~40%
Total: 000037748736
Used: 000015384112
Free: 000022364624
******************
%AUTOGEN-W-REPORT, Warnings were detected by AUTOGEN.
Please review the information in: SYS$SYSTEM:AGEN$PARAMS.REPORT
******************
%AUTOGEN-S-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 24-AUG-2026 14:05:34.67 %%%%%%%%%%%
Message from user SYSTEM on AG4002
%SYSGEN-I-WRITECUR, CURRENT system parameters modified by process ID 00000403 in
to file SYS$SYSROOT_MD:[SYSEXE]X86_64VMSSYS.PAR;1
%AUTOGEN-I-SYSGEN, parameters modified
%AUTOGEN-S-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 AG4002
%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 24-AUG-2026 14:05:35.12 %%%%%%%%%%%
Message from user SYSTEM on AG4002
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 24-AUG-2026 14:05:35.12 %%%%%%%%%%%
Message from user SYSTEM on AG4002
-RMS-E-FNF, file not found
SHUTDOWN message on AG4002 from user SYSTEM at AG4002 Batch 14:05:35
AG4002 will shut down in 0 minutes; back up soon. Please log off node AG4002.
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 24-AUG-2026 14:05:35.49 %%%%%%%%%%%
Message from user SYSTEM on AG4002
STARTUP, AG4002 shutdown was requested by the operator.
VSI Dump Kernel - Handles Shutdown/Reboot/Crash Dumps
** Dumping error logs to the system disk (AG4002$DKB100:)
** Error logs dumped to AG4002$DKB100:[SYS0.SYSEXE]SYS$ERRLOG.DMP
** (used 116 out of 128 available blocks)
Restarting the system...
Attempting to start up from:
> EFI Internal Shell (Unsupported option)...
EFI Shell version 2.70 [1.0]
Current running mode 1.1.2
Device mapping table
fs0 :HardDisk - Alias hd23b0a1 blk0
PciRoot(0x0)/Pci(0x11,0x0)/Pci(0x3,0x0)/Sata(0x1,0x0,0x0)/HD(1,GPT,6D588E99-9BE7-11F1-94DA-AA000400FEFF,0x266530,0x3E8 00)
fs1 :CDRom - Alias cd23a0a0 blk1
PciRoot(0x0)/Pci(0x11,0x0)/Pci(0x3,0x0)/Sata(0x0,0x0,0x0)/CDROM(0x0,0x1B,0xE800)
blk0 :HardDisk - Alias hd23b0a1 fs0
PciRoot(0x0)/Pci(0x11,0x0)/Pci(0x3,0x0)/Sata(0x1,0x0,0x0)/HD(1,GPT,6D588E99-9BE7-11F1-94DA-AA000400FEFF,0x266530,0x3E8 00)
blk1 :CDRom - Alias cd23a0a0 fs1
PciRoot(0x0)/Pci(0x11,0x0)/Pci(0x3,0x0)/Sata(0x0,0x0,0x0)/CDROM(0x0,0x1B,0xE800)
blk2 :HardDisk - Alias (null)
PciRoot(0x0)/Pci(0x11,0x0)/Pci(0x3,0x0)/Sata(0x1,0x0,0x0)/HD(2,GPT,6D588E9A-9BE7-11F1-94D8-AA000400FEFF,0x30,0x266500)
blk3 :HardDisk - Alias (null)
PciRoot(0x0)/Pci(0x11,0x0)/Pci(0x3,0x0)/Sata(0x1,0x0,0x0)/HD(3,GPT,6D588E99-9BE7-11F1-94D9-AA000400FEFF,0x2A4D30,0x215 B2AF)
blk4 :BlockDevice - Alias (null)
PciRoot(0x0)/Pci(0x11,0x0)/Pci(0x3,0x0)/Sata(0x0,0x0,0x0)
blk5 :BlockDevice - Alias (null)
PciRoot(0x0)/Pci(0x11,0x0)/Pci(0x3,0x0)/Sata(0x1,0x0,0x0)
blk6 :BlockDevice - Alias (null)
PciRoot(0x0)/Pci(0x11,0x0)/Pci(0x3,0x0)/Sata(0x2,0x0,0x0)
Press ESC in 1 seconds to skip startup.nsh, any other key to continue.
Shell>
Shell> FS1:
fs1:\> cd efi\vms
fs1:\EFI\VMS> vms_bootmgr.efi
Scanning devices and preparing the OpenVMS Boot Manager Build 160...
VSI OpenVMS Boot Manager: V9.2-* Build 160
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
Identifying devices. This may take a while. COMPLETED
VIRTUAL MACHINE GUEST:
VMware (tm) No Mouse support; Use Commands or Arrow Keys
BOOT MANAGER DEVICE: DKB0
DEFAULT BOOT COMMAND: BOOT DKB100 0x00 0x00000001
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.
V DKB100 (HD) = FS0 UEFI: E9_2_4 VMS: X86SYS1 18432 MB SATA Disk
B DKB0 (DVD) = FS1 UEFI: E9_2_4 VMS: None 1295 MB SATA DVD
BOOTMGR> BOOT DKB100
Booting...
%VMS_BOOTMGR-I-SECBOOT, SYSBOOT signature validated.
%%%%%%%%%%% 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
SYSBOOT> CONTINUE
VMS Software, Inc. OpenVMS (TM) x86_64 Operating System, E9.2-4
Copyright 2026 VMS Software, Inc.
MDS Mitigation active, variant verw(MD_CLEAR)
%DECnet-I-LOADED, network base image loaded, version = 05.92.09
%SMP-I-CPUTRN, CPU #3 has joined the active set.
%SMP-I-CPUTRN, CPU #5 has joined the active set.
%SMP-I-CPUTRN, CPU #1 has joined the active set.
%SMP-I-CPUTRN, CPU #2 has joined the active set.
%SMP-I-CPUTRN, CPU #4 has joined the active set.
%STDRV-I-STARTUP, OpenVMS startup begun at 24-AUG-2026 14:06:45.21
%EIA0, Link up: 10 gbit, 00-50-56-AC-3D-77
%RUN-S-PROC_ID, identification of created process is 00000404
%RUN-S-PROC_ID, identification of created process is 00000405
%%%%%%%%%%% OPCOM 24-AUG-2026 14:06:51.60 %%%%%%%%%%%
Operator _AG4002$OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 24-AUG-2026 14:06:51.60 %%%%%%%%%%%
Operator status for operator _AG4002$OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%%%%%%%%%%% OPCOM 24-AUG-2026 14:06:51.61 %%%%%%%%%%%
Logfile has been initialized by operator _AG4002$OPA0:
Logfile is AG4002::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;7
%%%%%%%%%%% OPCOM 24-AUG-2026 14:06:51.61 %%%%%%%%%%%
Operator status for operator AG4002::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;7
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 0000040B
%%%%%%%%%%% OPCOM 24-AUG-2026 14:06:51.67 %%%%%%%%%%%
Message from user SYSTEM on AG4002
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 24-AUG-2026 14:06:51.68 %%%%%%%%%%%
Message from user SYSTEM on AG4002
-RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 24-AUG-2026 14:06:51.75 %%%%%%%%%%%
Message from user SYSTEM on AG4002
%SECSRV-I-SERVERSTARTINGU, security server starting up
%%%%%%%%%%% OPCOM 24-AUG-2026 14:06:51.76 %%%%%%%%%%%
Message from user SYSTEM on AG4002
%SECSRV-I-CIACRECLUDB, security server created cluster intrusion database
%%%%%%%%%%% OPCOM 24-AUG-2026 14:06:51.76 %%%%%%%%%%%
Message from user SYSTEM on AG4002
%SECSRV-I-CIASTARTINGUP, breakin detection and evasion processing now starting u
p
%%%%%%%%%%% OPCOM 24-AUG-2026 14:06:51.77 %%%%%%%%%%%
Message from user SYSTEM on AG4002
%ACME-I-SERVERSTART, ACME_SERVER starting
%%%%%%%%%%% OPCOM 24-AUG-2026 14:06:54.76 %%%%%%%%%%%
Message from user SYSTEM on AG4002
%SECSRV-I-PROXYSTARTINGUP, proxy processing now starting up
%%%%%%%%%%% OPCOM 24-AUG-2026 14:06:54.77 %%%%%%%%%%%
Message from user SYSTEM on AG4002
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 24-AUG-2026 14:06:59.86 %%%%%%%%%%%
Message from user SYSTEM on AG4002
TDF-I-SETTDF TDF set new timezone differential
Copyright 2026 VMS Software, Inc.
%NET-I-LOADED, executive image LES$LES_V30.EXE loaded
%NET-I-LOADED, executive image NET$ALIAS.EXE loaded
%NET-I-LOADED, executive image NET$SESSION_CONTROL.EXE loaded
%NET$STARTUP-I-STARTPROCESS, starting process DNS
%NET-I-LOADED, executive image SYS$NAME_SERVICES.EXE loaded
%RUN-S-PROC_ID, identification of created process is 00000415
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script SYS$SYSROOT:[SYSMGR]NET$NODE_
STARTUP.NCL;
%NET-I-LOADED, executive image NET$CSMACD.EXE loaded
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script SYS$SYSROOT:[SYSMGR]NET$CSMAC
D_STARTUP.NCL;
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script SYS$SYSROOT:[SYSMGR]NET$SESSI
ON_STARTUP.NCL;
%LES-S-PROC_ID, identification of created process is 00000416
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:06.83 %%%%%%%%%%%
Message from user SYSTEM on AG4002
%LES-S-ACPSTARTED, LES$ACP_V30 started running LES$ACP V3.0
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:06.87 %%%%%%%%%%%
Message from user SYSTEM on AG4002
%LES-I-LOADING, loading NET$ component NETMANPPI from SYS$COMMON:[SYS$LDR]LES$NE
TMAN.EXE;1
%LES-I-LOADING, loading NET$ component NETMANPPI from SYS$COMMON:[SYS$LDR]LES$NE
TMAN.EXE;1
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script SYS$SYSROOT:[SYSMGR]NET$ROUTI
NG_STARTUP.NCL;
%NET-I-LOADED, executive image NET$TRANSPORT_NSP.EXE loaded
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script SYS$SYSROOT:[SYSMGR]NET$NSP_T
RANSPORT_STARTUP.NCL;
%NET-I-LOADED, executive image NET$TPCONS.EXE loaded
%NET-I-LOADED, executive image NET$TRANSPORT_OSI.EXE loaded
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script SYS$SYSROOT:[SYSMGR]NET$OSI_T
RANSPORT_STARTUP.NCL;
%SYSMAN-I-OUTPUT, command execution on node AG4002
%SYSMAN-I-IOADDRESS, the DPT is located at address 80651000
%NET-I-LOADED, executive image NET$OSVCM.EXE loaded
%SYSMAN-I-OUTPUT, command execution on node AG4002
%SYSMAN-I-IOADDRESS, the DPT is located at address 80653E00
%NET$STARTUP-I-STARTPROCESS, starting process ACP
%RUN-S-PROC_ID, identification of created process is 00000417
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:09.95 %%%%%%%%%%%
Message from user SYSTEM on AG4002
%NET$ACP-I-STARTUP, DECnet-Plus for OpenVMS ACP starting execution
%RUN-S-PROC_ID, identification of created process is 00000418
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script SYS$SYSROOT:[SYSMGR]NET$SEARC
HPATH_STARTUP.NCL;
%NET$STARTUP-I-STARTPROCESS, starting process EVD
%RUN-S-PROC_ID, identification of created process is 00000419
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script SYS$SYSROOT:[SYSMGR]NET$EVENT
_STARTUP.NCL;
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:10.88 %%%%%%%%%%%
Message from user SYSTEM on AG4002
Event: Change Filter from: Node LOCAL:.AG4002 Event Dispatcher SINK local_sink,
at: 2026-08-24-14:07:10.878+02:00Iinf
Old Specific Filter=
{
[
EventCode = (Node LOCAL:.AG4002 , All) ,
Filter Action = Ignore
] ,
[
EventCode = (Node LOCAL:.AG4002 Event Dispatcher, All) ,
Filter Action = Ignore
] ,
[
EventCode = (Node LOCAL:.AG4002 Event Dispatcher SINK local_sink, All)
,
Filter Action = Pass
]
},
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:10.90 %%%%%%%%%%%
Message from user SYSTEM on AG4002
Old Global Filter=
{
[
EventCode = ((Node), All) ,
Filter Action = Ignore
] ,
[
EventCode = ((Node, Event Dispatcher), All) ,
Filter Action = Block
] ,
[
EventCode = ((Node, Event Dispatcher, SINK), All) ,
Filter Action = Block
] ,
[
EventCode = ((Node, Event Dispatcher, Outbound Stream), All) ,
Filter Action = Block
] ,
[
EventCode = ((Node, Event Dispatcher, SINK, Inbound Stream), All) ,
Filter Action = Block
]
},
Old Catch All=Pass,
New Specific Filter=
{
[
EventCode = (Node LOCAL:.AG4002 , All) ,
Filter Action = Ignore
] ,
[
EventCode = (Node LOCAL:.AG4002 Event Dispatcher, All) ,
Filter Action = Ignore
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:10.91 %%%%%%%%%%%
Message from user SYSTEM on AG4002
] ,
[
EventCode = (Node LOCAL:.AG4002 Event Dispatcher SINK local_sink, All)
,
Filter Action = Pass
]
},
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:10.92 %%%%%%%%%%%
Message from user SYSTEM on AG4002
New Global Filter=
{
[
EventCode = ((Node), All) ,
Filter Action = Ignore
] ,
[
EventCode = ((Node, Event Dispatcher), All) ,
Filter Action = Block
] ,
[
EventCode = ((Node, Event Dispatcher, SINK), All) ,
Filter Action = Block
] ,
[
EventCode = ((Node, Event Dispatcher, Outbound Stream), All) ,
Filter Action = Block
] ,
[
EventCode = ((Node, Event Dispatcher, SINK, Inbound Stream), All) ,
Filter Action = Block
]
},
New catch All Filter=Pass
eventUid 19677A28-9FC5-11F1-8331-AA0004006906
entityUid 1966B6DD-9FC5-11F1-832E-AA0004006906
streamUid 1966B6DD-9FC5-11F1-832E-AA0004006906
%NET$STARTUP-I-STARTPROCESS, starting process DTSS
%RUN-S-PROC_ID, identification of created process is 0000041A
%NET$STARTUP-I-EXECUTESCRIPT, executing NCL script SYS$SYSROOT:[SYSMGR]NET$APPLI
CATION_STARTUP.NCL;
%NET-I-LOADED, executive image NET$LOOP_APPLICATION.EXE loaded
%NET$STARTUP-I-OPERSTATUS, DECnet-Plus for OpenVMS operational status is RUNNING
-ALL
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:12.31 %%%%%%%%%%%
Message from user SYSTEM on AG4002
Warning: DECdtm log file not found (SYS$JOURNAL:SYSTEM$AG4002.LM$JOURNAL)
%RMS-E-FNF, file not found
TP server process waiting
%STARTUP-I-AUDITCONTINUE, audit server initialization complete
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:12.41 %%%%%%%%%%%
Message from user AUDIT$SERVER on AG4002
Security alarm (SECURITY) and security audit (SECURITY) on AG4002, system id: 16
41
Auditable event: Audit server starting up
Event time: 24-AUG-2026 14:07:12.39
PID: 00000403
Username: SYSTEM
The OpenVMS system is now executing the site-specific startup commands.
%DCL-I-SUPERSEDE, previous value of SSL3$ROOT has been superseded
%TCPIP-I-INFO, TCP/IP Services startup beginning at 24-AUG-2026 14:07:13.45
%TCPIP-I-NORMAL, timezone information verified
%RUN-S-PROC_ID, identification of created process is 00000422
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:15.47 %%%%%%%%%%%
Message from user INTERnet on AG4002
INTERnet Loaded
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:15.49 %%%%%%%%%%%
Message from user INTERnet on AG4002
Subsystem "inet" configured by process 00010022
Status: success
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:15.49 %%%%%%%%%%%
Message from user INTERnet on AG4002
Subsystem "net" configured by process 00010022
Status: success
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:15.50 %%%%%%%%%%%
Message from user INTERnet on AG4002
Subsystem "socket" configured by process 00010022
Status: success
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:15.50 %%%%%%%%%%%
Message from user INTERnet on AG4002
Subsystem "iptunnel" configured by process 00010022
Status: success
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:15.51 %%%%%%%%%%%
Message from user INTERnet on AG4002
Subsystem "ipv6" configured by process 00010022
Status: success
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:15.51 %%%%%%%%%%%
Message from user INTERnet on AG4002
Subsystem "snmpinfo" configured by process 00010022
Status: success
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:15.52 %%%%%%%%%%%
Message from user INTERnet on AG4002
Subsystem "kvci" configured by process 00010022
Status: success
%TCPIP-I-SETLOCAL, setting domain and/or local host
%TCPIP-I-STARTCOMM, starting communication
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:15.97 %%%%%%%%%%%
Message from user INTERnet on AG4002
INTERnet Started
%TCPIP-I-SETPROTP, setting protocol parameters
%TCPIP-I-DEFINTE, defining interfaces
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:15.98 %%%%%%%%%%%
Message from user INTERnet on AG4002
INTERnet ACP Created INTERnet interface: IE0
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:15.99 %%%%%%%%%%%
Message from user INTERnet on AG4002
%TCPIP-I-FSIPADDRUP, IE0 10.10.102.242 primary active on node AG4002, interface
IE0
%TCPIP-I-STARTNAME, starting name service
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:16.09 %%%%%%%%%%%
Message from user INTERnet on AG4002
Subsystem "proxy" configured by process 00010003
Status: success
%TCPIP-S-STARTDONE, TCP/IP Kernel startup completed
%TCPIP-I-PROXYLOADED, loaded 0 NFS proxy records
%TCPIP-I-LOADSERV, loading TCPIP server proxy information
%TCPIP-I-SERVLOADED, auxiliary server loaded with 0 proxy records
-TCPIP-I-SERVSKIP, skipped 0 communication proxy records
-TCPIP-I-SERVTOTAL, total of 0 proxy records read
%TCPIP-S-STARTDONE, TCPIP$PROXY startup completed
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:16.55 %%%%%%%%%%%
Message from user INTERnet on AG4002
INTERnet ACP Activate FTP Server
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:16.56 %%%%%%%%%%%
Message from user INTERnet on AG4002
INTERnet ACP NOLISTEN Process creation success: Service - FTP
%TCPIP-S-STARTDONE, TCPIP$FTP startup completed
%TCPIP-S-STARTDONE, TCPIP$FTP_CLIENT startup completed
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:16.68 %%%%%%%%%%%
Message from user INTERnet on AG4002
INTERnet ACP Activate TELNET Server
%TCPIP-S-STARTDONE, TCPIP$TELNET startup completed
%TCPIP-S-STARTDONE, TCP/IP Services startup completed at 24-AUG-2026 14:07:16.74
%DECW$DEVICE-I-NODEVICE, no graphics devices found.
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
%RUN-S-PROC_ID, identification of created process is 00000425
%%%%%%%%%%% OPCOM 24-AUG-2026 14:07:17.02 %%%%%%%%%%%
Message from user SYSTEM on AG4002
%SMHANDLER-S-STARTUP, server management event handler startup
SYSTEM job terminated at 24-AUG-2026 14:07:19.03
Accounting information:
Buffered I/O count: 7128 Peak working set size: 13024
Direct I/O count: 13580 Peak virtual size: 258032
Page faults: 13528 Mounted volumes: 0
Charged CPU time: 0 00:00:07.74 Elapsed time: 0 00:00:33.86
Welcome to OpenVMS (TM) x86_64 Operating System, Version E9.2-4