El siguiente paso en la tarea de montar mi OpenVMS es configurar el simulador simh para poder ejecutarlo. Aquí empiezo a entrar en un terreno desconocido (al menos para mí) así que espero ir poniendo toda la atención. Por el camino, he ido encontrando algunos sitios en internet que dan una cierta orientación a mi tarea.
En primer lugar, voy a crear un directorio vax bajo /usr/local y bajo este directorio, dos subdirectorios uno llamado bin donde colocaré el binario del simulador y las ROMs de VAX y otro data donde irán los datos del simulador:
Ahora copio los ficheros a la localización recién creada:
Creo, bajo /usr/local/bin/vax un directorio images y copio la imagen iso del SO (usando WinSCP). Aprovecho y copio, al mismo directorio el fichero con la licencia:
Creo el fichero de inicialización (openvms.ini) del simulador y lo coloco en el directorio data.
Ya tenemos todo preparado para el primer arranque. Hay que ejecutar el simulador bajo un usuario privilegiado:
Se ha tomado su tiempo, sobre todo creando los discos virtuales pero parece que ya está arrancado. Hago un comando show device para ver que dispositivos hay y procedo al primer arranque de VAX que debe ser desde el CDROM virtual:
El CDROM virtual es la unidad DUA3. A por el boot:
VAX ha arrancado en modo monousuario y vamos a instalar el sistema operativo desde el backup existente en el CDROM:
Una vez completado esto salimos de la simulación (Ctrl-E). A continuación vamos a proceder a arrancar desde el disco duro y a realizar la instalación de OpenVMS. He capturado en un fichero las entradas y salidas durante el proceso:
1. Arranque de la boot ROM:
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.
2. Configurar el dispositivo desde el que se va a arrancar (DUA0) y arrancar en sistema (BOOT):
>>>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
3. Configurar la fecha y hora. Se va a quejar que no está licenciado.
* Please enter the date and time (DD-MMM-YYYY HH:MM) 15-DEC-2018 20:04
*********************************************************
%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 15-DEC-2018 20:04:07.27 %%%%%%%%%%%
Operator _OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 15-DEC-2018 20:04:07.28 %%%%%%%%%%%
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 15-DEC-2018 20:04:07.37 %%%%%%%%%%%
Logfile has been initialized by operator _OPA0:
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
%%%%%%%%%%% OPCOM 15-DEC-2018 20:04:07.38 %%%%%%%%%%%
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
%%%%%%%%%%% OPCOM 15-DEC-2018 20:04:09.36 %%%%%%%%%%%
Message from user JOB_CONTROL
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 15-DEC-2018 20:04:09.37 %%%%%%%%%%%
Message from user JOB_CONTROL
-RMS-E-FNF, file not found
%LICENSE-F-EMTLDB, license database contains no license records
%SYSTEM-I-BOOTUPGRADE, security server not started
%%%%%%%%%%% OPCOM 15-DEC-2018 20:04:11.70 %%%%%%%%%%%
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
4. Como vemos, se queja de que el sistema no está licenciado, eso lo dejaremos para más adelante. A continuación nos va a pedir una serie de parámetros y el volumen desde el que se va a instalar OpenVMS:
Startup processing continuing...
%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]:
* 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:
5. Nos va a pedir, a continuación, el software que deseamos instalar. Decido no instalar el software de DECNet, ni el soporte de clustering, ni la parte gráfica:
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]]
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.
6. A continuación, establecemos las contraseñas de cuentas importantes, nos proporciona una serie de consejos y acciones a realizar:
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:
* 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: TCVAX
* 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.
7. A continuación, nos pregunta si queremos registrar el producto y le contestamos que no, en el siguiente boot cargaremos el PAK con las licencias:
=================================================================
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.
********************************************************************************
8. En el siguiente paso, vamos a configurar la zona horaria y, finaliza la instalación prometiendo que va a arrancar de nuevo (cosa que no hace):
%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: 20
You selected MET as your time zone.
Is this correct? (Yes/No) [YES]:
Default Time Differential Factor for standard time is 1:00.
Default Time Differential Factor for daylight saving time is 2:00.
Is Daylight Savings time in effect? (Yes/No): n
Enter the Time Differential Factor [1:00]:
NEW SYSTEM TIME DIFFERENTIAL FACTOR = 1:00.
Is this correct? [Y]:
********************************************************************************
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 20:24:36
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> Simulation stopped, PC: 839ABD36 (ASHL #1,R3,R0)
Hasta aquí la instalación de OpenVMS. Ahora voy a intentar instalar la licencia. La licencia es un fichero de comandos ejecutable por lo que lo que tengo es que intentar hacerlo llegar al sistema de archivos de OpenVMS.
Antes de nada, voy a intentar rearrancar el sistema. Para ver si funciona:
La secuencia de mensajes, durante el arranque de OpenVMS es:
(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 16-DEC-2018 10:02:25.02
%RUN-S-PROC_ID, identification of created process is 00000206
%DCL-S-SPAWNED, process SYSTEM_1 spawned
%%%%%%%%%%% OPCOM 16-DEC-2018 10:02:46.13 %%%%%%%%%%%
Operator _TCVAX$OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 16-DEC-2018 10:02:46.14 %%%%%%%%%%%
Operator status for operator _TCVAX$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-DEC-2018 10:02:46.44 %%%%%%%%%%%
Logfile has been initialized by operator _TCVAX$OPA0:
Logfile is TCVAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;2
%%%%%%%%%%% OPCOM 16-DEC-2018 10:02:46.44 %%%%%%%%%%%
Operator status for operator TCVAX::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;2
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12
%SET-I-NEWAUDSRV, identification of new audit server process is 0000020C
%%%%%%%%%%% OPCOM 16-DEC-2018 10:02:47.54 %%%%%%%%%%%
Message from user JOB_CONTROL on TCVAX
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 16-DEC-2018 10:02:47.54 %%%%%%%%%%%
Message from user JOB_CONTROL on TCVAX
-RMS-E-FNF, file not found
%LICENSE-F-EMTLDB, license database contains no license records
%%%%%%%%%%% OPCOM 16-DEC-2018 10:02:49.19 %%%%%%%%%%%
Message from user SYSTEM on TCVAX
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 16-DEC-2018 10:02:49.22 %%%%%%%%%%%
Message from user SYSTEM on TCVAX
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 16-DEC-2018 10:02:49.28 %%%%%%%%%%%
Message from user SYSTEM on TCVAX
%SECSRV-I-CIACRECLUDB, security server created cluster intrusion database
%%%%%%%%%%% OPCOM 16-DEC-2018 10:02:49.29 %%%%%%%%%%%
Message from user SYSTEM on TCVAX
%SECSRV-I-SERVERSTARTINGU, security server starting up
%%%%%%%%%%% OPCOM 16-DEC-2018 10:02:49.37 %%%%%%%%%%%
Message from user SYSTEM on TCVAX
%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 16-DEC-2018 10:02:51.06 %%%%%%%%%%%
Message from user SYSTEM on TCVAX
%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-DEC-2018 10:02:51.81 %%%%%%%%%%%
Message from user SYSTEM on TCVAX
Warning: DECdtm log file not found (SYS$JOURNAL:SYSTEM$TCVAX.LM$JOURNAL)
%RMS-E-FNF, file not found
TP server process waiting
%%%%%%%%%%% OPCOM 16-DEC-2018 10:02:53.71 %%%%%%%%%%%
Message from user AUDIT$SERVER on TCVAX
Security alarm (SECURITY) and security audit (SECURITY) on TCVAX, system id: 1025
Auditable event: Audit server starting up
Event time: 16-DEC-2018 10:02:53.55
PID: 00000203
Username: SYSTEM
%STARTUP-I-AUDITCONTINUE, audit server initialization complete
The OpenVMS VAX system is now executing the site-specific startup commands.
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
SYSTEM job terminated at 16-DEC-2018 10:02:55.32
Accounting information:
Buffered I/O count: 1134 Peak working set size: 1791
Direct I/O count: 499 Peak page file size: 4924
Page faults: 3385 Mounted volumes: 0
Charged CPU time: 0 00:00:22.56 Elapsed time: 0 00:00:30.76
Welcome to OpenVMS (TM) VAX Operating System, Version V7.3
Username:
De entrada, observo que la hora está mal configurada, el sistema tiene una hora menos que la que debería. Procedo a hacer logon en el sistema y aparece una pantalla ancha con el prompt de VAX (‘$’):
El fichero de licencias es un fichero de texto de más de 2000 líneas que tiene una serie de comandos VAX. Voy a intentar hacer un copia y pega desde un editor del PC al editor de VAX dentro de la simulación. Para ello, lanzo el comando:
$ EDIT PACKS.COM
Se abre el editor, copio las líneas del fichero de licencias desde el Notepad++ del PC y, en la ventana del terminal, al pulsar el botón de la derecha del ratón, se pegan las líneas. Tarda un ratito y, una vez pegadas pulso Ctrl-Z para salvar el fichero y, ahí está:
Lo último que me queda es activar la licencia ejecutando el fichero de comandos:
$ @PACKS.COM
La ejecución del fichero de comandos se toma su tiempo y cuando finaliza voy a reiniciar la máquina para terminar la configuración:
$ @SYS$SYSTEM:SHUTDOWN
Las últimas tareas que voy a realizar (por ahora) son configurar los otros dos discos que tengo en el sistema. Voy a ejecutar los comandos siguientes (tendré que configurar esto para que el montaje se haga en cada uno de los arranques):
Por ahora nada más. Bajarme la documentación y recordar DCL.
Hacía tiempo que no escribía nada nuevo fundamentalmente porque estoy empleando otros medios para documentar las ñapas que voy haciendo. Sin embargo, me parece interesante compartir la experiencia que acabo de completar así que voy a hacer una serie de posts sobre ello.
El Ñapas 
