Herramientas de usuario
Herramientas del sitio
vax:system
Instalación del Sistema Operativo
root@VAX:~/VMS73 # vax
VAX simulator V3.11-0
NVR: creating new file
NVR: buffering file in memory
RQ: creating new file
RQ: creating new file
RQ: unit is read only
libpcap version 1.3.0
Eth: opened OS device eth0
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.
>>>
Si no está ya, se “introduce” la imagen de disco en el “lector virtual”.
>>> (Pulsar Ctrl+E) Simulation stopped, PC: 834B4F43 (CMPL R4,R5) sim> attach -r rq3 openvms-vax-073-os.iso RQ: unit is read only sim> cont _
y luego se continúa arrancando el CD
boot dua3: (BOOT/R5:0 DUA3 2.. -DUA3 1..0.. %SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk %SYSBOOT-W-SYSBOOT Can not map SYSDUMP.DMP on the System Disk %SYSBOOT-W-SYSBOOT Can not map PAGEFILE.SYS on the System Disk OpenVMS (TM) VAX Version X7G7 Major version id = 1 Minor version id = 0 %WBM-I-WBMINFO Write Bitmap has successfully completed initialization. PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) dd-mmm-yyyy hh:mm 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 RA92 Available device DUA1: device type RA92 Available device DUA3: device type RRD40 Enter "YES" when all needed devices are available: y %BACKUP-I-IDENT, Stand-alone BACKUP T7.2; the date is dd-mmm-yyyy hh:mm:ss.cc $ backup dua3:vms073.b/save_set dua0: %BACKUP-I-PROCDONE, operation completed. Processing finished at dd-mmm-yyyy hh:mm:ss.cc 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: (Pulsar Ctrl+E) Simulation stopped, PC: 839ABD40 (MOVL (R5),R4) sim> _
sim> boot cpu 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. >>>set boot dua0 >>>boot (BOOT/R5:0 DUA0 2.. -DUA0 1..0.. %SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk %SYSBOOT-W-SYSBOOT Can not map SYSDUMP.DMP on the System Disk %SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk %SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS OpenVMS (TM) VAX Version BI73-7G7 Major version id = 1 Minor version id = 0 %WBM-I-WBMINFO Write Bitmap has successfully completed initialization. OpenVMS VAX V7.3 Installation Procedure Model: VAXserver 3900 Series System device: RA92 - _DUA0: Free Blocks: 2854566 CPU type: 10-01 * Please enter the date and time (DD-MMM-YYYY HH:MM) dd-mmm-yyyy hh:mm ********************************************************* %SYSTEM-W-TZGMT, your local timezone has defaulted to GMT %SYSTEM-I-SETTZ, to set your local timezone use: $ @SYS$MANAGER:UTC$TIME_SETUP.COM ********************************************************* On MIN or UPGRADE system startup - CLUE is not run. %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Operator _OPA0: has been enabled, username SYSTEM %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% 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 dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Logfile has been initialized by operator _OPA0: Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1 %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% 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 dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% 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 dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user JOB_CONTROL %JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT; %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user JOB_CONTROL -RMS-E-FNF, file not found %SET-I-INTSET, login interactive limit = 1, current interactive value = 0 %SET-I-INTSET, login interactive limit = 0, current interactive value = 0 If this system disk is to be used in an OpenVMS 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 OVMSVAXSYS, press RETURN in response to the next question. * Enter the volume label for this system disk [OVMSVAXSYS]: (Pulsar ENTER) * Enter name of drive holding the OpenVMS distribution media: dua3 * Is the OpenVMS media ready to be mounted? [N] y %MOUNT-I-MOUNTED, VAXVMS073 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 - 52200 blocks o OpenVMS optional - 19000 blocks o OpenVMS Help Message - 10400 blocks o OpenVMS Management Station - 20000 blocks o DECwindows base support - 4400 blocks o DECwindows workstation support - 23800 blocks - 75 dots per inch video fonts - (included) - 100 dots per inch video fonts - 6200 blocks o DECnet-Plus networking - 80000 blocks o DECnet Phase IV networking - 800 blocks Space remaining on system disk: 2854377 blocks * Do you want to install the OpenVMS library files? (Y/N) y Space remaining on system disk: 2802177 blocks * Do you want to install the OpenVMS optional files? (Y/N) y Space remaining on system disk: 2783177 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 10400 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]] (Pulsar ENTER) Space remaining on system disk: 2772777 blocks The OpenVMS Management Station is a client-server application that provides OpenVMS system management capabilities through a client application on a personal computer (PC) running Microsoft Windows. The server application runs on OpenVMS systems and is automatically installed as part of the OpenVMS operating system. This option provides the files used to install the PC client software. If you want to use the OpenVMS Management Station, you must install these optional files on at least one OpenVMS system and then use one or both of them to install the PC client on one or more PCs. There are two files: TNT030_I.EXE for Intel systems (Windows 95 and Windows NT), and TNT030_A.EXE for Alpha Windows NT systems. The OpenVMS Management Station optional files consume approximately 20000 blocks and will be placed on your system disk in SYS$COMMON:[TNT.CLIENT]. * Do you want to install the optional OpenVMS Management Station files? (Y/N) y Space remaining on system disk: 2752777 blocks You can select DECwindows 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 select DECwindows now and tailor off unwanted files later. NOTE: This kit does NOT contain full DECwindows. To obtain full DECwindows, you must also install the separate layered product, DECwindows Motif for OpenVMS VAX. V1.2-3 is the minimum version of DECwindows Motif for OpenVMS VAX that can be used with OpenVMS VAX V7.3. The DECwindows components provided in this kit requires approximately 34400 blocks, broken down as follows: o DECwindows base support - 4400 blocks o DECwindows workstation support - 23800 blocks - 75 dots per inch video fonts - (included) - 100 dots per inch video fonts (optional) - 6200 blocks You must select the DECwindows base support option if - you plan to run DECwindows software, or - you are installing this kit on * a workstation or * an OpenVMS Cluster that contains workstations, or - you want to provide font files for Xterminals. If you are installing this kit on a system that includes Xterminals and you do NOT select DECwindows base support, then you will have to use the DECW$TAILOR utility to provide font files. * Do you want the DECwindows base support? (Y/N) n Beginning with OpenVMS V7.1, the DECnet-Plus kit is provided with the OpenVMS operating system kit. Compaq strongly recommends that DECnet users install DECnet-Plus. DECnet Phase IV applications are supported by DECnet-Plus. DECnet Phase IV is also provided as an option. Support for DECnet Phase IV is available through a Prior Version Support Contract. If you install DECnet-Plus and TCP/IP you can run DECnet applications over a TCP/IP network. Please see the OpenVMS Management Guide for information on running DECnet over TCI/IP. If you plan to install DECnet Phase IV do NOT select DECnet-Plus. * Do you want to install DECnet-Plus? (Y/N) n * Do you want to install DECnet Phase IV? (Y/N) n The following options will be provided: OpenVMS library OpenVMS optional OpenVMS Help Message OpenVMS Management Station Software -- PC files Space remaining on system disk: 2752777 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 Management Station Software -- PC files %BACKUP-I-STARTVERIFY, starting verification pass Now registering the OpenVMS operating system in the POLYCENTER Software Installation product database The following product will be registered: DEC VAXVMS VMS V7.3 DISK$VAXVMSV73:[VMS$COMMON.] The following product has been registered: DEC VAXVMS VMS V7.3 Transition (registration) You can now remove the distribution kit from DUA3:. In an OpenVMS Cluster, you can run multiple systems sharing all files except PAGEFILE.SYS, SWAPFILE.SYS, SYSDUMP.DMP, and VAXVMSSYS.PAR. Cluster configuration cannot be done at this time because no network is present. In order to configure a cluster you must FIRST do one or both of the following: o Install DECnet-Plus (or DECnet Phase IV), or o Execute SYS$STARTUP:LAN$STARTUP.COM by removing the comment delimiter ("!") from the line $! @SYS$STARTUP:LAN$STARTUP in SYS$MANAGER:SYSTARTUP_VMS.COM. Then configure the cluster by executing the following command: @ @SYS$MANAGER:CLUSTER_CONFIG See the OpenVMS System Manager's Manual: Essentials for more information. 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: (Teclear la clave deseada) * Re-enter for verification: (Repetir la clave anterior) %UAF-I-MDFYMSG, user record(s) updated %VMS-I-PWD_OKAY, account password for SYSTEM verified * Enter password for SYSTEST: (Teclear la clave deseada) * Re-enter for verification: (Repetir la clave anterior) %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: (Teclear la clave deseada) * Re-enter for verification: (Repetir la clave anterior) %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: vax * Please enter the SCSSYSTEMID: 1025 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 "Backup Procedures" chapter of tye upgrade and installation supplement provided 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 V7.3 Installation Procedure. Configuring all devices on the system ... 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): n ******************************************************************************** After the system has rebooted you must register any Product Authorization Keys (PAKs) that you have received with this kit. You can register these PAKs by executing the following procedure: $ @SYS$UPDATE:VMSLICENSE See the OpenVMS License Management Utility Manual for any additional information you need. ******************************************************************************** %UTC-I-UPDTIME, updating Time Zone information in SYS$COMMON:[SYSEXE] Configuring the Local Time Zone TIME ZONE SPECIFICATION -- Main Time Zone Menu 1) Australia 11) GMT 21) Mexico 31) Turkey 2) Brazil 12) Greenwich 22) NZ 32) UCT 3) CET 13) Hong Kong 23) NZ-CHAT 33) US 4) Canada 14) Iceland 24) Navajo 34) UTC 5) Chile 15) Iran 25) PRC 35) Universal 6) Cuba 16) Israel 26) Poland 36) W-SU 7) EET 17) Jamaica 27) ROC 37) WET 8) Egypt 18) Japan 28) ROK 38) Zulu 9) Factory 19) Libya 29) Singapore 10) GB-Eire 20) MET 30) SystemV 0) None of the above Select the number above that best describes your location: 3 You selected CET as your time zone. Is this correct? (Yes/No) [YES]: (Pulsar ENTER) 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 repects 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.). Is Daylight Savings time in effect? (Yes/No): n
Nota: Esta pregunta corresponde al cambio de hora, contestando n en invierno o y en verano, con lo que la diferencia horaria, en la siguiente pregunta será 1:00 en invierno y 2:00 en verano.
Enter the Time Differential Factor [1:00]: (Pulsar ENTER) NEW SYSTEM TIME DIFFERENTIAL FACTOR = 1:00. Is this correct? [Y]: (Pulsar ENTER) ******************************************************************************** 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, SYS$SYSROOT:[SYSEXE]PAGEFILE.SYS;1 extended %SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]SWAPFILE.SYS;1 extended %SYSGEN-I-CREATED, SYS$SPECIFIC:[SYSEXE]SYSDUMP.DMP;1 created %SYSGEN-I-CREATED, DUA0:[SYS0.SYSEXE]ERRORLOG.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$COMMON:[SYSEXE]QMAN$MASTER.DAT; -RMS-E-FNF, file not found SHUTDOWN message from user SYSTEM at Batch 19:58:47 The system will shut down in 0 minutes; back up SOON. Please log off. Reboot system with AUTOGENerated parameters %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 HALT instruction, PC: 8443B709 (MOVB 400(R1),R0) sim> _
sim> boot cpu 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.. %SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk %SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped %SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk %SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS OpenVMS (TM) VAX Version V7.3 Major version id = 1 Minor version id = 0 %WBM-I-WBMINFO Write Bitmap has successfully completed initialization. ***************************************************************** OpenVMS VAX V7.3 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, OpenVMS startup begun at dd-mmm-yyyy hh:mm:ss.cc %RUN-S-PROC_ID, identification of created process is 00000206 %DCL-S-SPAWNED, process SYSTEM_1 spawned %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Operator _VAX$OPA0: has been enabled, username SYSTEM %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Operator status for operator _VAX$OPA0: CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY, LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12 %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Logfile has been initialized by operator _VAX$OPA0: Logfile is VAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1 %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Operator status for operator VAX::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 dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user AUDIT$SERVER on VAX %AUDSRV-I-NEWSERVERDB, new audit server database created %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user AUDIT$SERVER on VAX %AUDSRV-I-REMENABLED, resource monitoring enabled for journal SECURITY %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user AUDIT$SERVER on VAX %AUDSRV-I-NEWOBJECTDB, new object database created %SET-I-NEWAUDSRV, identification of new audit server process is 0000020C %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user JOB_CONTROL on VAX %JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT; %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user JOB_CONTROL on VAX -RMS-E-FNF, file not found %LICENSE-F-EMTLDB, license database contains no license records %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX %SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT %RMS-E-FNF, file not found %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX %SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT %RMS-E-FNF, file not found %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX %SECSRV-I-CIACRECLUDB, security server created cluster intrusion database %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX %SECSRV-I-SERVERSTARTINGU, security server starting up %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX %SECSRV-I-CIASTARTINGUP, breakin detection and evasion processing now starting up %SMG-W-GBLNOTCRE, global section not created -SYSTEM-F-GPTFULL, global page table is full %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX %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 dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX Warning: DECdtm log file not found (SYS$JOURNAL:SYSTEM$VAX.LM$JOURNAL) %RMS-E-FNF, file not found TP server process waiting %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user AUDIT$SERVER on VAX Security alarm (SECURITY) and security audit (SECURITY) on VAX, system id: 1025 Auditable event: Audit server starting up Event time: dd-mmm-yyyy hh:mm:ss.cc PID: 00000203 Username: SYSTEM %STARTUP-I-AUDITCONTINUE, audit server initialization complete The OpenVMS VAX system is now executing the site-specific startup commands. %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user AUDIT$SERVER on VAX Security alarm (SECURITY) and security audit (SECURITY) on VAX, system id: 1025 Auditable event: Identifier added Event time: dd-mmm-yyyy hh:mm:ss.cc PID: 00000203 Process name: STARTUP Username: SYSTEM Process owner: [SYSTEM] Image name: VAX$DUA0:[SYS0.SYSCOMMON.][SYSEXE]AUTHORIZE.EXE Identifier name: SYS$NODE_VAX Identifier value: %X80010000 Attributes: none %UAF-I-RDBADDMSG, identifier SYS$NODE_VAX value %X80010000 added to rights database %SET-I-INTSET, login interactive limit = 64, current interactive value = 0 SYSTEM job terminated at dd-mmm-yyyy hh:mm:ss.cc Accounting information: Buffered I/O count: 1520 Peak working set size: 1709 Direct I/O count: 565 Peak page file size: 4963 Page faults: 4903 Mounted volumes: 0 Charged CPU time: 0 00:00:10.98 Elapsed time: 0 00:00:14.40(Pulsar ENTER) Welcome to OpenVMS (TM) VAX Operating System, Version V7.3 Username: system Password: (Teclear la clave correspondiente) %LICENSE-I-NOLICENSE, no license is active for this software product %LOGIN-S-LOGOPRCON, login allowed from OPA0: Welcome to OpenVMS (TM) VAX Operating System, Version V7.3 $ _
Se registra el producto, para lo que es necesario disponer de una PAK adecuada para el producto VAX-VMS
Se invoca la utilidad de registro de licencias con:
$ @sys$update:vmslicense
que presenta la pantalla siguiente:
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]:_
Se selecciona la opción 1
Do you have your Product Authorization Key? [YES]:(Pulsar ENTER)
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]:(Pulsar ENTER)
Authorization Number []:HOBBYIST-XX-KEY99999-999999
Product Name []:vax-vms
Producer [DEC]:(Pulsar ENTER)
Number of Units []:0
Version []:(Pulsar ENTER)
Product Release Date []:(Pulsar ENTER)
Key Termination Date []:dd-mmm-yyyy
Availability Table Code []:(Pulsar ENTER)
Activity Table Code []:100
Key Options []:(Pulsar ENTER)
Product Token []:(Pulsar ENTER)
Hardware-Id []:(Pulsar ENTER)
Checksum []:9-XXXX-XXXX-XXXX-XXXX
Here is a list of the license information just entered:
Issuer: DEC
Authorization: HOBBYIST-XX-KEY99999-999999
Product Name: VAX-VMS
Producer: DEC
Units: 0
Release Date:
Version:
Termination Date: dd-mmm-yyyy
Availability:
Activity: CONSTANT=100
Options:
Token:
Hardware ID:
Checksum: 9-XXXX-XXXX-XXXX-XXXX
Is that correct? [YES]:(Pulsar ENTER)
Registering VAX-VMS license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB...
Do you want to LOAD this license on this system? [YES]:(Pulsar ENTER)
%LICENSE-I-LOADED, DEC VAX-VMS was successfully loaded with 0 units
Press RETURN to return to the main menu(Pulsar ENTER)
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]:99
$ _
Ahora se inicializa y configura el disco duro adicional que se utilizará para datos, espacio de usuarios, etc. Se define un usuario llamado John Doe (JDOE):
$ initialize dua1: data1 $ mount/system dua1 data1 %MOUNT-I-MOUNTED, DATA1 mounted on _VAX$DUA1: $ set term/vt100 $ edit sys$manager:systartup_vms.com
Se borra la pantalla y aparece el editor, con la tecla [AvPág] se avanza al final
$!
$! SYS$MANAGER:SYSTARTUP_VMS.COM
$!
$! This is the template for the site-specific startup command procedure.
$!
$! As of OpenVMS V7.2, this template is common for OpenVMS Alpha and VAX.
$! Any changes to the template will be made to both systems.
$!
$!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
$!
$! NOTE: On OpenVMS VAX systems, this file replaces the site-specifice
$! startup procedure, SYS$MANAGER:SYSTARTUP_V5.COM. Only the name
$! has been changed, the functionality is the same.
$! See the documentation for further details.
$!
$!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
$!
$! You may add commands to this procedure or change the commands within this
$! procedure as needed for your system. This command procedure is saved when
$! you upgrade or update to a new version of OpenVMS. Other startup command
$! procedures are replaced with each release of OpenVMS. Place symbol
Buffer: SYSTARTUP_VMS.COM | Write | Insert | Forward
408 lines read from file SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM;1
y se añaden las líneas siguientes
$! $! $! To start the OpenVMS Management Station server application, remove the $! the comment delimiter ($!) from the command line below. $! $!$ @SYS$STARTUP:TNT$STARTUP $! $! $! Remove the comment delimiter ($!) from the following line to have $! Monitor run with TCP/IP. $! $!$ @SYS$STARTUP:VPM$STARTUP.COM $! $! $! Remove the comment delimiter ($!) from the following line to start $! RPC services. $! $!$ @SYS$STARTUP:DCE$RPC_STARTUP.COM $! $ MOUNT/SYSTEM DUA1 DATA1 $ EXIT Buffer: SYSTARTUP_VMS.COM | Write | Insert | Forward 408 lines read from file SYS$COMMON:[SYSMGR]SYSTARTUP_VMS.COM;1
Se pulsa [Ctrl+Z] para salir y guardar. Se continúa definiendo el nuevo usuario y creando su directorio de trabajo (en el disco DATA1)
$ set def sys$system $ run authorize UAF> add jdoe/password=temp/owner="John Doe"/dev=dua1/dir=[jdoe]/uic=[200,201]/f lag=nodisuser %UAF-I-PWDLESSMIN, new password is shorter than minimum password length %UAF-I-ADDMSG, user record successfully added %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user AUDIT$SERVER on VAX Security alarm (SECURITY) and security audit (SECURITY) on VAX, system id: 1025 Auditable event: System UAF record addition Event time: dd-mmm-yyyy hh:mm:ss.cc PID: 00000210 Process name: SYSTEM Username: SYSTEM Process owner: [SYSTEM] Terminal name: OPA0: Image name: VAX$DUA0:[SYS0.SYSCOMMON.][SYSEXE]AUTHORIZE.EXE Object class name: FILE Object name: SYS$COMMON:[SYSEXE]SYSUAF.DAT;1 User record: JDOE Default Device: New: DUA1: Original: SYS$SYSDEVICE: Default Directory: New: [JDOE] Original: [USER] Flags: New: (none) Original: DISUSER Owner: New: John Doe Original:UIC: New: [200,201] Original: [200,200] Password Date: New: (pre-expired) Original: (pre-expired) %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user AUDIT$SERVER on VAX Security alarm (SECURITY) and security audit (SECURITY) on VAX, system id: 1025 Auditable event: Identifier added Event time: dd-mmm-yyyy hh:mm:ss.cc PID: 00000210 Process name: SYSTEM Username: SYSTEM Process owner: [SYSTEM] Terminal name: OPA0: Image name: VAX$DUA0:[SYS0.SYSCOMMON.][SYSEXE]AUTHORIZE.EXE Identifier name: JDOE Identifier value: %X00800081 Attributes: none %UAF-I-RDBADDMSGU, identifier JDOE value [000200,000201] added to rights databas e UAF> exit %UAF-I-DONEMSG, system authorization file modified %UAF-I-RDBDONEMSG, rights database modified $ create/dir dua1:[jdoe] $ set directory/owner=jdoe dua1:[jdoe] $ logout SYSTEM logged out at dd-mmm-yyyy hh:mm:ss.cc
Con el comando logout se ha cerrado la sesión, ahora, para probar el nuevo usuario, se abre la sesión con los credenciales del mismo (la password definida al crearlo es “temp”)
(Pulsar ENTER) Welcome to OpenVMS (TM) VAX Operating System, Version V7.3 Username: jdoe Password: (Teclear la clave dada al crearlo: "temp") Welcome to OpenVMS (TM) VAX Operating System, Version V7.3 Your password has expired; you must set a new password to log in New password: (Teclear la clave deseada) Verification: (Repetir la clave anterior) %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user AUDIT$SERVER on VAX Security alarm (SECURITY) and security audit (SECURITY) on VAX, system id: 1025 Auditable event: System UAF record modification Event time: dd-mmm-yyyy hh:mm:ss.cc PID: 00000211 Process name: JDOE Username: JDOE Process owner: [JDOE] Terminal name: OPA0: Image name: VAX$DUA0:[SYS0.SYSCOMMON.][SYSEXE]LOGINOUT.EXE Object class name: FILE Object name: SYS$COMMON:[SYSEXE]SYSUAF.DAT;1 User record: JDOE Password Date: New: dd-mmm-yyyy hh:mm Original: (pre-expired) $ show user OpenVMS User Processes at dd-mmm-yyyy hh:mm:ss.cc Total number of users = 1, number of processes = 1 Username Interactive Subprocess Batch JDOE 1 $ logout JDOE logged out at dd-mmm-yyyy hh:mm:ss.cc(Pulsar ENTER) Welcome to OpenVMS (TM) VAX Operating System, Version V7.3 Username: system Password: (Teclear la clave correspondiente) Welcome to OpenVMS (TM) VAX Operating System, Version V7.3 Last interactive login on ???????, dd-mmm-yyyy hh:mm $ set term/vt100 $ set def sys$system $ edit modparams.dat
Se borra la pantalla y aparece el editor, donde se añaden las líneas en rojo (si no se va a utilizar ADA, entoces ADD_GBLPAGES puede reducirse a 10000):
SCSNODE="VAX" SCSSYSTEMID=1025 VAXCLUSTER=0 ADD_GBLPAGES=15000 ADD_GBLSECTIONS=100 ADD_NPAGEDYN=800000 ADD_NPAGEVIR=800000 MIN_SPTREQ=6000 [End of file] Buffer: MODPARAMS.DAT | Write | Insert | Forward 3 lines read from file SYS$SYSROOT:[SYSEXE]MODPARAMS.DAT;1
Se pulsa [Ctrl+Z] para salir y guardar y se continúa
$ set def sys$update $ @autogen getdata shutdown nofeedback %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, SYS$SYSROOT:[SYSEXE]SWAPFILE.SYS;1 extended %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, SHUTDOWN phase is beginning. The system is shutting down to allow the system to boot with the generated site-specific parameters and installed images. You must manually reboot the system after it halts. SHUTDOWN -- Perform an Orderly System Shutdown on node VAX %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 dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Operator status for operator _VAX$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 dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user JOB_CONTROL on VAX %JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT; %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user JOB_CONTROL on VAX -RMS-E-FNF, file not found SHUTDOWN message on VAX from user SYSTEM at _VAX$OPA0: 13:05:49 VAX will shut down in 0 minutes; back up LATER. Please log off node VAX. Shutting down system after setting AUTOGENerated parameters 1 terminal has been notified on VAX. %SHUTDOWN-I-SITESHUT, the site-specific shutdown procedure will now be invoked %SHUTDOWN-I-STOPUSER, all user processes will now be stopped %SHUTDOWN-I-STOPAUDIT, the security auditing subsystem will now be shut down %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user AUDIT$SERVER on VAX Security alarm (SECURITY) and security audit (SECURITY) on VAX, system id: 1025 Auditable event: Audit server shutting down Event time: dd-mmm-yyyy hh:mm:ss.cc PID: 00000215 Username: SYSTEM %SHUTDOWN-I-STOPSECSRV, the security server will now be shut down %SHUTDOWN-I-REMOVE, all installed images will now be removed %SHUTDOWN-I-DISMOUNT, all volumes will now be dismounted %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX %SECSRV-I-CIASHUTDOWN, breakin detection and evasion processing is shutting down %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX %SECSRV-I-PROXYSHUTDOWN, proxy processing is shutting down %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX %SECSRV-I-SERVERSHUTDOWN, security server shutting down %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX _VAX$OPA0:, VAX shutdown was requested by the operator. %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Logfile was closed by operator _VAX$OPA0: Logfile was VAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;2 %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Operator _VAX$OPA0: has been disabled, username SYSTEM SYSTEM SHUTDOWN COMPLETE - use console to halt system Infinite loop, PC: 833E32D3 (BRB 833E32D3) sim> _
sim> boot cpu 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.. %SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk %SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped %SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk %SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS OpenVMS (TM) VAX Version V7.3 Major version id = 1 Minor version id = 0 %WBM-I-WBMINFO Write Bitmap has successfully completed initialization. $! Copyright 2001 Compaq Computer Corporation. %STDRV-I-STARTUP, OpenVMS startup begun at dd-mmm-yyyy hh:mm:ss.cc %RUN-S-PROC_ID, identification of created process is 00000206 %DCL-S-SPAWNED, process SYSTEM_1 spawned %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Operator _VAX$OPA0: has been enabled, username SYSTEM %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Operator status for operator _VAX$OPA0: CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY, LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12 %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Logfile has been initialized by operator _VAX$OPA0: Logfile is VAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;3 %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Operator status for operator VAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;3 CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY, LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11, OPER12 %SET-I-NEWAUDSRV, identification of new audit server process is 0000020C %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user JOB_CONTROL on VAX %JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT; %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user JOB_CONTROL on VAX -RMS-E-FNF, file not found %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX %SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT %RMS-E-FNF, file not found %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX %SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT %RMS-E-FNF, file not found %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX %SECSRV-I-CIACRECLUDB, security server created cluster intrusion database %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX %SECSRV-I-SERVERSTARTINGU, security server starting up %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX %SECSRV-I-CIASTARTINGUP, breakin detection and evasion processing now starting up %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX Warning: DECdtm log file not found (SYS$JOURNAL:SYSTEM$VAX.LM$JOURNAL) %RMS-E-FNF, file not found TP server process waiting %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user AUDIT$SERVER on VAX Security alarm (SECURITY) and security audit (SECURITY) on VAX, system id: 1025 Auditable event: Audit server starting up Event time: dd-mmm-yyyy hh:mm:ss.cc PID: 00000203 Username: SYSTEM %STARTUP-I-AUDITCONTINUE, audit server initialization complete The OpenVMS VAX system is now executing the site-specific startup commands. %MOUNT-I-MOUNTED, DATA1 mounted on _VAX$DUA1: %SET-I-INTSET, login interactive limit = 64, current interactive value = 0 SYSTEM job terminated at dd-mmm-yyyy hh:mm:ss.cc Accounting information: Buffered I/O count: 1137 Peak working set size: 1562 Direct I/O count: 519 Peak page file size: 4924 Page faults: 3608 Mounted volumes: 1 Charged CPU time: 0 00:00:08.54 Elapsed time: 0 00:00:11.62(Pulsar ENTER) Welcome to OpenVMS (TM) VAX Operating System, Version V7.3 Username: system Password: (Teclear la clave correspondiente) Welcome to OpenVMS (TM) VAX Operating System, Version V7.3 Last interactive login on ???????, dd-mmm-yyyy hh:mm $ $ run sys$system:sysgen SYSGEN> SET INTSTKPAGES 20 SYSGEN> WRITE CURRENT SYSGEN> EXIT $ @sys$system:shutdown SHUTDOWN -- Perform an Orderly System Shutdown on node VAX How many minutes until final shutdown [0]: (Pulsar ENTER) Reason for shutdown [Standalone]: (Pulsar ENTER) Do you want to spin down the disk volumes [NO]? (Pulsar ENTER) Do you want to invoke the site-specific shutdown procedure [YES]? (Pulsar ENTER) Should an automatic system reboot be performed [NO]? (Pulsar ENTER) When will the system be rebooted [later]: (Pulsar ENTER) Shutdown options (enter as a comma-separated list): REBOOT_CHECK Check existence of basic system files SAVE_FEEDBACK Save AUTOGEN feedback information from this boot DISABLE_AUTOSTART Disable autostart queues Shutdown options [NONE]: (Pulsar ENTER) %SHUTDOWN-I-OPERATOR, this terminal is now an operator's console %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Operator status for operator _VAX$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 dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user JOB_CONTROL on VAX %JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT; %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user JOB_CONTROL on VAX -RMS-E-FNF, file not found SHUTDOWN message on VAX from user SYSTEM at _VAX$OPA0: 13:34:48 VAX will shut down in 0 minutes; back up later. Please log off node VAX. Standalone 1 terminal has been notified on VAX. %SHUTDOWN-I-SITESHUT, the site-specific shutdown procedure will now be invoked %SHUTDOWN-I-STOPUSER, all user processes will now be stopped %SHUTDOWN-I-STOPAUDIT, the security auditing subsystem will now be shut down %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user AUDIT$SERVER on VAX Security alarm (SECURITY) and security audit (SECURITY) on VAX, system id: 1025 Auditable event: Audit server shutting down Event time: dd-mmm-yyyy hh:mm:ss.cc PID: 00000210 Username: SYSTEM %SHUTDOWN-I-STOPSECSRV, the security server will now be shut down %SHUTDOWN-I-REMOVE, all installed images will now be removed %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX %SECSRV-I-CIASHUTDOWN, breakin detection and evasion processing is shutting down %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX %SECSRV-I-PROXYSHUTDOWN, proxy processing is shutting down %SHUTDOWN-I-DISMOUNT, all volumes will now be dismounted %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX %SECSRV-I-SERVERSHUTDOWN, security server shutting down %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Message from user SYSTEM on VAX _VAX$OPA0:, VAX shutdown was requested by the operator. %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Logfile was closed by operator _VAX$OPA0: Logfile was VAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;3 %%%%%%%%%%% OPCOM dd-mmm-yyyy hh:mm:ss.cc %%%%%%%%%%% Operator _VAX$OPA0: has been disabled, username SYSTEM SYSTEM SHUTDOWN COMPLETE - use console to halt system Infinite loop, PC: 833C2CD3 (BRB 833C2CD3) sim> quit Goodbye NVR: writing buffer to file Eth: closed eth0 root@VAX:~/MVS73 # _
Se recomienda realizar una copia de los ficheros disk0.dsk y disk1.dsk que contienen los discos duros del VAX (y comprimirlos para ahorrar espacio), así no es necesario volver a comenzar y realizar este apartado en caso de equivocaciones futuras.
En este momento, se ha instalado y configurado el sistema operativo, sin ningún añadido. Ahora, en el siguiente apartado se instalará la Red DECnet.
©2017-2024, jCæsar
Contacto
Contacto