=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2016.06.11 10:45:45 =~=~=~=~=~=~=~=~=~=~=~= 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 (RA82) -DUA3 (RRD40) UQSSP Tape Controller 0 (774500) -MUA0 (TK50) -MUA1 (TK50) -MUA2 (TK50) -MUA3 (TK50) Ethernet Adapter 0 (774440) -XQA0 (08-00-2B-AA-BB-DD) >>>BOOT DUA3 (BOOT/R5:0 DUA3 2.. -DUA3 1..0.. OpenVMS VAX Version X5ZX-C3L Major version id = 1 Minor version id = 0 PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 11-JUN-2016 10:47 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 RA82 Available device DUA3: device type RRD40 Available device MUA0: device type TK50 Available device MUA1: device type TK50 Available device MUA2: device type TK50 Available device MUA3: device type TK50 Enter "YES" when all needed devices are available: YES %BACKUP-I-IDENT, Stand-alone BACKUP V6.1; the date is 11-JUN-2016 10:48:39.59 $ BACKUP DUA3:VMS061.B/SAVE_SET DUA0: %BACKUP-I-PROCDONE, operation completed. Processing finished at 11-JUN-2016 10:49:21.67 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: [Comment: System halted by sending a BREAK from the terminal] ?06 HLT INST PC = 83B12B47 >>>BOOT DUA0 (BOOT/R5:0 DUA0 2.. -DUA0 1..0.. OpenVMS VAX Version BI61-5ZX Major version id = 1 Minor version id = 0 OpenVMS VAX V6.1 Installation Procedure Model: VAXserver 3900 Series System device: RA82 - _DUA0: Free Blocks: 1166163 CPU type: 10-01 * Please enter the date and time (DD-MMM-YYYY HH:MM) 11-JUN-2016 10:51 On MIN or UPGRADE system startup - CLUE is not run. %%%%%%%%%%% OPCOM 11-JUN-2016 10:51:03.01 %%%%%%%%%%% Operator _OPA0: has been enabled, username SYSTEM %%%%%%%%%%% OPCOM 11-JUN-2016 10:51:03.02 %%%%%%%%%%% 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 11-JUN-2016 10:51:03.05 %%%%%%%%%%% Logfile has been initialized by operator _OPA0: Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1 %%%%%%%%%%% OPCOM 11-JUN-2016 10:51:03.05 %%%%%%%%%%% 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 %SYSTEM-I-BOOTUPGRADE, security auditing disabled %LICENSE-F-EMTLDB, license database contains no license records %SYSTEM-I-BOOTUPGRADE, security server not started %%%%%%%%%%% OPCOM 11-JUN-2016 10:51:05.26 %%%%%%%%%%% Message from user JOB_CONTROL %JBC-E-OPENERR, error opening SYS$SYSROOT:[SYSEXE]QMAN$MASTER.DAT; %%%%%%%%%%% OPCOM 11-JUN-2016 10:51:05.27 %%%%%%%%%%% Message from user JOB_CONTROL -RMS-E-FNF, file not found %%%%%%%%%%% OPCOM 11-JUN-2016 10:51:06.33 %%%%%%%%%%% 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... 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 can indicate a volume label of 1 to 12 characters in length. If you want to use the default name of OpenVMS061, press RETURN in response to the next question. * Enter the volume label for this system disk [OpenVMS061]: * Enter name of drive holding the OpenVMS distribution media: DUA3 * Is the OpenVMS media ready to be mounted? [N] Y %MOUNT-I-MOUNTED, VAXVMS061 mounted on _DUA3: Select optional software you want to install. You can install one or more of the following OpenVMS or DECwindows components: o OpenVMS library - 41500 blocks o OpenVMS optional - 18950 blocks o OpenVMS Help Message - 8900 blocks o Text versions of three OpenVMS manuals - 6300 blocks o DECwindows workstation support - 25750 blocks o DECwindows base support - 3600 blocks Space remaining on system disk: 1165983 blocks * Do you want to install the OpenVMS library files? (Y/N) Y Space remaining on system disk: 1124483 blocks * Do you want to install the OpenVMS optional files? (Y/N) Y Space remaining on system disk: 1105533 blocks The Help Message utility (MSGHLP) provides online explanations and user actions for OpenVMS messages in place of the hardcopy OpenVMS System Messages and Recovery Procedures Reference Manual, which is now separately orderable. The MSGHLP database file, MSGHLP$LIBRARY.MSGHLP$DATA, consumes approximately 8900 blocks and will be placed by default on your system disk in SYS$COMMON:[SYSHLP] unless you specify an alternate device when prompted. * Do you want to install the MSGHLP database? (Y/N) Y You can install this database on your system disk in SYS$COMMON:[SYSHLP] or on an alternate device. If you specify an alternate device, but no directory, MSGHLP$LIBRARY.MSGHLP$DATA is placed in [HELP_MESSAGE]. When prompted, take the default of the system disk or specify an alternate device using this format: device:[directory] * Where do you want to install the MSGHLP database?[SYS$COMMON:[SYSHLP]] Space remaining on system disk: 1096633 blocks You have the choice of installing text versions of one or more OpenVMS manuals. o OpenVMS Master Index - 5100 blocks o OpenVMS Glossary - 750 blocks o Overview of OpenVMS Documentation - 450 blocks You can install these manuals, by default, to your system disk in [SYSHLP.VMSDOC], or to an alternate device of your choice. In either case, all manuals must reside on the same device. If you choose an alternate device and do not specify a directory, [VMSDOC_TEXT] will be created for you. The directory structure for an alternate device should resemble the following: device:[directory] * Do you want any of these three OpenVMS manuals? (Y/N) Y * Do you want all three OpenVMS manuals? (Y/N) Y * Where do you want to install the OpenVMS manual(s)? [SYSHLP.VMSDOC] The selected OpenVMS manual(s) will reside at [SYSHLP.VMSDOC] Space remaining on system disk: 1090333 blocks You can select DECwindows support now, or you can use the DECW$TAILOR utility to provide or remove DECwindows support after the installation. 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. You can install all of the DECwindows components provided in this kit, which requires approximately 29350 blocks, or you can select specific components. o DECwindows workstation support - 20750 blocks - 75 dots per inch video fonts (included) - 100 dots per inch video fonts (optional) - 5000 blocks o DECwindows base support - 3600 blocks If you are installing this kit on a workstation or on a VAXcluster that contains workstations, then you must choose the DECwindows workstation support option. If you are installing this kit on a system that does not include workstations but does include Xterminals, then you might want to choose the DECwindows workstation support option to provide font files. If you decide not to select the DECwindows workstation support option at this time, then you will have to use the DECW$TAILOR utility to provide font files for the Xterminals. If you plan to run DECwindows software, then you must choose the DECwindows base support option. NOTE: This kit does NOT contain full DECwindows support. It includes only the DECwindows base and workstation support components. To obtain full DECwindows support, you must also install the separate DECwindows Motif for OpenVMS VAX layered product. NOTE: VMS DECwindows Motif Version 1.1 is the minimum version that can be used with OpenVMS VAX Version 6.1. * Do you want to provide optional DECwindows support? (Y/N) N The following options will be provided: OpenVMS library OpenVMS optional OpenVMS Help Message OpenVMS Master Index OpenVMS Glossary Overview of OpenVMS Documentation Space remaining on system disk: 1090333 blocks * Is this correct? (Y/N) Y Restoring OpenVMS library save set ... %BACKUP-I-STARTVERIFY, starting verification pass Restoring OpenVMS optional save set ... %BACKUP-I-STARTVERIFY, starting verification pass Restoring OpenVMS Help Message save set ... %BACKUP-I-STARTVERIFY, starting verification pass Restoring OpenVMS manuals save set ... %BACKUP-I-STARTVERIFY, starting verification pass Creating [VMS$COMMON] directory tree ... In a cluster, you can run multiple systems sharing all files except PAGEFILE.SYS, SWAPFILE.SYS, SYSDUMP.DMP, and VAXVMSSYS.PAR. * Will this node be a cluster member? (Y/N) N Now we will ask you for new passwords for the following accounts: SYSTEM, SYSTEST, FIELD Passwords must be a minimum of 8 characters in length. All passwords will be checked and verified. Any passwords that can be guessed easily will not be accepted. [Comment: The passwords are not echoed back when typed below] * Enter password for SYSTEM: * Re-enter for verification: %UAF-I-MDFYMSG, user record(s) updated %VMS-I-PWD_OKAY, account password for SYSTEM verified * Enter password for SYSTEST: * Re-enter for verification: %UAF-I-MDFYMSG, user record(s) updated %VMS-I-PWD_OKAY, account password for SYSTEST verified The SYSTEST_CLIG account will be disabled. You must re-enable it before running UETP but do not assign a password. %UAF-I-PWDLESSMIN, new password is shorter than minimum password length %UAF-I-MDFYMSG, user record(s) updated * Enter password for FIELD: * Re-enter for verification: %UAF-I-MDFYMSG, user record(s) updated %VMS-I-PWD_OKAY, account password for FIELD verified Creating RIGHTS database file, SYS$SYSTEM:RIGHTSLIST.DAT Ignore any "-SYSTEM-F-DUPIDENT, duplicate identifier" errors. %UAF-I-RDBCREMSG, rights database created %UAF-I-RDBADDMSGU, identifier DEFAULT value [000200,000200] added to rights database %UAF-I-RDBADDMSGU, identifier FIELD value [000001,000010] added to rights database %UAF-I-RDBADDMSGU, identifier SYSTEM value [000001,000004] added to rights database %UAF-I-RDBADDMSGU, identifier SYSTEST value [000001,000007] added to rights database %UAF-E-RDBADDERRU, unable to add SYSTEST_CLIG value [000001,000007] to rights database -SYSTEM-F-DUPIDENT, duplicate identifier %UAF-I-NOMODS, no modifications made to system authorization file %UAF-I-RDBDONEMSG, rights database modified Creating MODPARAMS.DAT database file, SYS$SYSTEM:MODPARAMS.DAT * Please enter the SCSNODE name: SIMH3 [Comment: I chose SCSSYSTEMID as 4 x 1024 plus 15] * Please enter the SCSSYSTEMID: 4111 After the installation finishes, you might want to do one or more of the following tasks: o DECOMPRESS THE SYSTEM LIBRARIES - To save space, many of the system libraries are shipped in a data-compressed format. If you have enough disk space, you can decompress the libraries for faster access. To data expand the libraries, type: $ @SYS$UPDATE:LIBDECOMP.COM If you do not decompress these libraries, you will experience slower response to the HELP and LINK commands. o BUILD A STANDALONE BACKUP KIT - You can build a standalone backup kit using the procedure described in the upgrade and installation supplement" supplied for your VAX computer. o TAILOR THE SYSTEM DISK - You might 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. OpenVMS tailoring: $ RUN SYS$UPDATE:VMSTAILOR DECwindows tailoring: $ RUN SYS$UPDATE:DECW$TAILOR NOTE: The tailor procedure cannot be used to TAILOR ON or TAILOR OFF files located on an alternate disk. ================================================================= Continuing with OpenVMS VAX V6.1 Installation Procedure. Configuring all devices on the system ... You can safely ignore the following NCP error messages. %NCP-W-UNRCMP, Unrecognized component , Object If you have Product Authorization Keys (PAKs) to register, you can register them now. * Do you want to register any Product Authorization Keys? (Y/N): y\y\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 return to this menu. 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. Type '?' at any prompt for a description of the information requested. Press Ctrl/Z at any prompt to return to the main menu. [Comment: All the XXXX strings below are to mask out my HOBBYIST PAK details] Issuer [DEC]: Authorization Number []:HOBBYIST-VA-KEYXXXXX-XXXXXX Product Name []:VAX-VMS Producer [DEC]: Number of Units []:0 Version []: Product Release Date []: Key Termination Date []:28-APR-2017 Availability Table Code []: Activity Table Code []:100 Key Options []: Product Token []: Hardware-Id []: Checksum []:X-XXXX-XXXX-XXXX-XXXX Here is a list of the license information just entered: Issuer: DEC Authorization: HOBBYIST-VA-KEYXXXXX-XXXXXX Product Name: VAX-VMS Producer: DEC Units: 0 Release Date: Version: Termination Date: 28-APR-2017 Availability: Activity: CONSTANT=100 Options: Token: Hardware ID: Checksum: X-XXXX-XXXX-XXXX-XXXX Is that 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 Press RETURN to return to the main menu 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 return to this menu. Enter one of the above choices [1]: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. Type '?' at any prompt for a description of the information requested. Press Ctrl/Z at any prompt to return to the main menu. Issuer [DEC]: Authorization Number []:HOBBYIST-VA-KEYXXXXX-XXXXXX Product Name []:DVNETRTG Producer [DEC]: Number of Units []:0 Version []: Product Release Date []: Key Termination Date []:28-APR-2017 Availability Table Code []: Activity Table Code []:100 Key Options []: Product Token []: Hardware-Id []: Checksum []:X-XXXX-XXXX-XXXX-XXXX Here is a list of the license information just entered: Issuer: DEC Authorization: HOBBYIST-VA-KEYXXXXX-XXXXXX Product Name: DVNETRTG Producer: DEC Units: 0 Release Date: Version: Termination Date: 28-APR-2017 Availability: Activity: CONSTANT=100 Options: Token: Hardware ID: Checksum: X-XXXX-XXXX-XXXX-XXXX Is that correct? [YES]: Registering DVNETRTG license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB... Do you want to LOAD this license on this system? [YES]: %LICENSE-I-LOADED, DEC DVNETRTG was successfully loaded with 0 units Press RETURN to return to the main menu 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 return to this menu. Enter one of the above choices [4]:99 ******************************************************************************** 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 OpenVMS License Management Utility Manual for any additional information you need. ******************************************************************************** Running AUTOGEN to compute the new SYSTEM parameters ... %AUTOGEN-I-BEGIN, GETDATA phase is beginning. %AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created. You may wish to purge this file. %AUTOGEN-I-END, GETDATA phase has successfully completed. %AUTOGEN-I-BEGIN, GENPARAMS phase is beginning. %AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created. You may wish to purge this file. %AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created. You may wish to purge this file. %AUTOGEN-I-END, GENPARAMS phase has successfully completed. %AUTOGEN-I-BEGIN, GENFILES phase is beginning. %SYSGEN-I-EXTENDED, DUA0:[SYS0.SYSEXE]PAGEFILE.SYS;1 extended %SYSGEN-I-EXTENDED, DUA0:[SYS0.SYSEXE]SWAPFILE.SYS;1 extended %SYSGEN-I-CREATED, SYS$SYSROOT:[SYSEXE]SYSDUMP.DMP;1 created %AUTOGEN-I-REPORT, AUTOGEN has produced some informational messages which have been stored in the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You may wish to review the information in that file. %AUTOGEN-I-END, GENFILES phase has successfully completed. %AUTOGEN-I-BEGIN, SETPARAMS phase is beginning. %AUTOGEN-I-END, SETPARAMS phase has successfully completed. %AUTOGEN-I-BEGIN, REBOOT phase is beginning. The system is shutting down to allow the system to boot with the generated site-specific parameters and installed images. The system will automatically reboot after the shutdown and the installation will be complete. SHUTDOWN -- Perform an Orderly System Shutdown %SHUTDOWN-I-BOOTCHECK, performing reboot consistency check... %SHUTDOWN-I-CHECKOK, basic reboot consistency check completed %SHUTDOWN-I-OPERATOR, this terminal is now an operator's console %OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running %SHUTDOWN-I-DISLOGINS, interactive logins will now be disabled %SET-I-INTSET, login interactive limit = 0, current interactive value = 0 %SHUTDOWN-I-STOPQUEUES, the queues on this node will now be stopped %JBC-E-OPENERR, error opening SYS$SYSROOT:[SYSEXE]QMAN$MASTER.DAT; -RMS-E-FNF, file not found SHUTDOWN message from user SYSTEM at Batch 11:17:21 The system will shut down in 0 minutes; back up SOON. Please log off. Reboot system with AUTOGENerated parameters %SHUTDOWN-I-SITESHUT, the site-specific shutdown procedure will now be invoked %SHUTDOWN-I-STOPUSER, all user processes will now be stopped %SHUTDOWN-I-REMOVE, all installed images will now be removed %SHUTDOWN-I-DISMOUNT, all volumes will now be dismounted %OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running %OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running [Comment: System halted at this point (possibly by sending BREAK at the terminal - I can't recall exactly] >>>show boot >>>set boot dua0 >>>show boot DUA0 [SIMH restarted at this point] 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 (BOOT/R5:0 DUA0 2.. -DUA0 1..0.. OpenVMS VAX Version V6.1 Major version id = 1 Minor version id = 0 ***************************************************************** OpenVMS VAX V6.1 You have SUCCESSFULLY installed the OpenVMS VAX 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 11-JUN-2016 11:21:41.08 %DCL-S-SPAWNED, process SYSTEM_1 spawned %%%%%%%%%%% OPCOM 11-JUN-2016 11:21:51.00 %%%%%%%%%%% Operator _SIMH3$OPA0: has been enabled, username SYSTEM %%%%%%%%%%% OPCOM 11-JUN-2016 11:21:51.00 %%%%%%%%%%% Operator status for operator _SIMH3$OPA0: CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY, LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12 %%%%%%%%%%% OPCOM 11-JUN-2016 11:21:51.02 %%%%%%%%%%% Logfile has been initialized by operator _SIMH3$OPA0: Logfile is SIMH3::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1 %%%%%%%%%%% OPCOM 11-JUN-2016 11:21:51.02 %%%%%%%%%%% Operator status for operator SIMH3::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 11-JUN-2016 11:21:51.16 %%%%%%%%%%% Message from user AUDIT$SERVER on SIMH3 %AUDSRV-I-NEWSERVERDB, new audit server database created %%%%%%%%%%% OPCOM 11-JUN-2016 11:21:51.21 %%%%%%%%%%% Message from user AUDIT$SERVER on SIMH3 %AUDSRV-I-REMENABLED, resource monitoring enabled for journal SECURITY %%%%%%%%%%% OPCOM 11-JUN-2016 11:21:51.29 %%%%%%%%%%% Message from user AUDIT$SERVER on SIMH3 %AUDSRV-I-NEWOBJECTDB, new object database created %SET-I-NEWAUDSRV, identification of new audit server process is 0000020A %%%%%%%%%%% OPCOM 11-JUN-2016 11:21:52.68 %%%%%%%%%%% Message from user JOB_CONTROL on SIMH3 %JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT; %%%%%%%%%%% OPCOM 11-JUN-2016 11:21:52.69 %%%%%%%%%%% Message from user JOB_CONTROL on SIMH3 -RMS-E-FNF, file not found %%%%%%%%%%% OPCOM 11-JUN-2016 11:21:53.50 %%%%%%%%%%% Message from user SYSTEM on SIMH3 %SECSRV-E-NOPROXYDB, proxy database does not exist %RMS-E-FNF, file not found %%%%%%%%%%% OPCOM 11-JUN-2016 11:21:53.52 %%%%%%%%%%% Message from user SYSTEM on SIMH3 %SECSRV-E-NOPROXYDB, proxy database does not exist %RMS-E-FNF, file not found %%%%%%%%%%% OPCOM 11-JUN-2016 11:21:53.53 %%%%%%%%%%% Message from user SYSTEM on SIMH3 %SECSRV-I-SERVERSTARTINGU, Security Server starting up. %%%%%%%%%%% OPCOM 11-JUN-2016 11:21:53.54 %%%%%%%%%%% Message from user SYSTEM on SIMH3 %SECSRV-I-CIASTARTINGUP, breakin detection and evasion now starting up %%%%%%%%%%% OPCOM 11-JUN-2016 11:21:54.56 %%%%%%%%%%% Message from user SYSTEM on SIMH3 Warning: DECdtm log file not found (SYS$JOURNAL:SYSTEM$SIMH3.LM$JOURNAL) %RMS-E-FNF, file not found TP server process waiting %%%%%%%%%%% OPCOM 11-JUN-2016 11:21:54.89 %%%%%%%%%%% Message from user AUDIT$SERVER on SIMH3 Security alarm (SECURITY) and security audit (SECURITY) on SIMH3, system id: 4111 Auditable event: Audit server starting up Event time: 11-JUN-2016 11:21:54.85 PID: 0000020A %%%%%%%%%%% OPCOM 11-JUN-2016 11:21:55.12 %%%%%%%%%%% Message from user AUDIT$SERVER on SIMH3 Security alarm (SECURITY) and security audit (SECURITY) on SIMH3, system id: 4111 Auditable event: Identifier added Event time: 11-JUN-2016 11:21:55.11 PID: 00000203 Process name: STARTUP Username: SYSTEM Process owner: [SYSTEM] Image name: SIMH3$DUA0:[SYS0.SYSCOMMON.][SYSEXE]AUTHORIZE.EXE Identifier name: SYS$NODE_SIMH3 Identifier value: %X80010000 Attributes: none %UAF-I-RDBADDMSG, identifier SYS$NODE_SIMH3 value %X80010000 added to rights database %SET-I-INTSET, login interactive limit = 64, current interactive value = 0 SYSTEM job terminated at 11-JUN-2016 11:21:56.42 Accounting information: Buffered I/O count: 1233 Peak working set size: 835 Direct I/O count: 471 Peak page file size: 4308 Page faults: 5181 Mounted volumes: 0 Charged CPU time: 0 00:00:12.66 Elapsed time: 0 00:00:17.02 Welcome to OpenVMS VAX V6.1 Username: SYSTEM Password: Welcome to OpenVMS VAX version V6.1 $ dir Directory SYS$SYSROOT:[SYSMGR] ACCOUNTNG.DAT;1 CLUE$LAST_SIMH3.LIS;1 OPERATOR.LOG;1 VMSIMAGES.DAT;1 Total of 4 files. Directory SYS$COMMON:[SYSMGR] AGEN$NEW_NODE_DEFAULTS.DAT;1 AGEN$NEW_NODE_DEFAULTS.TEMPLATE;1 AGEN$NEW_SATELLITE_DEFAULTS.DAT;1 AGEN$NEW_SATELLITE_DEFAULTS.TEMPLATE;1 AGENPARAMS.EXE;1 ALFMAINT.COM;1 CLUSTER_CONFIG.COM;1 DBLSTRTUP.COM;1 DECW$STARTXTERMINAL.COM;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$JOURNAL;1 SMISERVER.COM;1 SNAPSHOT$CLEANUP.COM;1 SNAPSHOT$NEW_DISK.COM;1 SNAPSHOT$SYCLEANUP.TEMPLATE;1 SNAPSHOT$SYSHUTDOWN.TEMPLATE;1 SNAPSHOT.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_VMS.COM;1 SYSTARTUP_VMS.TEMPLATE;1 TFF$STARTUP.COM;1 UTC$CONFIGURE_TDF.COM;1 VMS$AUDIT_SERVER.DAT;1 VMS$IMAGES_MASTER.DAT;1 VMSIMAGES.DAT;1 WELCOME.TEMPLATE;1 WELCOME.TXT;1 Total of 54 files. Grand total of 2 directories, 58 files. $ shutdown SHUTDOWN -- Perform an Orderly System Shutdown on node SIMH3 %SHUTDOWN-I-OPERATOR, this terminal is now an operator's console %%%%%%%%%%% OPCOM 11-JUN-2016 11:23:00.38 %%%%%%%%%%% Operator status for operator _SIMH3$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 %%%%%%%%%%% OPCOM 11-JUN-2016 11:23:01.08 %%%%%%%%%%% Message from user JOB_CONTROL on SIMH3 %JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT; %%%%%%%%%%% OPCOM 11-JUN-2016 11:23:01.09 %%%%%%%%%%% Message from user JOB_CONTROL on SIMH3 -RMS-E-FNF, file not found SHUTDOWN message on SIMH3 from user SYSTEM at _SIMH3$OPA0: 11:23:01 SIMH3 will shut down in 0 minutes; back up LATER. Please log off node SIMH3. SHUTDOWN 1 terminal has been notified on SIMH3. %SHUTDOWN-I-STOPUSER, all user processes will now be stopped %SHUTDOWN-I-STOPAUDIT, the security auditing subsystem will now be shut down %%%%%%%%%%% OPCOM 11-JUN-2016 11:23:10.65 %%%%%%%%%%% Message from user AUDIT$SERVER on SIMH3 Security alarm (SECURITY) and security audit (SECURITY) on SIMH3, system id: 411 1 Auditable event: Audit server shutting down Event time: 11-JUN-2016 11:23:10.63 PID: 0000020E %SHUTDOWN-I-REMOVE, all installed images will now be removed %SHUTDOWN-I-DISMOUNT, all volumes will now be dismounted %%%%%%%%%%% OPCOM 11-JUN-2016 11:23:12.55 %%%%%%%%%%% Message from user SYSTEM on SIMH3 _SIMH3$OPA0:, SIMH3 shutdown was requested by the operator. %%%%%%%%%%% OPCOM 11-JUN-2016 11:23:12.60 %%%%%%%%%%% Logfile was closed by operator _SIMH3$OPA0: Logfile was SIMH3::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1 %%%%%%%%%%% OPCOM 11-JUN-2016 11:23:12.67 %%%%%%%%%%% Operator _SIMH3$OPA0: has been disabled, username SYSTEM SYSTEM SHUTDOWN COMPLETE - use console to halt system Disconnected from the MicroVAX 3900 simulator