OPENVMS Alpha Version 7.2 Upgrade

3/26/01

 

[OpenVMS] OpenVMS Alpha V7.2 Upgrade Checklist     Last Technical Review: 3-SEP-1999       Size: 694 lines

Any party granted access to the following copyrighted information (protected under Federal Copyright Laws), pursuant to a duly executed Compaq Service Agreement may, under the terms of such agreement copy all or selected portions of this information for internal use and distribution only. No other copying or distribution for any other purpose is authorized. Copyright(c) 1999 Compaq Computer Corporation   All rights reserved. Note:   The name of the OpenVMS AXP operating system has been changed to OpenVMS Alpha.  Any reference to OpenVMS AXP or AXP is synonymous with OpenVMS Alpha or Alpha.    

PRODUCT:    OpenVMS Alpha Version 7.2 COMPONENT:  Upgrade SOURCE:     Compaq Computer Corporation

This document contains information in a checklist format that is useful prior to performing an upgrade of this product. Included at the end of this document is a list of all source document references.   Please note that this document does not replace other installation or upgrade documents you may require. It is intended to supplement these documents and provide the most up-to-date upgrade information.   The following documentation can be found on the distribution CD-ROM located at [ALPHA072.DOCUMENTATION]: "OpenVMS Alpha Version7.2 Upgrade and Installation Manual" ,  "OpenVMS Version7.2 New Features Manual" , "OpenVMS Version7.2 Release Notes" The following Software Product Description can be found in the "SPD" text search database:   "SPD 25.01.55: OpenVMS Operating for Alpha and VAX, Version 7.2"  

 

  • -Operating System CD-ROM

  • -Required Firmware

  • -License Name: OpenVMS-ALPHA

  • -Hardware Prerequisites

  • -Software Prerequisites

  • -Disk Space Requirements

  • -Process Quotas

  • -SYSGEN Parameters

  • -Upgrade Time

  • -Other Pre-Installation Information

  • -Booting the Distribution CD from the Local Drive

  • -Booting the Distribution CD from the INFOSERVER

  • -Performing the Upgrade

  • -Post-Installation Information

  • -ECO/Remedial kits

  •  

  • check OPERATING SYSTEM CD-ROM:

  • Included in your kit is the OpenVMS Alpha operating system CD-ROM, which you use to install or upgrade the operating system, or to perform operations such as backing up the system disk.   OpenVMS Alpha assumes that all Alpha systems have either a local CD-ROM reader or INFOSERVER access to a CD-ROM reader.   Without CD-ROM access, it is possible to upgrade a target disk from an existing OpenVMS Alpha V7.2 operating system.   Refer to the "Upgrading from a Running System" section in the "OpenVMS Alpha Version 7.2 Upgrade and Installation Manual". This operation is building a basic system.

    The CD-ROM is labeled as follows:

          CD-ROM Label:             OpenVMS[TM] Alpha[TM]

                                                  Operating System V7.2

                                                  Software and Documentation

          Volume Label:                 ALPHA072

    NOTE:   The volume label is the machine-readable name that the OpenVMS Alpha operating system and InfoServer systems use to access the CD-ROM.

    To request your OpenVMS Alpha operating system CD from ITEC:

    Go to http://vc.itec.suny.edu/~gsoft/gsform.html .

    Enter your Remote License Manager account and password.

    Select CDROM Offerings, click on Submit Query.

    Select the box to the left of VMSAXP0721, click on Get_Software.

    At this time,  you can also order the firmware CD (FIMWARE57) thru ITEC, if it is needed-- See next paragraph.

    Ignore all the File Copy Preferences and click on Submit Query.

    Your CD order will be on it's way to your Campus thru the mail.

    up

  • check REQUIRED FIRMWARE:

  • If your computer console does not have a specific minimum version of the Privileged Architecture Library code (PALcode), you may not be able to boot your system during the upgrade procedure.   Refer to the "Firmware Revision Checking" section in the "OpenVMS Alpha Version 7.2 Upgrade and Installation Manual" for the minimum and supported PALcode versions.

    I.E. DEC 3000 Model 400:

             Required minimum version of PALcode is 5.56.

             Recommended minimum version of PALcode is 5.56.

    To determine the PALcode version refer to the "How to Find the Alpha PALcode Version While Running OpenVMS" article in the "OpenVMS" text search database.  

    To request your Firmware CD from ITEC, follow the same steps for ordering the system CD (above paragraph), except select the box next to FIMWARE57-Alpha sys Firmware update V 5.7.  Your CD will be sent thru the mail to your campus.

    up

  • check LICENSE NAME: OpenVMS-ALPHA

  • Check your OpenVMS Alpha and System Integrated Products (SIPs) licenses for a Release Date. If a date is listed and it is prior to January 1999, then you must replace the PAK in order for the product to work with OpenVMS Alpha V7.2. A PAK that has a release date should be replaced with a permanent PAK even if the release date is acceptable.  

    up

  • check HARDWARE PREREQUISITES:

  • The minimum amount of memory required to install, boot and log into an OpenVMS Alpha system is 64 MB. Refer to specific layered product documentation for other memory requirements.   Refer to "Systems Supported by OpenVMS Alpha and VAX Version 7.2" and Appendix A of the "OpenVMS Operating System for Alpha and VAX, Version 7.2 (SPD25.01.55)" to determine other hardware requirements.  

    up

  • check SOFTWARE PREREQUISITES:

  • To upgrade to OpenVMS Alpha Version 7.2, the system must be running a minimum of Version 6.1.  You can not upgrade from Version 1.5 to Version 7.2.  

    up

  • check DISK SPACE REQUIREMENTS:

  • File Category   Space Used Running Total
    Minimum OpenVMS Files   78 MB   78 MB
    Other OpenVMS Files  106 MB   184 MB
    DECwindows support   32 MB 216 MB
    Paging File (required)  38 MB  254 MB
    Swap File (suggested) 3 MB   257 MB
    Dump File (optional)  2 8 MB 285 MB
    Decompressed Help Files (optional) 15 MB   300 MB
    Full DECwindows MotifV1.2-5 (optional) 90 MB 390 MB
    Safeguard for upgrading  50 MB  440 MB

    The minimum OpenVMS files listed above are for a system configuration where all optional features have been declined during the initial installation.  For most applications, this is not a realistic OpenVMS environment.   The paging, swap, and dump file requirements above are the minimum for a system with 32 MB of main memory.  Additional memory in most cases adds to the space needed for these files, as will particular needs of your application.  With careful system management it is possible to use the paging file space as a temporary dump file. The maximum amount of disk space needed is 360,000 blocks, but your system might use substantially less.  Check for free disk space with the following command:

        $ SHOW DEVICE SYS$SYSDEVICE

    up

  • check PROCESS QUOTAS:

  • Set PGFLQUOTA to at least twice the size of the largest library being decompressed with SYS$UPDATE:LIBDECOMP.COM.   If PGFLQUOTA is low decompressing libraries could fail without any error message or with LIBRAR-E-INDEXERROR.

    I.E. STARLET.OLB is 26,290 blocks, so PGFLQUOTA would be set to at least 52,580.

           PROCESS PRIVILEGES:  None specified.

    up

  • check SYSGEN PARAMETERS:

  • For a concurrent upgrade, set these parameters as follows:

        EXPECTED VOTES = 1

        VOTES = 1

    up

  • check UPGRADE TIME:

  • 1.5 hours (DECpc AXP 150, 64 MB, RZ25L, DECwindows support)  

    (i.e. pre-upgrade, upgrade, options, IVP, post upgrade)

    up

  • check OTHER PRE-INSTALLATION INFORMATION:

  •  

  • check Review the layered product versions installed on your system for compatibility with OpenVMS Alpha Version 7.2.   For third-party layered product compatibility information, contact the appropriate vendor.  

  • up

  • check The OpenVMS Alpha Software Rollout Schedule can be accessed through the following web page:

  •   http://www.openvms.digital.com/openvms/OperatingSystem.html  

    up

    check The Spiralog file system will not work with OpenVMS Alpha Version 7.2.   It must be de-installed before upgrading to OpenVMS Alpha Version7.2  

    up

     

    check If your system boots from a shadowed system disk, prepare a non-shadowed system disk for the upgrade.  Refer to the “Volume Shadowing for OpenVMS" section titled "Upgrading the OpenVMS Operating System on a System Disk Shadow Set".  

    up

     

  • check On an OpenVMS system disk, the file [SYSx]SYSCOMMON.DIR is an alias directory of the file [000000]VMS$COMMON.DIR.  This means that both files point to the same file header.  Prior to OpenVMS AXP Version 1.5,BACKUP did not properly restore the VMS$COMMON.DIR file and[000000]VMS$COMMON.DIR becomes the alias directory for [SYSx]SYSCOMMON.DIR.  This might produce errors with DCL commands and lexical functions.

  • OpenVMS AXP Version1.5 corrected this problem.  However, if you  restored image backups created with a previous OpenVMS version,  the problem recurred.  If the OpenVMS Alpha operating system has been upgraded to V6.1or later, it is unlikely that your system disk has this problem.  To check for incorrect file specifications, enter the following command:

                $ SHOW DEVICE/FILES SYS$SYSDEVICE

      The correct file specification should be:

                ddcu:[VMS$COMMON.subdirectory]filename

      The incorrect file specification is of the form:

               ddcu:[SYSCOMMON.subdirectory]filename

    If the file specification is incorrect, correct the problem according to one of the following articles in the "OpenVMS" text search database:

               "Checking the Alias Directory Structure on the System Disk"

                "Incorrect File Specs Returned After BACKUP/IMAGE Restore"  

    up

  • check Ensure that each root, SYSx, in SYS$SYSDEVICE:[000000] is valid, where x is a hexadecimal digit in the range 1 through 9 or A through D (for example, SYS1 or SYSA).   For satellite nodes, x must be in the range from 10 to FFFF.

  • Also each root must have a SYSCOMMON.DIR and it must have the same "File ID" as VMS$COMMON.DIR in SYS$SYSDEVICE:[000000]. To check the "File ID" enter the following commands using the correct root and compare the "File ID" to the VMS$COMMON.DIR "File ID":

                 $ dir sys$sysdevice:[sys4]syscommon.dir/full

                 $ dir sys$sysdevice:[000000]vms*.dir/full

    up

  • check Perform a backup of the system disk by booting the ALPHA072 CD-ROM and using menu option 7.  Refer to Appendix B, "Backing Up and Restoring the System Disk", in the "OpenVMS Alpha Version 7.2 Upgrade and Installation Manual".  

  •  Backup the System Disk
      1. Shutdown the system
      2. Boot the operating system CD-ROM
      3. Use the menu to enter the DCL environment (option 4)
      4. Mount the system disk and the target device on which you will make the backup copy
      5. Enter backup command:

    $ BACKUP/IMAGE [source disk] [destination disk]

      1. Log out from the DCL environment
      2. Shut down the system by selecting option 5 from the menu
      3. Boot from the system disk

    up

  • check Analyze the system and repair errors with the following commands:  

  •  

  •  

             $ Analyze/disk system disk

              $ Analyze/disk repair

  • or

  • $ Diagnose   

    Type $Help Diagnose for additional information about the Diagnose command.

    up

  • check Verify AUTOGEN feedback data using this DCL command:

  • $@SYS$UPDATE:AUTOGEN GETDATA TESTFILES

    If feedback data is invalid and the system has been up longer than 24 hours, generate new feedback data using the following   DCL command:

    $@SYS$UPDATE:AUTOGEN SAVPARAMS SAVPARAMS

    WARNING:   AUTOGEN will be run during the upgrade. Page and swap files may be resized.  Adding the entries PAGEFILE=0, SWAPFILE=0, DUMPFILE=0 to SYS$SYSTEM:MODPARAMS.DAT will prevent AUTOGEN   from resizing these files.

    If you use AGEN$INCLUDE in SYS$SYSTEM:MODPARAMS.DAT to include file(s) containing additional parameter settings, and the files which are being included are not on the system disk, the files should be moved to the system disk and the AGEN$INCLUDE entry updated to reflect the new location.

    More information on using AUTOGEN and making adjustments to MODPARAMS.DAT may be found in the "OpenVMS System Manager's Manual" or in the "How To Use AUTOGEN For The First Time" article in the "OpenVMS" text search database.

    NOTE: The upgrade procedure may not complete when the page file has been renamed.  Please review the following article:

    PAGEFILE3_CURSIZE Returned While Upgrading To OpenVMS Alpha v7.2  

    up

    check Check for the existence of the logical name SYSUAF. If this logical is defined and it points to a SYSUAF.DAT file in any location other than SYS$SYSTEM, copy the file to SYS$SYSTEM for use during the upgrade.

    up

     

  • check Check for the existence of files that might interfere with the upgrade in the SYS$SPECIFIC directories for all nodes that boot from the system disk.

  • I.E. SYS$LIBRARY:DCLTABLES.EXE

    SYS$SYSTEM:DCL.EXE  

    up

    check If the system disk contains a shared dump file it must not be named SYS$COMMON:[SYSEXE]SYSDUMP.DMP.  The recommended file name for a shared dump file is SYS$COMMON:[SYSEXE]SYSDUMP-COMMON.DMP.  

    up

    check If upgrading a standalone system, shutdown the system.  

    up

    check If performing a concurrent upgrade, shut down the entire cluster and upgrade each system disk.  No one can use the cluster until you upgrade each system disk and reboot each Alpha computer.  

    up

    check If performing rolling upgrade, refer to the "Rolling Upgrade" section of the "OpenVMS Alpha Version 7.2 Upgrade   and Installation Guide".  

    up

  • check Enable auto boot, to boot the system automatically after the halt command.

  • I.E. At the console prompt (>>>) on a DECpc AXP 150, enter the following command:

                 >>> SET AUTO_ACTION BOOT  

    up

  • check BOOTING THE DISTRIBUTION CD FROM THE LOCAL DRIVE:

  • At the console prompt (>>>), enter the SHOW DEVICE command to identify the device name of the CD-ROM (for example, DKA400:).   Enter the boot command in the following format:

    BOOT -flags 0,0source-drive

    I.E.  >>> BOOT-flags 0,0 DKA400

      up

  • check BOOTING THE DISTRIBUTION CD FROM THE INFOSERVER:

  • At the console prompt, enter the following command:

    >>> BOOT -FL0,0 -FL APB_072 lan-device-name

    APB_072 is the file name of the APB program used for the initial system load (ISL) boot program.

    lan-device-name is the name of the local area network device  (FDDI or Ethernet) identified with your computer, as listed in the tables in the “OpenVMS Alpha Version 7.2 Upgrade and Installation Manual" section titled "Booting the Operating System CD-ROM".

    The InfoServer ISL program menu will be displayed.   Respond to the prompts as follows:

    Enter 3 for the function

    Enter 2 for the option ID

    Enter the service name(ALPHA072)

      up

  • check PERFORMING THE UPGRADE:

  • After you boot the distribution compact disc, choose the upgrade option (1) from the menu displayed on the screen.   The following questions will be asked:

    Do you want to INITIALIZE or to PRESERVE? [PRESERVE]

    For an upgrade, press the Return key to accept the default (PRESERVE)

    CAUTION: Do not INITIALIZE the disk for an upgrade. All software and data files will be removed.

    Enter device name for target disk: (? for choices) ddcu

    I.E. ddcu =DKA200

    Do you want to keep this label? (Yes/No) [Yes]

    Will this system be a member of an OpenVMS Cluster? (Yes/No)

    Will this system be an instance in an OpenVMS Galaxy? (Yes/No)

    The upgrade procedure will determine what products are installed on the system and list them then ask:

    Do you want the defaults for all product options?

    If NO, then you can add or delete them later.  You are prompted regarding questions for each product that was listed.

    Do you want to upgrade to V1.2-5? (Yes/No) [YES]

    Brief description prior to this question refers to DECwindows Motif.

    Do you want to install DECnet-Plus for OpenVMS Alpha V7.2?   (Yes/No) [NO]  

    NOTE:  ITEC supports DECnet Phase IV.  DECnet-Plus (Phase V) is not supported.

    If DECnet-Plus (Phase V) is found on the system, then the procedure will state that it will be upgraded, and DECnet Phase IV will not be upgraded.  If the answer is NO, and DECnet Phase IV is installed, then the procedure will state that DECnet Phase IV will be upgraded.

    Do you want to upgrade to V5.0-9? (Yes/No) [YES]

    Brief description prior to this question refers to Digital TCP/IP Services for OpenVMS.

    Do you always want detailed descriptions? (Yes/No) [No]

    Configuration phase starting ...

    Do you want the defaults for all options? [YES]

    Do you want all the default values for this product? [YES]

    Do you want to view the values? [NO]

    If YES is entered, the following prompts will be displayed:

                Accounting Log Report Generator Utility: [YES]

                 Access Control List Utilities: [YES]

                 Print and Batch Queue Utilities: [YES]

                 DECdtm Distributed Transaction Manager: [YES]

                 Support for DECnet-Plus or DECnet for OpenVMS: [YES]

                 DECnet Incoming Remote File Access [ YES]

                 DECnet Incoming Remote Terminal  [YES]

                 DECnet Network Test [YES]

                 DECnet Remote Task Loading [YES]

                 Programming Support: [YES]

                 Debugger Utility: [YES]

                 Image Dump Utility (ANALYZE/PROCESS_DUMP): [YES]

                 RMS Analyze and FDL Editor Utilities: [YES]

                 Message Utility: [YES]

                 System Sharable Image and Object Module Libraries: [YES]

                 Macro libraries: [YES]

                 Macro-32Migration Compiler: [YES]

                 TLB intermediary form of STARLET: [YES]

                 FORTRAN Require Files: [YES]

                 C Object Libraries: [YES]

                 C Header Files: [YES]

                 RMS Journaling Recovery Utility: [YES]

                 System Programming Support: [YES]

                 Support for ISO 9660 and High Sierra CD-rom Formats: [YES]

                 MONITOR:[YES]

                 Analyze Object File Utility: [YES]

                 Delta Debugger: [YES]

                  System Dump Analyzer Utility: [YES]

                 Miscellaneous Symbol Table Files: [YES]

                 OpenVMS Management Station Software -- PC files: [NO]

                 Utilities:[YES]

                 OpenVMS Mail Utility: [YES]

                  Dump Utility: [YES]

                 DIGITAL Standard Runoff (DSR) Text Formatter: [YES]

                 Phone Utility: [YES]

                 Help Library: [YES]

                 Foreign Terminal Support: [YES]

                 LAT-11Terminal Server (via Ethernet): [YES]

                 Error Log Generator Utility (ANALYZE/ERROR): [YES]

                 Terminal Fallback Facility: [YES]

                 TECO Interactive Text Editor: [YES]

                 National Character Set Utility (NCS): [YES]

                 DIAGNOSE Utility (DECevent): [YES]

                 XPG4Internationalization Utilities: [YES]

                 Bliss Require Files: [YES]

                 Example Files:[YES]

                 Message Facility Files (HELP/MESSAGE): [YES]

                  Translated Image Support: [YES]

                 UETP Files:[YES]

                 Support for DECwindows: [YES]

                 DECwindows workstation files: [YES}

                 video fonts:[YES]

                 100 dots per inch video fonts: [YES]

                 Delete any obsolete OpenVMS files: [YES]

    ** The following products will be upgraded on the system if needed.

                 DECwindows Motif for OpenVMS Alpha [YES]

                 DECnet-Plus for OpenVMS Alpha [NO]

                  DECnet Phase IV for OpenVMS Alpha [YES]

                 TCP/IP Services for OpenVMS [YES]

                 Applications [YES]

    Do you want to review the options? [NO]

    Execution phase starting ...

    The following products will be installed:

             DEC AXPVMSDECNET_OSI V7.2         Layered Product

             DEC AXPVMS OPENVMSV7.2              Platform (product suite)

             DEC AXPVMS UCXV4.2-16                   Layered Product

    DEC AXPVMS VMSV7.2                       Operating System

    The following product will be removed:

             DEC AXPVMS VMSV6.x(or 7.x)             Platform (product suite)

             DEC AXPVMS VMSV6.x(or 7.x)             Operating System

             DEC AXPVMS UCXV4.1-12                   Layered Product

         %PCSI-I-VOLINFO, estimated space information for volume

         DISK$AXPVMSSYS

         -PCSI-I-VOLSPC, 28061required; 143721 available; 115660 net

         Portion Done:0%...10%...20%...30%...40%...50%...60%...

                      70%...80%...90%...100%

         The following products have been installed:

             DEC AXPVMS DECNETOSI V7.2          Layered Product

             DEC AXPVMS OPENVMSV7.2             Platform (product suite)

             DEC AXPVMS UCXV5.0-9                    Layered Product

              DEC AXPVMS VMS V7.2                      Operating System

         The following products have be removed:

             DEC AXPVMS VMSV6.x(or 7.x)         Platform (product suite)

             DEC AXPVMS VMSV6.x(or 7.x)         Operating System

             DEC AXPVMS UCXV4.1-12               Layered Product

    Products which have been upgraded will display post upgrade messages.

    The upgrade is now complete.

    When the newly upgraded system is first booted, a special startup procedure will be run.  This procedure will:

        o   Run AUTOGEN to set system parameters.

        o   Reboot the system with the newly set parameters.

    You may shut down now or continue with other operations.

    Process AXPVMS_INSTALL logged out at [date& time]

    Press return to continue ...

    If you do not want to perform any other operations prior to booting the upgraded disk, choose option 8 to shut down the system.

     up

  • check POST-INSTALLATION INFORMATION:

  • up

  • check Monitor system reboot messages for errors or abnormalities.  

  • up

  • check Carefully confirm the complete date and time, including the year with the following command:

  •               $ SHOW TIME

    If the time is incorrect, correct it using this example:

                 $ SET TIME=14-JAN-1996:19:31  

    up

  • check If the system disk was a member of a Volume Shadowing set, enable Volume Shadowing on the upgraded system.  Refer to the "Volume Shadowing for OpenVMS" section titled "Upgrading the OpenVMS Operating System on a System Disk Shadow Set".  

  • $MOUNT/CONFIRM/SYSTEM DSAn: /SHADOW=(upgraded-disk:,new-member:) volume-label

    up

  • check Register any new layered product licenses, if necessary.

  • If you need to register new OpenVMS Alpha or layered product licenses, enter:

    $ LICENSE LIST/BRIEF   -  will list already registered licenses

    $ @SYS$UPDATE:VMSLICENSE

    up

  • check Review the AUTOGEN output file SYS$SYSTEM:AGEN$PARAMS.REPORT for errors, warnings, or inappropriately set parameter values.  

  • up

  • check Review the SYS$SYSTEM:MODPARAMS.DAT file.  The old version is named SYS$SYSTEM:MODPARAMS.DAT_OLD.  

  • up

  • check Review SYS$MANAGER:SYSTARTUP_VMS.COM, the following lines should be located after the decnet startup section: (if NOT, then add)

  •               $! Register all network services available

                   $@SYS$STARTUP:SYS$NET_SERVICES.COM

                   $!  

    up

  • check The upgrade procedure retains the site-specific versions of the following files:

  •           [SYSMGR]LAT$SYSTARTUP.COM

               [SYSMGR]LOGIN.COM

               [SYSMGR]SYCONFIG.COM

               [SYSMGR]SYLOGICALS.COM

               [SYSMGR]SYLOGIN.COM

               [SYSMGR]SYPAGSWPFILES.COM

               [SYSMGR]SYSECURITY.COM

               [SYSMGR]SYSHUTDWN.COM

               [SYSMGR]SYSTARTUP_VMS.COM

               [SYSMGR]TFF$STARTUP.COM

               [SYSMGR]WELCOME.TXT

               [SYS$STARTUP]ESS$LAST_STARTUP.DAT

    New templates with the .TEMPLATE extension for some of these files have been provided by the upgrade.  The new templates may include features that are not in your site-specific files. Check the templates against your site-specific files and edit your files as necessary.  

    up

    check If SYSUAF.DAT was copied to SYS$SYSTEM as a pre-upgrade task, copy it back to its original location.

    up

  • check Create a DECdtm log file, if the following message occurred during reboot:

  •               DECdtm log file not found (SYS$JOURNAL:SYSTEM$node.LM$JOURNAL)

    To create a DECdtm log file, enter the following commands:

                 $ RUN SYS$SYSTEM:LMCP

             LMCP> CREATE LOGFILE SYS$JOURNAL:SYSTEM$<node-name>.LM$JOURNAL

    If you have no applications on your system that use DECdtm, then you may want to inhibit DECdtm with the following command in SYS$MANAGER:SYLOGICALS.COM.  This will not effect the OpenVMS Queue Manager operation since the Inter Process Communications (IPC) are started up separate from DECdtm under OpenVMS.

                  $DEFINE/SYSTEM/EXECUTIVE SYS$DECDTM_INHIBIT "YES"

                  $DEFINE/SYSTEM/EXECUTIVE SYS$DECDTM_INHIBIT "YES"

    up

  • check If you have approximately 30,000 free blocks on the disk, you can decompress all system libraries with the following command:

  •              $@SYS$UPDATE:LIBDECOMP

    up

  • check Test the System with UETP, the User Environment Test Package
  • The User Environment Test Package (UETP) is a software package designed to test whether the OpenVMS Alpha operating system is installed correctly.  As part of  the postupgrade procedure, Compaq recommends that you run UETP to verify the upgrade.

     

    up

    check After you have upgraded, customized and installed layered products, protect your work by making a backup copy of the system disk.   Refer to the "Backing Up the Customized System Disk" section of the "OpenVMS Alpha Version 7.2 Upgrade and Installation Guide.

    up

  • check Install DECevent.  DIAGNOSE command is disabled during the upgrade procedure.  The DECevent kit is located on the OpenVMS Alpha 7.2 distribution CD-ROM.  

  • up

  • check Reboot the upgraded system and each system that boots from that system disk.

  • up

    check After 24 hours of operation run AUTOGEN  in FEEDBACK mode and reboot the system.  Run AUTOGEN in this way again two workdays later. Digital recommends that you run AUTOGEN from SAVPARAMS through TESTFILES on a weekly basis and examine AGEN$PARAMS.REPORT to determine the need for additional changes. More information on using AUTOGEN and making adjustments to MODPARAMS.DAT may be found in the "OpenVMS System Manager's Manual" or in the "How To Use AUTOGEN For The First Time" article in the “OpenVMS" text search database.

    up

  • check Install/Upgrade Layered Products and related ECOs/Patches
  •  

    Except in certain instances, you should not have to reinstall layered products that you had on your system prior to the upgrade.  However, if you need to install layered products, you can use the menu system included on the operating system CD-ROM to install certain layered products with the POLYCENTER Software Installation utility. 

     

    To install layered products that require VMSINSTAL (indicated in the directories by save-set file names with files types of .A, .B and so on), enter the @SYS$UPDATE:VMSINSTAL command and then specify the CD-ROM device and directory. 

     

    To locate the directories and files containing the available layered products: 

    $ DIRECTORY /NOHEAD/NOTRAIL DKA400:[*.KIT]

     

    To locate kits that are installed using the POLYCENTER Software Installation utility: 

    $PRODUCT FIND * /SOURCE=DKA400:[*.kit]

     

    To install layered products that require the POLYCENTER Software Installation utility (indicated in the directories by file names with file types of  .PCSI or .PCSI$DESCRIPTION), use the PRODUCT INSTALL command:                 

                            $ PRODUCT INSTALL name /SOURCE=DKB400:[name.KIT]

    up

    SEARCH/QUERY WORDS:

    NEW_7.2_ALPHA

    REFERENCES

       "OpenVMS Alpha Version 7.2 Upgrade and Installation Manual", January 1999, (AA-QSE8C-TE).

      "OpenVMS Version 7.2 New Features Manual", January 1999, (AA-QSBFC-TE).

      "OpenVMS Version 7.2 Release Notes", January 1999, (AA-QSBFC-TE).

      "SPD 25.01.55: OpenVMS Operating System for Alpha and VAX, Version 7.2", January 1999.

      "OpenVMS System Manager's Manual", January 1999,(AA-PV5ME-TK).

      "VMScluster Systems for OpenVMS", January 1999,(AA-PV5WD-TK).

      "Volume Shadowing for OpenVMS", November 1996,(AA-PVXMD-TE).

    [R]  Motif, OSF, and OSF/Motif are registered trademarks of the Open Software Foundation,Inc.  

     
     

    ITEC bullet Buffalo State College bullet Twin Rise 200 bullet 1300 Elmwood Avenue bullet Buffalo, NY 14222 bullet (716) 878-4832


    [ Home ] [ Academic Support ] [ Administrative Support ] [ Systems Support ] [ News ] [ SUNY Links ]

    E-mail ITEC: scacad@itec.mail.suny.edu