Micro VAX 3100-80 3. Установка OpenVMS 7.3 Опции

[SuperMax]

Берем дистрибутив OpenVMS 7.3 VAX
к примеру отсюда http://mirrors.pdp-11.ru/_vms/ftp.usa.hp.com/VAX/
нарезаем на CD и вставляем в привод VAXа

Код

>>> sh conf

KA47-A V1.4-38D-V4.2
08-00-2B-3C-30-0B
40MB

DEVNBR    DEVNAM           INFO
------    --------    --------------------------
     1         NVR    OK
     3          DZ    OK
     4       CACHE    OK
     5         MEM    OK
                      40MB = S0/1=8MB, S2/3=32MB, S4/5=0MB
     6         FPU    OK
     7          IT    OK
     8         SYS    OK
     9          NI    OK
    10        SCSI    OK
                      0-L0-ST15150 5-L0-MJ-5.16 5-L1-MJ-5.16 5-L2-MJ-5.16 5-L3-M
J-5.16 5-L4-MJ-5.16 6-INITR    
    12        COMM    OK
                      DSW41/42 2 CHANNEL V4.52-b9
    14       ASYNC    OK
                      DHW41/2 V1.6

>>> sh dev

  VMS/VMB      ADDR      DEVTYPE    NUMBYTES     RM/FX    WP    DEVNAM      REV
  -------      ----      -------    --------     -----    --    ------      ---
  ESA0         08-00-2B-3C-30-0B
  DKA0         A/0/0     DISK         4.29GB      FX            ST15150     0023
  DKA500       A/5/0     RODISK     547.37MB      RM      WP    MJ-5.16     1.02
  DKA501       A/5/1     RODISK      ......       RM      WP    MJ-5.16     1.02
  DKA502       A/5/2     RODISK      ......       RM      WP    MJ-5.16     1.02
  DKA503       A/5/3     RODISK      ......       RM      WP    MJ-5.16     1.02
  DKA504       A/5/4     RODISK      ......       RM      WP    MJ-5.16     1.02
..HostID..    A/6       INITR

CD-ROM у нас крутой японский CD-CHANGER на 5 дисков ;-)
сразу видно в каком установлен диск дистрибутива

[SuperMax]

И так - приступаем

Код

>>> boot dka500

-DKA500
%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)  04-JUN-2015 21:43

Configuring devices . . .

Available device  DKA0:                            device type SEAGATE ST15150N
Available device  DKA500:                          device type NAKAMICH MJ-5.16S
%BACKUP-I-IDENT, Stand-alone BACKUP T7.2; the date is  4-JUN-2015 21:44:43.26
$

система ждет команды BACKUP

Код

$ BACKUP/IMAGE DKA500:VMS073.B /SAVE DKA0:
%BACKUP-I-PROCDONE, operation completed.  Processing finished at  4-JUN-2015 21:
47:34.16
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: YES
%BACKUP-I-IDENT, Stand-alone BACKUP T7.2; the date is  4-JUN-2015 21:48:14.80
$

жмем кнопку останов

Код

?02 EXT HLT
  PC= 820F9BA1 PSL= 04C30000

а теперь грузимся уже с нашего винта

Код

>>> BOOT DKA0


-DKA0
%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: MicroVAX 3100-80
                 System device: DKX00 - _DKA0:
                   Free Blocks: 8301708
                      CPU type: 18-04

операционка определила конфигурацию

Код

* Please enter the date and time (DD-MMM-YYYY HH:MM) 04-JUN-2015 21:48
*********************************************************
%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   4-JUN-2015 21:48:16.39  %%%%%%%%%%%
Operator _OPA0: has been enabled, username SYSTEM

%SYSTEM-I-BOOTUPGRADE, security auditing disabled
%%%%%%%%%%%  OPCOM   4-JUN-2015 21:48:16.43  %%%%%%%%%%%
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   4-JUN-2015 21:48:17.44  %%%%%%%%%%%
Logfile has been initialized by operator _OPA0:
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1

%%%%%%%%%%%  OPCOM   4-JUN-2015 21:48:17.49  %%%%%%%%%%%
Operator status for operator SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12

%%%%%%%%%%%  OPCOM   4-JUN-2015 21:48:17.75  %%%%%%%%%%%
Message from user JOB_CONTROL
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;

%%%%%%%%%%%  OPCOM   4-JUN-2015 21:48:17.75  %%%%%%%%%%%
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   4-JUN-2015 21:48:21.08  %%%%%%%%%%%
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...

%SET-I-INTSET, login interactive limit = 1, current interactive value = 0
%SET-I-INTSET, login interactive limit = 0, current interactive value = 0
%SYSGEN-W-OPENIN, error opening SYS$COMMON:[SYSEXE]ZTDRIVER.EXE; as input
%SYSGEN-E-FNF, file not found

    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]: VMSSYS73

система запросила имя тома - я ввел VMSSYS73