This page shows the console log when installing VMS 5.5 on a MicroVAX3900 in SIMH.
Drive DUA0 is a simulated RA80 drive.
Drive DUA3 is a simulated CDROM drive, with Disc 1 of the November 1992 Consolidated Software Distribution installed.
This section shows the initial boot of the CD and running standalone backup.
Connected to the MicroVAX 3900 simulator CON-TEL device KA655-B V5.3, VMB 2.7 Performing normal system tests. 40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25.. 24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09.. 08..07..06..05..04..03.. Tests completed. >>>SHOW DEV ⤶ UQSSP Disk Controller 0 (772150) -DUA0 (RA80) -DUA3 (RRD40) Ethernet Adapter 0 (774440) -XQA0 (08-00-2B-AA-BB-CC) >>>BOOT/R5:E0000000 DUA3: ⤶ (BOOT/R5:E0000000 DUA3 2.. -DUA3 1..0.. VAX/VMS Version V5.5 Major version id = 1 Minor version id = 0 PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 16-AUG-2016 08:54 ⤶ Configuring devices . . . Now configuring HSC, RF, and MSCP-served devices . . . Please check the names of the devices which have been configured, to make sure that ALL remote devices which you intend to use have been configured. If any device does not show up, please take action now to make it available. Available device DUA0: device type RA80 Available device DUA3: device type RRD40 Available device DDA0: device type TU58 Available device DDA1: device type TU58 Enter "YES" when all needed devices are available: YES ⤶ %BACKUP-I-IDENT, Stand-alone BACKUP V5.5; the date is 16-AUG-2016 08:56:26.32 $ BACKUP DUA3:VMS055.B/SAVE_SET DUA0: ⤶ %BACKUP-I-PROCDONE, operation completed. Processing finished at 16-AUG-2016 08:57:51.50 If you do not want to perform another standalone BACKUP operation, use the console to halt the system. If you do want to perform another standalone BACKUP operation, ensure the standalone application volume is online and ready. Enter "YES" to continue: [VAX was HALT'd by pressing CTRL-BREAK in the console (PuTTY)]
?06 HLT INST
PC = 83BC2ADF
>>>BOOT DUA0: ⤶
(BOOT/R5:0 DUA0
2..
-DUA0
1..0..
VAX/VMS Version BI55-52I Major version id = 1 Minor version id = 0
VAX/VMS V5.5 Installation Procedure
Model: VAXserver 3900 Series
System device: RA80 - _DUA0:
Free Blocks: 190830
CPU type: 10-01
* Please enter the date and time (DD-MMM-YYYY HH:MM) 16-AUG-2016 08:58 ⤶
%STDRV-I-STARTUP, VMS startup begun at 16-AUG-2016 08:58:00.32
%SET-I-NEWAUDSRV, identification of new audit server process is 00000028
%LICENSE-F-EMTLDB, license database contains no license records
%%%%%%%%%%% OPCOM 16-AUG-2016 08:58:09.55 %%%%%%%%%%%
Operator _OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 16-AUG-2016 08:58:09.57 %%%%%%%%%%%
Operator status for operator _OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%%%%%%%%%%% OPCOM 16-AUG-2016 08:58:09.82 %%%%%%%%%%%
Logfile has been initialized by operator _OPA0:
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
%%%%%%%%%%% OPCOM 16-AUG-2016 08:58:09.83 %%%%%%%%%%%
Operator status for operator SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%%%%%%%%%%% OPCOM 16-AUG-2016 08:58:10.50 %%%%%%%%%%%
Message from user SYSTEM
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
Startup processing continuing...
%%%%%%%%%%% OPCOM 16-AUG-2016 08:58:14.84 %%%%%%%%%%%
Message from user AUDIT$SERVER
Security alarm (SECURITY) and security audit (SECURITY), system id: 65534
Auditable event: Audit server shutting down
Event time: 16-AUG-2016 08:58:14.81
PID: 00000023
%STDRV-I-STARTUP, VMS startup begun at 16-AUG-2016 08:58:21.35
If this system disk is to be used in a cluster with multiple system
disks, then each system disk must have a unique volume label. Any
nodes having system disks with duplicate volume labels will fail to
boot into the cluster.
You may indicate a volume label of 1 to 12 characters in length. If you
wish to use the default name of VAXVMSV055 just press RETURN in response
to the next question.
* Enter the volume label for this system disk [VAXVMSV055]: ⤶
* Enter name of drive holding the VMS distribution media: DUA3: ⤶
* Is the VMS media ready to be mounted? [N] Y ⤶
%MOUNT-I-MOUNTED, CDBIN10NOV21 mounted on _DUA3:
Select optional software you wish to have installed. You can choose to
install one or more of the following VMS and/or DECwindows components:
o VMS library - 32000 blocks
o VMS optional - 16500 blocks
o DECwindows device support - 21400 blocks
o DECwindows applications - 12000 blocks
o DECwindows programming support - 26500 blocks
o DECwindows example files - 3500 blocks
Space remaining: 190629 blocks
* Do you want to install the VMS library files? (Y/N) Y ⤶
Space remaining: 158629 blocks
* Do you want to install the VMS optional files? (Y/N) Y ⤶
Space remaining: 142129 blocks
You can provide DECwindows support now, or you can use the
DECW$TAILOR utility to provide or remove DECwindows support
after the installation.
NOTE: Some media, TK50s in particular, can be very slow when
tailoring on files. You might want to provide DECwindows
options now and tailor off unwanted files later.
* Do you want to provide optional DECwindows support? (Y/N) Y ⤶
You can install either the complete DECwindows kit or selected portions
of it. A complete installation requires 63400 blocks. If you
want to perform a partial installation, you can choose to install one
or more of the following DECwindows components:
o DECwindows device support - 21400 blocks
o DECwindows applications - 12000 blocks
o DECwindows programming support - 26500 blocks
o DECwindows example files - 3500 blocks
* Do you want to install complete DECwindows support? (Y/N) Y ⤶
Space remaining: 78729 blocks
The following options will be provided:
VMS library
VMS optional
DECwindows device support with:
o 75 dots per inch video fonts
o 100 dots per inch video fonts
o applications
DECwindows programming support for:
o Ada
o BASIC
o BLISS
o C (MIT binding)
o C (VAX binding)
o FORTRAN
o MACRO
o Pascal
o PL/1
DECwindows example files
Space remaining: 78729 blocks
* Is this correct? (Y/N) Y ⤶
Restoring VMS library save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring VMS optional save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring DECwindows applications save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring DECwindows device support save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring DECwindows 75DPI fonts save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring DECwindows 100DPI fonts save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring DECwindows programming support save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
Restoring DECwindows examples save set ...
%BACKUP-I-STARTVERIFY, starting verification pass
You may now remove the distribution kit from DUA3:.
Creating [VMS$COMMON] directory tree ...
In a cluster, you can run multiple systems sharing all files except
PAGEFILE.SYS, SWAPFILE.SYS, SYSDUMP.DMP and VAXVMSSYS.PAR.
* Will this node be a cluster member? (Y/N) N ⤶
* Do you want DECwindows as the default windowing system? (Y/N) Y ⤶
Now we will ask you for new passwords for the following accounts:
SYSTEM, SYSTEST, FIELD
Passwords must be a minimum of 8 characters in length. All passwords
will be checked and verified. Any passwords that can be guessed easily
will not be accepted.
* Enter password for SYSTEM: [Type your selected password] ⤶
* Re-enter for verification: [Re-type your selected password] ⤶
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for SYSTEM verified
* Enter password for SYSTEST: [Type your selected password] ⤶
* Re-enter for verification: [Re-type your selected password] ⤶
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for SYSTEST verified
The SYSTEST_CLIG account will be disabled. You must re-enable
it before running UETP but do not assign a password.
%UAF-I-MDFYMSG, user record(s) updated
* Enter password for FIELD: [Type your selected password] ⤶
* Re-enter for verification: [Re-type your selected password] ⤶
%UAF-I-MDFYMSG, user record(s) updated
%VMS-I-PWD_OKAY, account password for FIELD verified
Creating RIGHTS database file, SYS$SYSTEM:RIGHTSLIST.DAT
Ignore any "-SYSTEM-F-DUPIDENT, duplicate identifier" errors.
%UAF-I-RDBCREMSG, rights data base created
%UAF-I-RDBADDMSGU, identifier DEFAULT value: [000200,000200] added to rights data base
%UAF-I-RDBADDMSGU, identifier FIELD value: [000001,000010] added to rights data base
%UAF-I-RDBADDMSGU, identifier SYSTEM value: [000001,000004] added to rights data base
%UAF-I-RDBADDMSGU, identifier SYSTEST value: [000001,000007] added to rights data base
%UAF-E-RDBADDERRU, unable to add SYSTEST_CLIG value: [000001,000007] to rights data base
-SYSTEM-F-DUPIDENT, duplicate identifier
%UAF-I-NOMODS, no modifications made to system authorization file
%UAF-I-RDBDONEMSG, rights data base modified
After the installation finishes, you may want to do one or more of the
following tasks:
o DECOMPRESS THE SYSTEM LIBRARIES - For space considerations, many of
the system libraries are shipped in a data-compressed format. If you
have enough disk space, you may decompress them for faster access. To
data expand the libraries, type:
$ @SYS$UPDATE:LIBDECOMP.COM
If you choose not to decompress these libraries you will experience
slower response with the HELP and LINK commands.
o BUILD A STANDALONE BACKUP KIT - You can build a standalone backup kit
using the procedure described in your VMS installation and operations
guide which is supplied for your VAX computer.
o TAILOR THE SYSTEM DISK - You may want to review the files provided or
not provided during this installation. If you find there are files
you want to remove from the system disk (TAILOR OFF) or files you want
to add (TAILOR ON), use the following utilities to perform the
desired tailoring.
VMS tailoring: $ RUN SYS$UPDATE:VMSTAILOR
DECwindows tailoring: $ RUN SYS$UPDATE:DECW$TAILOR
=================================================================
Continuing with VAX/VMS V5.5 Installation Procedure.
Configuring all devices on the system ...
%STDRV-I-STARTUP, VMS startup begun at 16-AUG-2016 09:02:54.69
You must now install the Mandatory Update, which may be found
on a separate distribution volume.
VAX/VMS Software Product Installation Procedure BI55-52I
It is 16-AUG-2016 at 09:03.
Enter a question mark (?) at any time for help.
* Where will the distribution volumes be mounted: DUA3: ⤶
Please mount the first volume of the set on DUA3:.
* Are you ready? Y ⤶
%MOUNT-I-MOUNTED, CDBIN10NOV21 mounted on _DUA3:
The following products will be processed:
VMSMUP V5.5
Beginning installation of VMSMUP V5.5 at 09:04
%VMSINSTAL-I-RESTORE, Restoring product save set A ...
* Do you want to purge files replaced by this installation [YES]? ⤶
%VMSINSTAL-I-RESTORE, Restoring product save set B ...
1) AUTOGEN (new file)
2) CONFIGURE (new image)
3) DECINTACT$READY_TO_COMMIT (new image)
4) DECW$DEVICE (new file)
5) DECW$DEVICE_GF (new file)
6) DECW$PRIVATE_SERVER_SETUP (new file)
7) DECW$SERVER_DDX_GF (new image)
8) ERFNVAX (new image)
9) ESS$LASTDRIVER (new image)
10) F11BXQP (new image)
11) GFBDRIVER (new image)
12) HELPLIB (miscellaneous fix)
13) IKDRIVER (new image)
14) IPCACP (new image)
15) JBC$UPGRADE (new file)
16) JOBCTL (patch image)
%PATCH-I-NOLCL, image does not contain local symbols
%PATCH-I-NOGBL, some or all global symbols not accessible
%PATCH-I-WRTFIL, updating image file DUA0:[SYS0.SYSUPD.VMSMUP055]JOBCTL.EXE;1
17) KITTING (new file)
18) LOCKING (new image)
19) LOGINOUT (new image)
20) LTDRIVER (new image)
21) MKDRIVER (new image)
22) MOUNTSHR (new image)
23) PADRIVER01U3054 (new file)
24) PROCESS_MANAGEMENT (new image)
25) QMAN$QUEUE_MANAGER (patch image)
%PATCH-I-NOGBL, some or all global symbols not accessible
%PATCH-I-WRTFIL, updating image file DUA0:[SYS0.SYSUPD.VMSMUP055]QMAN$QUEUE_MANAGER.EXE;1
26) SHDRIVER (new image)
27) SODRIVER (new image)
28) SYS$CLUSTER (new image)
29) SYS$TRANSACTION_SERVICES (new image)
30) SYSBOOT (new image)
31) SYSLICENSE (patch image)
%PATCH-I-NOLCL, image does not contain local symbols
%PATCH-I-WRTFIL, updating image file DUA0:[SYS0.SYSUPD.VMSMUP055]SYSLICENSE.EXE;1
32) SYSLOA1202 (new image)
33) SYSLOA1302 (new image)
34) SYSLOA440 (new image)
35) SYSLOA46 (new image)
36) SYSLOA690 (new image)
37) SYSLOA69D (new image)
38) TMSCP (new image)
39) UAFHELP (new file)
40) VMS$BASEENVIRON-050_VMS (new file)
41) VMS$UPGRADE_A55_V55 (new file)
42) XQDRIVER (new image)
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...
%VMSMUP-I-NOMOVEMOVE, setting NOMOVE on some replaced files
Installation of VMSMUP V5.5 completed at 09:05
VMSINSTAL procedure done at 09:05
You may safely ignore the following NCP error message(s).
%NCP-W-UNRCMP, Unrecognized component , Object
If you have Product Authorization Keys (PAKs) to register, you may
register them now.
* Do you want to register any Product Authorization Keys? (Y/N): Y ⤶
VMS License Management Utility Options:
1. REGISTER a Product Authorization Key
2. AMEND an existing Product Authorization Key
3. CANCEL an existing Product Authorization Key
4. LIST the Product Authorization Keys
5. MODIFY an existing Product Authorization Key
6. DISABLE an existing Product Authorization Key
7. DELETE an existing Product Authorization Key
8. COPY an existing Product Authorization Key
9. MOVE an existing Product Authorization Key
10. ENABLE an existing Product Authorization Key
11. SHOW the licenses loaded on this node
12. SHOW the unit requirements for this node
99. EXIT this procedure
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to exit this procedure.
Enter one of the above choices [1] ⤶
Do you have your Product Authorization Key? [YES] ⤶
Use the REGISTER option to add a new license to a license
database. A Product Authorization Key (PAK) provides the product
name and information you need to register the license. You must
enter all the information provided by your PAK exactly as it
appears.
PAK ID:
Issuer [DEC] ⤶
Authorization Number [][Enter details from license PAK] ⤶
PRODUCT ID:
Product Name []VAX-VMS ⤶
Producer [DEC] ⤶
NUMBER OF UNITS:
Number of Units [][Enter details from license PAK] ⤶
KEY LEVEL:
Version [] ⤶
Product Release Date [] ⤶
KEY TERMINATION DATE:
Key Termination Date [][Enter details from license PAK] ⤶
RATING:
Availability Table Code [] ⤶
Activity Table Code [][Enter details from license PAK] ⤶
MISCELLANEOUS:
Key Options [] ⤶
Product Token [] ⤶
Hardware-Id [] ⤶
Checksum [][Enter details from license PAK] ⤶
License Database File: SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB
Issuer: DEC
Authorization: [as entered above]
Producer: DEC
Product Name: VAX-VMS
Units: [as entered above]
Release Date:
Version:
Termination Date:
Availability:
Activity: CONSTANT=[as entered above]
Options:
Token:
Hardware ID:
Checksum: [as entered above]
Is this information correct? [YES] ⤶
Registering VAX-VMS license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB...
Do you want to LOAD this license on this system? [YES] ⤶
%LICENSE-I-LOADED, DEC VAX-VMS was successfully loaded with 0 units
VMS License Management Utility Options:
1. REGISTER a Product Authorization Key
2. AMEND an existing Product Authorization Key
3. CANCEL an existing Product Authorization Key
4. LIST the Product Authorization Keys
5. MODIFY an existing Product Authorization Key
6. DISABLE an existing Product Authorization Key
7. DELETE an existing Product Authorization Key
8. COPY an existing Product Authorization Key
9. MOVE an existing Product Authorization Key
10. ENABLE an existing Product Authorization Key
11. SHOW the licenses loaded on this node
12. SHOW the unit requirements for this node
99. EXIT this procedure
Type '?' at any prompt for a description of the information
requested. Press Ctrl/Z at any prompt to exit this procedure.
Enter one of the above choices [1]99 ⤶
********************************************************************************
Setting the NOMOVE attribute on critical system files.
This will take a few minutes...
********************************************************************************
After completion of this installation, you should set the
NOMOVE attribute on the critical system files of all
alternative system disks by executing the command:
$ @SYS$SYSTEM:SETFILENOMOVE
********************************************************************************
After the system has rebooted you should register any additional
Product Authorization Keys (PAKs) you have, or receive in the
future, by executing the following procedure:
$ @SYS$UPDATE:VMSLICENSE
See the VMS License Management Utility Manual for any additional
information you may need.
********************************************************************************
Running AUTOGEN to compute the new SYSGEN parameters ...
%AUTOGEN-I-BEGIN, GETDATA phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GETDATA phase has successfully completed.
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GENPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, GENFILES phase is beginning.
%SYSGEN-I-EXTENDED, DUA0:[SYS0.SYSEXE]SWAPFILE.SYS;1 extended
******************
%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.
%AUTOGEN-I-END, SETPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, REBOOT phase is beginning.
The system is shutting down to allow the system to boot with the
generated site-specific parameters and installed images.
The system will automatically reboot after the shutdown and the
installation will be complete.
SHUTDOWN -- Perform an Orderly System Shutdown
%SHUTDOWN-I-BOOTCHECK, Performing reboot consistency check...
%SHUTDOWN-I-CHECKOK, Basic reboot consistency check completed
%SHUTDOWN-I-OPERATOR, This terminal is now an operator's console.
%OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running
%SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled.
%SET-I-INTSET, login interactive limit = 0, current interactive value = 0
%SHUTDOWN-I-STOPQUEUES, The queues on this node will now be stopped.
%JBC-E-JOBQUEDIS, system job queue manager is not running
SHUTDOWN message from user SYSTEM at _OPA0: 09:15:36
The system will shut down in 0 minutes; back up SOON. Please log off.
Reboot system with AUTOGENerated parameters
1 terminal has been notified.
%SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked.
%SHUTDOWN-I-STOPUSER, All user processes will now be stopped.
%SHUTDOWN-I-REMOVE, All installed images will now be removed.
%SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted.
%OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running
%OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running
KA655-B V5.3, VMB 2.7 Performing normal system tests. 40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25.. 24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09.. 08..07..06..05..04..03.. Tests completed. >>>BOOT DUA0 ⤶ (BOOT/R5:0 DUA0 2.. -DUA0 1..0.. VAX/VMS Version V5.5 Major version id = 1 Minor version id = 0 *************************************************************** VAX/VMS V5.5 You have SUCCESSFULLY installed the VMS operating system. The system is now executing the STARTUP procedure. Please wait for the completion of STARTUP before logging in to the system. *************************************************************** %STDRV-I-STARTUP, VMS startup begun at 16-AUG-2016 09:18:18.56 %SET-I-NEWAUDSRV, identification of new audit server process is 0000020A %%%%%%%%%%% OPCOM 16-AUG-2016 09:18:34.03 %%%%%%%%%%% Operator _OPA0: has been enabled, username SYSTEM %%%%%%%%%%% OPCOM 16-AUG-2016 09:18:34.05 %%%%%%%%%%% Operator status for operator _OPA0: CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY, LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12 %%%%%%%%%%% OPCOM 16-AUG-2016 09:18:34.27 %%%%%%%%%%% Logfile has been initialized by operator _OPA0: Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1 %%%%%%%%%%% OPCOM 16-AUG-2016 09:18:34.28 %%%%%%%%%%% Operator status for operator SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1 CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY, LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12 %%%%%%%%%%% OPCOM 16-AUG-2016 09:18:35.21 %%%%%%%%%%% Message from user SYSTEM Warning: DECdtm log file not found (SYS$JOURNAL:SYSTEM$ .LM$JOURNAL) %RMS-E-FNF, file not found TP server process waiting %SET-I-INTSET, login interactive limit = 64, current interactive value = 0 16-AUG-2016 09:18:35 %DECW-W-NODEVICE, No graphics device found on this system -DECW-I-NODECW, DECwindows graphics drivers will not be loaded SYSTEM job terminated at 16-AUG-2016 09:18:40.34 Accounting information: Buffered I/O count: 1221 Peak working set size: 826 Direct I/O count: 536 Peak page file size: 11389 Page faults: 3884 Mounted volumes: 0 Charged CPU time: 0 00:00:12.23 Elapsed time: 0 00:00:26.58 [Press ENTER in the console (PuTTY) to display the login prompt] Welcome to VAX/VMS V5.5 Username: SYSTEM ⤶ Password: [Type your password] ⤶ Welcome to VAX/VMS version V5.5 $ DIR ⤶ Directory SYS$SYSROOT:[SYSMGR] ACCOUNTNG.DAT;1 OPERATOR.LOG;1 VMSIMAGES.DAT;1 Total of 3 files. Directory SYS$COMMON:[SYSMGR] ALFMAINT.COM;1 AUDIT_SERVER.DAT;1 CLUSTER_CONFIG.COM;1 DBLSTRTUP.COM;1 DECW$CHECK_PARAMS.COM;1 DECW$DEVICE.COM;2 DECW$DEVICE_GE.COM;1 DECW$DEVICE_GF.COM;1 DECW$DEVICE_GG.COM;1 DECW$LOGICALS.COM;1 DECW$PRIVATE_SERVER_SETUP.TEMPLATE;1 DECW$RGB.COM;1 DECW$STARTAPPS.COM;1 DECW$STARTLIBS.COM;1 DECW$STARTSERVER.COM;1 DECW$STARTSM.COM;1 DECW$STARTUP.COM;1 DECW$STARTXTERMINAL.COM;1 DECW$SYLOGIN.COM;1 DECW$SYLOGIN.TEMPLATE;1 DNS$CHANGE_DEF_FILE.COM;1 DNS$CLIENT_STARTUP.COM;1 DNS$CLIENT_STOP.COM;1 EDTINI.TEMPLATE;1 LAT$SYSTARTUP.COM;1 LAT$SYSTARTUP.TEMPLATE;1 LIB$DT_STARTUP.COM;1 LOADNET.COM;1 LOGIN.COM;1 LOGIN.TEMPLATE;1 LPA11STRT.COM;1 LTLOAD.COM;1 MAKEROOT.COM;1 NETCONFIG.COM;1 RTTLOAD.COM;1 SECURITY_AUDIT.AUDIT$JOURNAL;1 SMISERVER.COM;1 STARTNET.COM;1 SYCONFIG.COM;1 SYCONFIG.TEMPLATE;1 SYLOGICALS.COM;1 SYLOGICALS.TEMPLATE;1 SYLOGIN.COM;1 SYLOGIN.TEMPLATE;1 SYPAGSWPFILES.COM;1 SYPAGSWPFILES.TEMPLATE;1 SYSECURITY.COM;1 SYSECURITY.TEMPLATE;1 SYSHUTDWN.COM;1 SYSHUTDWN.TEMPLATE;1 SYSTARTUP_V5.COM;1 SYSTARTUP_V5.TEMPLATE;1 TFF$STARTUP.COM;1 VMS$IMAGES_MASTER.DAT;1 VMSIMAGES.DAT;1 WELCOME.TEMPLATE;1 WELCOME.TXT;1 Total of 57 files. Grand total of 2 directories, 60 files. $ SHUTDOWN ⤶ SHUTDOWN -- Perform an Orderly System Shutdown %SHUTDOWN-I-OPERATOR, This terminal is now an operator's console. %%%%%%%%%%% OPCOM 16-AUG-2016 09:19:34.80 %%%%%%%%%%% Operator status for operator _OPA0: CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY, LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12 %SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled. %SET-I-INTSET, login interactive limit = 0, current interactive value = 1 %SHUTDOWN-I-STOPQUEUES, The queues on this node will now be stopped. %JBC-E-JOBQUEDIS, system job queue manager is not running SHUTDOWN message from user SYSTEM at _OPA0: 09:19:38 The system will shut down in 0 minutes; back up LATER. Please log off. SHUTDOWN 1 terminal has been notified. %SHUTDOWN-I-STOPUSER, All user processes will now be stopped. %SHUTDOWN-I-REMOVE, All installed images will now be removed. %SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted. %SHUTDOWN-I-STOPAUDIT, stopping the audit server %%%%%%%%%%% OPCOM 16-AUG-2016 09:19:42.50 %%%%%%%%%%% Message from user AUDIT$SERVER Security alarm (SECURITY) and security audit (SECURITY), system id: 65534 Auditable event: Audit server shutting down Event time: 16-AUG-2016 09:19:42.42 PID: 0000020E %%%%%%%%%%% OPCOM 16-AUG-2016 09:19:43.28 %%%%%%%%%%% Message from user SYSTEM _OPA0:, The system shutdown was requested by the operator. %%%%%%%%%%% OPCOM 16-AUG-2016 09:19:43.31 %%%%%%%%%%% Logfile was closed by operator _OPA0: Logfile was SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1 %%%%%%%%%%% OPCOM 16-AUG-2016 09:19:43.34 %%%%%%%%%%% Operator _OPA0: has been disabled, username SYSTEM SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM [SIMH automatically drops back to the "sim> " prompt here without any user intervention] Disconnected from the MicroVAX 3900 simulator