[Digital logo]
[HR]

OpenVMS Alpha Version 7.1
Upgrade and Installation Manual


Previous | Contents

Note: It it also possible to back up your running system disk by using the qualifier /IGNORE=INTERLOCK with the BACKUP command and ignoring warning messages. However, that method requires that all other use of the system be suspended, including disabling logins, stopping print and batch queues, and turning off networking software. In addition, you cannot use this method to restore files to the running system disk. Because of these limitations, Digital recommends that if you must use an alternate method to back up or restore the system disk, you use the method described in this section.

B.4.1 Preparing an Alternate Disk

Prepare an alternate disk as follows:

  1. Log in to a privileged account on your running OpenVMS Alpha system.
  2. Using the SHOW DEVICE command, identify a data disk on which you can install the operating system, with no options. This will be your target disk during that installation. Note the following:
  3. The target disk must be mounted privately to your process. (This prevents other users from accessing this disk during the installation and backup procedures.) Therefore, if the target disk was mounted with /SYSTEM, /CLUSTER, /GROUP, or /SHARE, dismount that disk and mount it without using those qualifiers or the /FOREIGN qualifier. For example:
    $ MOUNT/OVERRIDE=IDENTIFICATION DKA200 
    
  4. Enter the following command to install the OpenVMS Alpha operating system, with no options, on the target disk:
    $ @SYS$SYSTEM:AXPVMS$PCSI_INSTALL_MIN.COM [target-disk]
    

    (The procedure will prompt you for a device name if you do not specify it on the command line.)
  5. As the procedure completes the installation, the display is similar to the following:
    *** DEC AXPVMS VMS V7.1: VMS Operating System, Version V7.1 
     
        COPYRIGHT © (c) 21-NOV-1996 -- All rights reserved 
     
        Digital Equipment Corporation 
     
    %PCSIUI-I-DONEASK, execution phase starting 
    The following product will be installed: 
    DEC AXPVMS VMS V7.1 
    %PCSI-I-VOLINFO, estimated space information for volume DISK$MINAlpha 
    -PCSI-I-VOLSPC, -1 required; 741063 available; 741064 net 
    Portion Done: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% 
    The following product has been installed: 
    DEC AXPVMS VMS V7.1 
        . 
        . 
        . 
        The installation of minimum OpenVMS Alpha is now complete. 
     
        Use the following command to boot minimum OpenVMS: 
     
            BOOT -FLAGS E,O <device-name> 
     
        (Your system may require additional parameters to boot.) 
    

    Caution: If your system is a cluster member, Digital recommends that you shut down the entire OpenVMS Cluster system before you back up your system disk. This will prevent you from creating a partitioned cluster and from jeopardizing the integrity of your data in any other way.

    B.4.2 Using the Alternate Disk

    Use the alternate disk (on which you installed the operating system with no options) to perform backup and restore operations as follows:

    1. Shut down your system.
    2. Boot the alternate disk from the SYSE root. For example:
      >>> BOOT -FLAGS E,0 DKA200
      

      The system automatically logs you in to the SYSTEM account and then displays a triple dollar sign prompt ($$$).
      Note: During the boot and login operations on this minimum version of the operating system, you can ignore license messages that are similar to the following:
      %LICENSE-I-NOLICENSE, no license is active for this software product 
      
    3. If your system disk is shadowed, install and load a Volume Shadowing license on this data disk. You will then be able to back up the shadowed system disk from this data disk without disabling the shadow set.
      Note: Digital recommends that you do not install any other licenses, including OpenVMS licenses, on this alternate system. You will be able to use the system only from the console.
    4. Mount the system disk and any output devices you plan to use during the backup or restore operations.
    5. Perform the necessary backup and restore operations by entering the appropriate BACKUP commands.
    6. Shut down the system.
    7. Boot from your original system disk.


    Appendix C
    License Management Supplement

    This appendix contains information that supplements the license instructions in this manual and in the OpenVMS License Management Utility Manual.

    After you install the OpenVMS Alpha operating system, you must register OpenVMS Alpha licenses, which let you use the OpenVMS Alpha operating system. You must also register the licenses for the OpenVMS Alpha layered products you have purchased, such as DECnet for OpenVMS. (Note that after an upgrade, however, you do not have to reregister licenses for the OpenVMS Alpha operating system or for the layered products.) To register a license, you need to obtain a Product Authorization Key (PAK). A PAK is a printed document provided by Digital that contains the appropriate information to authorize access to software on an Alpha computer (or in an OpenVMS Cluster environment). You can obtain a PAK from a Digital support representative in the same way as you obtain software.

    C.1 Using the License Unit Requirement Table (LURT)

    Many PAKs contain a table name in the availability or activity fields. This name refers to a column in the License Unit Requirement Table (LURT), which is shown in Table C-1. Column A in the LURT indicates the number of license units required for each processor listed in the System Marketing Model column. Column H refers to layered products you may choose to register as well. For example, if your PAK specifies availability = A, you would require 50 license units to load the license on a DEC 3000 Alpha Model 500 series computer, or 500 license units to load the license on a DEC 7000 Alpha Model 610 computer.

    Note that some PAKs specify MOD_UNITS in the options field. The MOD_UNITS option allows the system manager to use the DCL command LICENSE MODIFY/UNITS to temporarily increase the size of the PAK. This permits a product to be used, in certain emergency situations, on a processor larger than the processor size specified in the license. Check your license terms and conditions before modifying license units. Reset the PAK size to its original size after the emergency situation is resolved.

    Table C-1 License Unit Requirement Table (LURT)
    System Marketing Model A H
    ALPHAbook 1 12 1050
    AlphaServer 400 12 1050
    AlphaServer 1000, 1000A 15 1050
    AlphaServer 2000, 2000A (1 CPU) 400 1100
    AlphaServer 2000, 2000A (2 CPU) 500 1100
    AlphaServer 2100, 2100A (1 CPU) 400 1100
    AlphaServer 2100, 2100A (2 CPU) 500 1100
    AlphaServer 2100, 2100A (3 CPU) 600 1100
    AlphaServer 2100, 2100A (4 CPU) 700 1100
    AlphaServer 4100 (1 CPU) 400 1100
    AlphaServer 4100 (2 CPU) 500 1100
    AlphaServer 4100 (3 CPU) 600 1100
    AlphaServer 4100 (4 CPU) 700 1100
    AlphaServer 8200 (1 CPU) 2000 1150
    AlphaServer 8200 (2 CPU) 2100 1150
    AlphaServer 8200 (3 CPU) 2200 1150
    AlphaServer 8200 (4 CPU) 2300 1150
    AlphaServer 8200 (5 CPU) 2400 1150
    AlphaServer 8200 (6 CPU) 2500 1150
    AlphaServer 8400 (1 CPU) 2600 1150
    AlphaServer 8400 (2 CPU) 2700 1150
    AlphaServer 8400 (3 CPU) 2800 1150
    AlphaServer 8400 (4 CPU) 2900 1150
    AlphaServer 8400 (5 CPU) 3000 1150
    AlphaServer 8400 (6 CPU) 3100 1150
    AlphaServer 8400 (7 CPU) 3200 1150
    AlphaServer 8400 (8 CPU) 3300 1150
    AlphaServer 8400 (9 CPU) 3400 1150
    AlphaServer 8400 (10 CPU) 3500 1150
    AlphaServer 8400 (11 CPU) 2600 1150
    AlphaServer 8400 (12 CPU) 2600 1150
    AlphaStation 205, 250, 255, 500 12 1050
    AlphaStation 400 12 1050
    AlphaStation 600 12 1050
    DEC 2000-300/300S 12 1050
    DEC 2000-500/500S 12 1050
    DEC 3000-300 15 1050
    DEC 3000-300L 15 1050
    DEC 3000-400/400S 20 1050
    DEC 3000-600/600S 20 1050
    DEC 3000-500/500S 50 1100
    DEC 3000-500X 50 1100
    DEC 3000-800/800S 50 1100
    DEC 4000-610 300 1150
    DEC 4000-620 400 1200
    DEC 4000-710 300 1150
    DEC 4000-720 400 1200
    DEC 7000-610 500 1200
    DEC 7000-620 600 1250
    DEC 7000-630 700 1250
    DEC 7000-640 800 1250
    DEC 10000-610 800 1250
    DEC 10000-620 900 1300
    DEC 10000-630 1000 1300
    DEC 10000-640 1100 1300


    Key to License Type Codes and Values:

    C.2 License Management Facility (LMF) Notes

    The following list addresses some common concerns and questions regarding the License Management Facility (LMF). For full explanations of these issues, see the OpenVMS License Management Utility Manual.

    C.2.1 Restrictions

    Availability Product Authorization Keys (PAKs) are available for the OpenVMS Alpha operating system. An OpenVMS Alpha PAK is identified by the keyword ALPHA in the PAK's option field. Note the following restrictions:

    C.2.2 For More Information

    For additional license information, see the release notes and the OpenVMS License Management Utility Manual.


    Appendix D
    OpenVMS Alpha Hardware Release Notes

    This appendix contains release notes, restrictions, and related information about using the OpenVMS Alpha operating system on the following computers:

    This appendix also includes information about graphics support on Alpha computers.

    D.1 ALPHAbook 1 Notes

    The following sections contain release notes specific to the ALPHAbook 1 notebook computer.

    D.1.1 Using the SCSI_MODE Utility

    The OpenVMS Alpha operating system includes a generic SCSI_MODE utility that allows privileged users to modify a SCSI device's mode pages. By using this utility to enable automatic disk spindown, users can save approximately 2 watts of power. Because mode pages are saved on the disk drive, the state is saved across power cycles.

    The following example shows how to enable automatic SCSI disk spindown after a one minute timeout period. (To select a spindown time other than one minute, replace the 01 following the offset f with the desired number of minutes expressed as a 2-digit hexadecimal value.) This procedure is recommended for use only on the internal drive of the ALPHAbook 1 notebook computer. Note that the parameter values shown in this example apply only to DVAS-2810 devices. To identify the SCSI disk devices on your system, use the SHOW DEVICE/FULL DK command.

    $ define dcl$path sys$etc 
    $ scsi_mode -devnam dka0 -devtyp DVAS-2810 -offset f 01 -page 38 -mount -save 
    $! 
    $! Processing Page #38h 
    $! 
    $! Cur   00______ 04______ 08______ 0C______ 10______ 14______ 18______ 1C______ 
    $! 0000  11000008 001829D0 00000200 B80400B4 0000 
    $! 
    $! Chng  00______ 04______ 08______ 0C______ 10______ 14______ 18______ 1C______ 
    $! 0000  11000008 001829D0 00000200 B80400FF 0000 
    $! 
    $! Sel   00______ 04______ 08______ 0C______ 10______ 14______ 18______ 1C______ 
    $! 0000  00000008 001829D0 00000200 38040001 0000 
    $! Perform MODE SELECT to page 38h [y/n] ? y 
    

    D.1.2 Naming Serial Line Devices

    If an ALPHAbook 1 notebook computer is booted with the console environment variable set to graphics, the name of the serial line (COM1) will be different. On an ALPHAbook 1, the COM1 device is called TTA0.

    The COM1 device is controlled by SYS$YSDRIVER, instead of SYS$OPDRIVER.

    If the console is set to serial, the device is called OPA0.

    D.1.3 Graphics Display Modes

    The ALPHAbook 1 notebook computer contains a Western Digital 90C24A graphics controller displayed on a 10.4 inch active matrix Thin Film Transistor (TFT) display.

    Note that, if a video monitor (CRT) is connected, the DECwindows display server software (which automatically detects the presence of an attached video monitor) will set the resolution to 1024 x 768 and disable the TFT display. If the server determines that no monitor is connected, it will force the size to match the LCD (800 x 600) and disable the CRT outputs (which saves power when the computer is running on battery).

    D.1.4 Customizing the Graphics Display

    You can override the size selection by modifying the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM file.

    You can also modify other parameters by using the DCL command DEFINE/SYSTEM for the following logical names:

    D.1.5 Modifying DECterm Options

    In the DECterm Options pull-down dialog box, the Window, General, and Printer options cannot be modified because the dialog box is larger than the screen. As a workaround, Digital recommends setting the display server to a large virtual screen size mode, which will allow access to the dialog box. A future version of DECwindows Motif (post-V1.2--3) will add a scroll bar to these dialog boxes for easier access.

    D.1.6 UCX Configuration Procedure

    The UCX Version 4.0 configuration procedure (UCX$CONFIG.COM) has not yet been updated to include support for the new 3Com PCMCIA Ethernet adapter for the ALPHAbook 1. Therefore, before you run UCX$CONFIG.COM, enter the following command to manually inform UCX of the new Ethernet controller:

    $ UCX DEFINE COMMUNICATION_CONTROLLER EO /INTERNET_INTERFACE=O -
    _$  /TYPE=(ETHERNET,CLUSTER) /DESCRIPTION=PCMCIA_3COM
    

    Other implementations of TCP/IP for OpenVMS may have a similar problem. Check with your TCP/IP vendor about device support for the new Ethernet controller.

    D.1.7 PCMCIA Bus Support

    The following notes apply to the PCMCIA bus.

    Supported PCMCIA Cards

    OpenVMS support for the PCMCIA bus on the ALPHAbook 1 system is limited to the following cards:

    The OpenVMS operating system can configure a maximum of one Ethernet card and one FAX/Modem card.

    Hot Swapping PCMCIA Cards Not Supported

    Hot swapping (removing and replacing cards while the computer is running) PCMCIA cards is not supported. If a PCMCIA card is inserted or removed while the OpenVMS operating system is running, it could result in a system hang (the system is unresponsive) or a system crash. A future release of the OpenVMS operating system is expected to include support for hot swapping PCMCIA cards.

    PCMCIA Modem Setting

    The highest recommended baud rate for the Apex Data ClipperCom V.34 International Data/FAX Modem card is 9600. For access to the modem, Digital recommends that you use the following DCL and modem commands:

    $ SET TERM/PERM/SPEED=9600/ALT/MODEM TTB0: 
    $ SET HOST/DTE TTB0: 
    at*ncxx
    at&k6 
    at&s1 
    at\g1 
    at\q1 
    at\x1) 
    

    (Note that xx represents the country number; for example, the United States is 22. See the Apex Data ClipperCom V.34 documentation for a list of country numbers.)


    Previous | Next | Contents | [Home] | [Comments] | [Ordering info] | [Help]

    [HR]

      6486P009.HTM
      OSSG Documentation
       6-DEC-1996 10:35:21.10
    

    Copyright © Digital Equipment Corporation 1996. All Rights Reserved.

    Legal