KA655 и я

DEC Alpha, ARM, MIPS, PowerPC, SPARC, VAX, PDP-8 и другие устройства
Hunta
Advanced Member
Сообщения: 427
Зарегистрирован: 31.08.2020,21:16
Откуда: Самара

KA655 и я

Сообщение Hunta » 24.03.2021,15:37

Запустил ещё одну процессорную плату VAX. В зависимости от того, где она использовалась, это могли быть MicroVAX 3800, MicroVAX 3900 или MicroVAX III+. Крайне полезным для запуска оказался конвертер SCSI-IDE, купленный здесь же, на фантомах. Ну и просто неоценимым - контроллер MSCP, видимый снаружи как SCSI :)

На PC iso образ дистрибутива был сброшен на CF, затем средствами контроллера карты была разбита на два раздела и теперь видна в системе как два диска. Поскольку VMS я хочу поставить на нулевой диска (ака DUA0: ), первое моё действие - скопировать дистрибутив с DUA0 на DUA1, что, собственно, сейчас и делается.

Код: Выделить всё

KA655-A 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.
>>>U
>>>I

>>>D/P/W 20001F40 20
>>>D/L 20088008 80000002
>>>D/W 2000146A A72E
>>>D * 100
>>>S 400


SCSI UTILITY PROGRAM V2.0

SELECT CSR ADDRESS

1 = 772150     A = 774500
2 = 760334     B = 760404
3 = 760354     C = 760444
4 = 760374     D = 760504
5 = 760340     E = 760544
6 = 760344     F = 760410
7 = 760350     G = 760450
8 = 760360     H = 760454

WHICH CSR # 1


SCSI HOST ADAPTER UTILITY  (REV. B2L-00 )

   X = UTILITY EXIT
   D = DIAGNOSTICS TEST

[ DISK ]                            : [ TAPE ]
   1 = LOGICAL UNIT NUMBER OFFSET   :    6 = LOGICAL UNIT NUMBER OFFSET
   2 = FORMAT DRIVE                 :    7 = ADDITIONAL UTILITIES
   3 = QUALIFY DRIVE                :
   4 = MANUALLY REPLACE BAD BLOCKS  :
   5 = ADDITIONAL UTILITIES         :

SELECT OPTION ?   5

ADDITIONAL UTILITIES  (REV. B2L-00 )        SN = 3674

   D = DISPLAY SCSI DEVICE & SETUP CONFIGURATION
   S = SEND SCSI COMMAND TO THE DEVICE
   T = TEST SCSI DEVICE
   R = FORMAT RCT BLOCK

SELECT OPTION ?  D

CURRENT CONFIGURATION :

DEV0: DU0  SCSI ID 0  LUN 0
      Disc ON,Sync ON,PMR ON,WWV OFF,Tag-Q OFF,RCT OFF,RA OFF,
DEV1: DU1  SCSI ID 0  LUN 0
      Disc ON,Sync ON,PMR ON,WWV OFF,Tag-Q OFF,RCT OFF,RA OFF,
DEV2: DU2  SCSI ID 1  LUN 0
      Disc OFF,Sync OFF,PMR OFF,WWV OFF,Tag-Q OFF,RCT OFF,RA OFF,
DEV3  NOT AVAILABLE
DEV4  NOT AVAILABLE
DEV5  NOT AVAILABLE
DEV6  NOT AVAILABLE
DEV7  SCSI ID 7  HOST ADAPTER, SCSI Reset ON,Density Mode ON,Default Tape OFF,
      Rew/Im OFF,Eject Disk ON,Truncate Size OFF,RCT size= OFF,RA dev= DEF,
      Rsv/Rls Option ON,MSCP credit = 22,sync rate = 10 MB/sec,
      RSX FP OFF,Sel Timeout = 250 ms
      (PMR=Prevent Medium Removal   WWV=Write W/Verify)
CHANGE CONFIGURATION ? (Y/N) Y
 R = Toggle SCSI Reset,      M = Toggle Density Mode
 D = Toggle Disconnect,      B = Toggle Buffer/Truncate Mode
 S = Toggle Sync/Async,      W = Toggle Density/Write Verify Mode
 C = Reconfigure Device,     P = Toggle Prevent Medium Removal
 A = Set the RA number,      1 = Toggle device RA
 E = Eject after Dismount    2 = Toggle device RCT
 G = Toggle RSX w/floppy
 J = Change Selection Timeout Period
 K = Toggle Host/Target Queue Mode
 L = Reserve/Release Disk
 Q = Allow Rewind w/No-Wait
 T = Reset All Device
 U = Toggle Default Tape
 V = Truncate for Volume Shadowing
 Y = Set the RCT size
 Z = Reset Controller
    ( Hit <return> key to exit )

SELECT OPTION ?  C

 Enter MSCP credit limit
 1 =  22 credits
 2 =  16 credits
 Enter  1

 Enter synchronous transfer rate (MB/sec)
 Enter (4 - 10) 10
 Number of Disks ? (0 - 7)  2
 DU0  to be Reconfigured ? (Y/N)Y
 DU0  SCSI ID ? (0 - 7)  0
 DU0  LUN ? (0 - 7)
 Number of Partitions ? (None,2,4) N2
Number of Tapes ? (0 - 5)
DEV0: DU0  SCSI ID 0  LUN 0
      Disc ON,Sync ON,PMR ON,WWV OFF,Tag-Q OFF,RCT OFF,RA OFF,
DEV1: DU1  SCSI ID 0  LUN 0
      Disc ON,Sync ON,PMR ON,WWV OFF,Tag-Q OFF,RCT OFF,RA OFF,
DEV2  NOT AVAILABLE
DEV3  NOT AVAILABLE
DEV4  NOT AVAILABLE
DEV5  NOT AVAILABLE
DEV6  NOT AVAILABLE
DEV7  SCSI ID 7  HOST ADAPTER, SCSI Reset ON,Density Mode ON,Default Tape OFF,
      Rew/Im OFF,Eject Disk ON,Truncate Size OFF,RCT size= OFF,RA dev= DEF,
      Rsv/Rls Option ON,MSCP credit = 22,sync rate = 10 MB/sec,
      RSX FP OFF,Sel Timeout = 250 ms
      (PMR=Prevent Medium Removal   WWV=Write W/Verify)
CHANGE CONFIGURATION ? (Y/N)

SCANNING SCSI DEVICES ATTACHED ...

DEV0: DU0  SCSI ID 0  LUN 0  ATA     CF       CARD   2014
      Disc ON,Sync ON,PMR ON,WWV OFF,Tag-Q OFF,RCT OFF,RA OFF,
DEV1: DU1  SCSI ID 0  LUN 0  ATA     CF       CARD   2014
      Disc ON,Sync ON,PMR ON,WWV OFF,Tag-Q OFF,RCT OFF,RA OFF,
DEV2  NOT AVAILABLE
DEV3  NOT AVAILABLE
DEV4  NOT AVAILABLE
DEV5  NOT AVAILABLE
DEV6  NOT AVAILABLE
DEV7  SCSI ID 7  HOST ADAPTER, SCSI Reset ON,Density Mode ON,Default Tape OFF,
      Rew/Im OFF,Eject Disk ON,Truncate Size OFF,RCT size= OFF,RA dev= DEF,
      Rsv/Rls Option ON,MSCP credit = 22,sync rate = 10 MB/sec,
      RSX FP OFF,Sel Timeout = 250 ms
      (PMR=Prevent Medium Removal   WWV=Write W/Verify)
CHANGE CONFIGURATION ? (Y/N)

ADDITIONAL UTILITIES  (REV. B2L-00 )        SN = 3674

   D = DISPLAY SCSI DEVICE & SETUP CONFIGURATION
   S = SEND SCSI COMMAND TO THE DEVICE
   T = TEST SCSI DEVICE
   R = FORMAT RCT BLOCK

SELECT OPTION ?
?02 EXT HLT
        PC = 000005C9
Failure.
>>>
>>>SHO DEV
UQSSP Disk Controller 0 (772150)
-DUA0 (RA90)
-DUA1 (RA90)

Ethernet Adapter 0 (774440)
-XQA0 (08-00-2B-0E-EE-87)
>>>BOO DUA0
(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-W-SYSBOOT Can not map PAGEFILE.SYS on the System Disk
   OpenVMS (TM) VAX Version V6.2     Major version id = 1 Minor version id = 0

PLEASE ENTER DATE AND TIME (DD-MMM-YYYY  HH:MM)  24-MAR-2021 18\8\7:26

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 RA90
Available device  DUA1:                            device type RA90

Enter "YES" when all needed devices are available: YES
%BACKUP-I-IDENT, Stand-alone BACKUP V6.2; the date is 24-MAR-2021 17:27:55.26
$ BACKUP/PHYSICAL DUA0: DUA1:
После окончание сего процесса сделаю установку и тоже выложу лог

Hunta
Advanced Member
Сообщения: 427
Зарегистрирован: 31.08.2020,21:16
Откуда: Самара

KA655 и я

Сообщение Hunta » 24.03.2021,16:50

Ну, не особо интересно...

Код: Выделить всё

%BACKUP-I-IDENT, Stand-alone BACKUP V6.2; the date is 24-MAR-2021 18:10:00.16
$
$
?02 EXT HLT
        PC = 81B4A15B
>>>
>>>BOO DUA1
(BOOT/R5:0 DUA1)



  2..
-DUA1
  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 V6.2     Major version id = 1 Minor version id = 0

PLEASE ENTER DATE AND TIME (DD-MMM-YYYY  HH:MM)
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY  HH:MM)  24-MAR-2021 18:10

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 RA90
Available device  DUA1:                            device type RA90

Enter "YES" when all needed devices are available: YES
%BACKUP-I-IDENT, Stand-alone BACKUP V6.2; the date is 24-MAR-2021 18:12:34.04
$ BACKUP/IMAGE DUA1:VMS062.B/SAVE_SET DU0:
%BACKUP-I-PROCDONE, operation completed.  Processing finished at 24-MAR-2021 18:
14:25.21
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 V6.2; the date is 24-MAR-2021 18:14:33.43
$
?02 EXT HLT
        PC = 81B4A14D
>>>BOO DUA0
(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
   OpenVMS (TM) VAX Version BI62-I06 Major version id = 1 Minor version id = 0


                OpenVMS VAX V6.2 Installation Procedure

                         Model: MicroVAX 3900 Series
                 System device: RA90 - _DUA0:
                   Free Blocks: 3866052
                      CPU type: 10-01



* Please enter the date and time (DD-MMM-YYYY HH:MM) 240MA\AM0\-MAR-2021 18:15
On MIN or UPGRADE system startup - CLUE is not run.
%%%%%%%%%%%  OPCOM  24-MAR-2021 18:15:06.05  %%%%%%%%%%%
Operator _OPA0: has been enabled, username SYSTEM

%%%%%%%%%%%  OPCOM  24-MAR-2021 18:15:06.07  %%%%%%%%%%%
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  24-MAR-2021 18:15:06.36  %%%%%%%%%%%
Logfile has been initialized by operator _OPA0:
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1

%%%%%%%%%%%  OPCOM  24-MAR-2021 18:15:06.37  %%%%%%%%%%%
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  24-MAR-2021 18:15:07.35  %%%%%%%%%%%
Message from user JOB_CONTROL
%JBC-E-OPENERR, error opening SYS$SYSROOT:[SYSEXE]QMAN$MASTER.DAT;

%%%%%%%%%%%  OPCOM  24-MAR-2021 18:15:07.36  %%%%%%%%%%%
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  24-MAR-2021 18:15:11.16  %%%%%%%%%%%
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 OpenVMS062, press RETURN in response
    to the next question.

* Enter the volume label for this system disk [OpenVMS062]: TEST

* Enter name of drive holding the OpenVMS distribution media: DUA1:
* Is the OpenVMS media ready to be mounted? [N] Y
%MOUNT-I-MOUNTED, VAXVMS062    mounted on _DUA1:

    Select optional software you want to install.  You can install one
    or more of the following OpenVMS or DECwindows components:

    o OpenVMS library                              -  43500 blocks
    o OpenVMS optional                             -  19100 blocks
    o OpenVMS Help Message                         -   8400 blocks
    o Text versions of three OpenVMS manuals       -   4650 blocks
    o DECwindows workstation support               -  25750 blocks
    o DECwindows base support                      -   3600 blocks
    o OpenVMS Management Station                   -   5900 blocks

    Space remaining on system disk:  3865872 blocks

* Do you want to install the OpenVMS library files? (Y/N) Y

    Space remaining on system disk:  3822372 blocks

* Do you want to install the OpenVMS optional files? (Y/N) Y

    Space remaining on system disk:  3803272 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 create the installation media
    for the PC client software.  If you want to use the OpenVMS Management
    Station, you must install these files on at least one OpenVMS system to
    create the installation media, which can then be used to install the
    PC client on one or more PCs.

    Note: To use the OpenVMS Management Station on your PC, you must be
    running Digital's PATHWORKS V5.0A for DOS and Windows (or V5.1)
    software.

    The OpenVMS Management Station optional files consume approximately 5900
    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:  3797372 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 8400 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:  3788972 blocks


    You have the choice of installing text versions of one or more OpenVMS
    manuals.

    o OpenVMS Master Index                       -   3700 blocks
    o OpenVMS Glossary                           -    650 blocks
    o Overview of OpenVMS Documentation          -    300 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:  3784322 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.2.

* Do you want to provide optional DECwindows support? (Y/N) Y
* Do you want to install DECwindows workstation support? (Y/N) Y

    Space remaining:  3759972 blocks


    You elected to install DECwindows workstation support, you
    automatically get the following installed:

        - DECwindows workstation support
        - DECwindows base support
        - 75 dots per inch video fonts

    All DECwindows applications run with 75 dots per inch video fonts.
    By default, most systems startup with 75 dots per inch video fonts.
    You have the option of installing 100 dots per inch video fonts,
    which certain applications can take advantage of.

    For the VAXstation 4000 series machines, 100 dots per inch video fonts
    are used by default.  If you decide not to install 100 dots per inch
    video fonts, you must edit SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM
    to force 75 dots per inch video fonts to be the default.  Otherwise,
    certain applications may not space text properly.

    For instructions on how to configure your system with both 75 and 100
    dots per inch video fonts, see the installation guide or look at the
    template command procedure SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE.

* Do you want 100 dots per inch video fonts installed? (Y/N) Y

    Space remaining:  3754972 blocks


    The following options will be provided:

        OpenVMS library
        OpenVMS optional
        OpenVMS Help Message
        OpenVMS Master Index
        OpenVMS Glossary
        Overview of OpenVMS Documentation
        OpenVMS Management Station Software -- PC files
        DECwindows workstation support with:
            -  DECwindows base support
            -  75 dots per inch video fonts
            - 100 dots per inch video fonts

    Space remaining on system disk:  3754972 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

    Restoring OpenVMS Management Station Software -- PC files
%BACKUP-I-STARTVERIFY, starting verification pass

    You can now remove the OpenVMS distribution kit from DUA1:.


    Load the DECwindows distribution kit.


* Enter name of drive holding the DECwindows distribution media: DUA1l\l\:
* Is the DECwindows media ready to be mounted? [N] Y
%MOUNT-I-MOUNTED, VAXVMS062    mounted on _DUA1:

    Restoring DECwindows base support save set ...
%BACKUP-I-STARTVERIFY, starting verification pass

    Restoring DECwindows workstation support save set ...
%BACKUP-I-STARTVERIFY, starting verification pass

    Restoring DECwindows 75 dots per inch video fonts save set ...
%BACKUP-I-STARTVERIFY, starting verification pass

    Restoring DECwindows 100 dots per inch video fonts save set ...
%BACKUP-I-STARTVERIFY, starting verification pass

    You can now remove the DECwindows distribution kit from DUA1:.



    Creating [VMS$COMMON] directory tree ...


    In a cluster, you can run multiple systems sharing all files except
    PAGEFILE.SYS, SWAPFILE.SYS, SYSDUMP.DMP, and VAXVMSSYS.PAR.

* Will this node be a cluster member? (Y/N) N

* Do you want DECwindows Motif as the default windowing system? (Y/N) Y

    Now we will ask you for new passwords for the following accounts:

        SYSTEM, SYSTEST, FIELD

    Passwords must be a minimum of 8 characters in length.  All passwords
    will be checked and verified.  Any passwords that can be guessed easily
    will not be accepted.


* Enter password for SYSTEM:
* 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 data
base
%UAF-I-RDBADDMSGU, identifier FIELD value [000001,000010] added to rights databa
se
%UAF-I-RDBADDMSGU, identifier SYSTEM value [000001,000004] added to rights datab
ase
%UAF-I-RDBADDMSGU, identifier SYSTEST value [000001,000007] added to rights data
base
%UAF-E-RDBADDERRU, unable to add SYSTEST_CLIG value [000001,000007] to rights da
tabase
-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: TEST

* 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 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.2 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): 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.

********************************************************************************

    Now registering the OpenVMS operating system in the
    POLYCENTER Software Installation product database

The following product will be registered:
DEC VAXVMS VMS V6.2
The following product has been registered:
DEC VAXVMS VMS V6.2

********************************************************************************


    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

%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   18:40:44
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
?06 HLT INST
        PC = 822C07C5
Loading system software.
No default boot device has been specified.

Available devices.
-DUA0 (RA90)
-DUA1 (RA90)
-XQA0 (08-00-2B-0E-EE-87)

Device? [XQA0]: DUA0

(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
   OpenVMS (TM) VAX Version V6.2     Major version id = 1 Minor version id = 0


    *****************************************************************

    OpenVMS VAX V6.2

    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 24-MAR-2021 18:41:56.31
%DCL-S-SPAWNED, process SYSTEM_1 spawned
%%%%%%%%%%%  OPCOM  24-MAR-2021 18:42:17.40  %%%%%%%%%%%
Operator _TEST$OPA0: has been enabled, username SYSTEM

%%%%%%%%%%%  OPCOM  24-MAR-2021 18:42:17.43  %%%%%%%%%%%
Operator status for operator _TEST$OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12

%%%%%%%%%%%  OPCOM  24-MAR-2021 18:42:17.50  %%%%%%%%%%%
Logfile has been initialized by operator _TEST$OPA0:
Logfile is TEST::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1

%%%%%%%%%%%  OPCOM  24-MAR-2021 18:42:17.51  %%%%%%%%%%%
Operator status for operator TEST::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

%SET-I-NEWAUDSRV, identification of new audit server process is 0000010A
%%%%%%%%%%%  OPCOM  24-MAR-2021 18:42:18.35  %%%%%%%%%%%
Message from user AUDIT$SERVER on TEST
%AUDSRV-I-NEWSERVERDB, new audit server database created

%%%%%%%%%%%  OPCOM  24-MAR-2021 18:42:18.56  %%%%%%%%%%%
Message from user AUDIT$SERVER on TEST
%AUDSRV-I-REMENABLED, resource monitoring enabled for journal SECURITY

%%%%%%%%%%%  OPCOM  24-MAR-2021 18:42:18.74  %%%%%%%%%%%
Message from user AUDIT$SERVER on TEST
%AUDSRV-I-NEWOBJECTDB, new object database created

%%%%%%%%%%%  OPCOM  24-MAR-2021 18:42:19.57  %%%%%%%%%%%
Message from user JOB_CONTROL on TEST
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;

%%%%%%%%%%%  OPCOM  24-MAR-2021 18:42:19.59  %%%%%%%%%%%
Message from user JOB_CONTROL on TEST
-RMS-E-FNF, file not found

%LICENSE-F-EMTLDB, license database contains no license records
%%%%%%%%%%%  OPCOM  24-MAR-2021 18:42:21.63  %%%%%%%%%%%
Message from user SYSTEM on TEST
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found

%%%%%%%%%%%  OPCOM  24-MAR-2021 18:42:21.70  %%%%%%%%%%%
Message from user SYSTEM on TEST
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found

%%%%%%%%%%%  OPCOM  24-MAR-2021 18:42:21.74  %%%%%%%%%%%
Message from user SYSTEM on TEST
%SECSRV-I-SERVERSTARTINGU, security server starting up

%%%%%%%%%%%  OPCOM  24-MAR-2021 18:42:21.92  %%%%%%%%%%%
Message from user SYSTEM on TEST
%SECSRV-I-CIASTARTINGUP, breakin detection and evasion processing now starting u
p

%%%%%%%%%%%  OPCOM  24-MAR-2021 18:42:23.17  %%%%%%%%%%%
Message from user SYSTEM on TEST
%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  24-MAR-2021 18:42:24.32  %%%%%%%%%%%
Message from user SYSTEM on TEST
Warning: DECdtm log file not found (SYS$JOURNAL:SYSTEM$TEST.LM$JOURNAL)
        %RMS-E-FNF, file not found
        TP server process waiting


%%%%%%%%%%%  OPCOM  24-MAR-2021 18:42:25.36  %%%%%%%%%%%
Message from user AUDIT$SERVER on TEST
Security alarm (SECURITY) and security audit (SECURITY) on TEST, system id: 1025
Auditable event:          Audit server starting up
Event time:               24-MAR-2021 18:42:25.15
PID:                      00000103
Username:                 SYSTEM

%%%%%%%%%%%  OPCOM  24-MAR-2021 18:42:26.16  %%%%%%%%%%%
Message from user AUDIT$SERVER on TEST
Security alarm (SECURITY) and security audit (SECURITY) on TEST, system id: 1025
Auditable event:          Identifier added
Event time:               24-MAR-2021 18:42:26.11
PID:                      00000103
Process name:             STARTUP
Username:                 SYSTEM
Process owner:            [SYSTEM]
Image name:               TEST$DUA0:[SYS0.SYSCOMMON.][SYSEXE]AUTHORIZE.EXE
Identifier name:          SYS$NODE_TEST
Identifier value:         %X80010000
Attributes:               none

%UAF-I-RDBADDMSG, identifier SYS$NODE_TEST value %X80010000 added to rights data
base
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
  SYSTEM       job terminated at 24-MAR-2021 18:42:27.88

  Accounting information:
  Buffered I/O count:            1230         Peak working set size:     916
  Direct I/O count:               479         Peak page file size:      4324
  Page faults:                   5059         Mounted volumes:             0
  Charged CPU time:           0 00:00:26.26   Elapsed time:     0 00:00:36.73

        Welcome to OpenVMS VAX V6.2

Username: SYSTEM
Password:
%LICENSE-I-NOLICENSE, no license is active for this software product
%

Аватара пользователя
size_t
Advanced Member
Сообщения: 672
Зарегистрирован: 20.02.2019,14:28
Откуда: Санкт-Петербург
Контактная информация:

Вклад в сообщество

KA655 и я

Сообщение size_t » 24.03.2021,17:04

Hunta писал(а): 24.03.2021,15:37 контроллер MSCP, видимый снаружи как SCSI
А снаружи - это со стороны системной шины, или со стороны диска?
Я к чему - к MSCP можно как-то прицепить сказевые винты и убедить контроллер что это скази?
(я просто пытаюсь придумать применение контроллеру на 11/04)

Hunta
Advanced Member
Сообщения: 427
Зарегистрирован: 31.08.2020,21:16
Откуда: Самара

KA655 и я

Сообщение Hunta » 24.03.2021,17:25

size_t писал(а): 24.03.2021,17:04 А снаружи - это со стороны системной шины, или со стороны диска?
Я к чему - к MSCP можно как-то прицепить сказевые винты и убедить контроллер что это скази?
Честно говоря, что то я не помню, что бы где то попадалось про именно DEC-овский контроллер, но вот этот для PDP-11 и VAX-ов изнутри (со стороны шины) выглядит, как контроллер MSCP (и TMSCP), а снаружи (для устройств) - именно как контроллер SCSI-2. К нему я цеплял SCSI винты, CD-ROM-ы, а сейчас через конвертер SCSI-IDE подключены CF карты.
size_t писал(а): 24.03.2021,17:04 я просто пытаюсь придумать применение контроллеру на 11/04
Ну, мой вроде как не пойдёт. Если мне не изменяет память, 11/04 - это unibus, а мой контроллер под qbus. Но, и фирма моего контроллера и ещё парочка, которая выпускала такие контроллеры - делала вариант и под unibus.

И ещё, насчёт выпуска чего то похожего (внутри mscp, снаружи scsi) от DEC - они использовали в своих системах диски, которые SCSI, причём это были как бы DEC-овские винты (но часть из них делала точно не DEC)

И ещё. контроллеры RQDX1-2-3 - они тоже - внутри MSCP, а снаружи (нет, не SCSI) - МFM

Аватара пользователя
size_t
Advanced Member
Сообщения: 672
Зарегистрирован: 20.02.2019,14:28
Откуда: Санкт-Петербург
Контактная информация:

Вклад в сообщество

KA655 и я

Сообщение size_t » 24.03.2021,17:39

Не, не ваш. У меня же UD33, он MSCP, но насколько он похож по внешним интерфейсам...

Hunta
Advanced Member
Сообщения: 427
Зарегистрирован: 31.08.2020,21:16
Откуда: Самара

KA655 и я

Сообщение Hunta » 24.03.2021,17:54

А, да, вспомнил. Но он снаружи не SCSI. Похож на MFM (два кабеля), но... я не уверен :)

Hunta
Advanced Member
Сообщения: 427
Зарегистрирован: 31.08.2020,21:16
Откуда: Самара

KA655 и я

Сообщение Hunta » 27.03.2021,21:05

Пришлось повоевать, но...
Винды на ВАКСе
Уф... :)

lammer_3
Newbie
Сообщения: 9
Зарегистрирован: 09.04.2021,11:08
Откуда: СПб

KA655 и я

Сообщение lammer_3 » 12.04.2021,11:02

А в чём война то состояла? Правда, у меня никогда не было x-Windows. Да, если совсем честно, никогда не было и VAX вместе с VMS: перестройка закончилась буквально за пару-тройку месяцев до отгрузки ;)
Как я понимаю, включение Windows это часть генерации VMS? Не надо ничего доустанавливать...

Hunta
Advanced Member
Сообщения: 427
Зарегистрирован: 31.08.2020,21:16
Откуда: Самара

KA655 и я

Сообщение Hunta » 12.04.2021,11:24

lammer_3 писал(а): 12.04.2021,11:02 А в чём война то состояла?
Запустить X Window сервер на писюке. Причём такой, который смог бы взаимодействовать поверх telnet с VAX-ой
lammer_3 писал(а): 12.04.2021,11:02 включение Windows это часть генерации VMS? Не надо ничего доустанавливать...
И да и нет. Генерации как таковой (если сравнивать с, скажем, RSX) - нет. Есть восстановление системы с дистрибутива и выбор пакетов для установки и настройки. То есть - доустановка - да, есть

lammer_3
Newbie
Сообщения: 9
Зарегистрирован: 09.04.2021,11:08
Откуда: СПб

KA655 и я

Сообщение lammer_3 » 13.04.2021,10:08

И как же выглядит Ваша конфигурация по железу? Какой индекс у КА655? Сколько памяти? И где что в корзине?
Это принципиально для VMS - внешний сервер xWindows, а MicroVax только рабочая станция? Просто, по опыту RSX, любая (почти?) системная задача может исполняться на этом же процессоре, где и пользовательские - было бы место. Здесь так нельзя?
Правильно ли я понимаю, что КА655 ни в каком исполнении не будет работать в ВА23, ему нужно минимум ВА213?

Hunta
Advanced Member
Сообщения: 427
Зарегистрирован: 31.08.2020,21:16
Откуда: Самара

KA655 и я

Сообщение Hunta » 13.04.2021,10:28

lammer_3 писал(а): 13.04.2021,10:08 Правильно ли я понимаю, что КА655 ни в каком исполнении не будет работать в ВА23, ему нужно минимум ВА213?
Понятия не имею. У меня только корзина H9278-A и всё воткнуто в неё.
lammer_3 писал(а): 13.04.2021,10:08 И как же выглядит Ваша конфигурация по железу?
Плата проца, до двух плат памяти (если пара по 8 и пара по 16 мб), MSCP контроллер CQD-420, в него могу воткнуть SCSI винчестеры и CD-ROM, но обычно, через конвертер, подключены CF-ки. В принципе есть ещё платы с серийными портами и мультиплексор с ними же, но их втыкать не пробовал.
lammer_3 писал(а): 13.04.2021,10:08 Какой индекс у КА655?
Это что за зверь?
lammer_3 писал(а): 13.04.2021,10:08 Это принципиально для VMS - внешний сервер xWindows, а MicroVax только рабочая станция?
Нет. Если в системе есть поддерживаемая графическая карат - можно запустить и локальный X Window сервер. И - никакого (VAX-овского) кода там не выполняется - это чисто отрисовка картинки, то есть команды, можно сказать - графические
lammer_3 писал(а): 13.04.2021,10:08 росто, по опыту RSX, любая (почти?) системная задача может исполняться на этом же процессоре, где и пользовательские - было бы место.
Это Вы про что? PDP-11 можно считать однопроцессорной машиной, так что по любому всё выполняется на одном и том же процессоре. Да, были многопроцессорные, но единственная система, которая это поддерживает - RSX-11M-Plus, и там процессоре равноправные.

Ответить