HP OpenVMS Systems Documentation

If you upgraded a VAX 8200, 8250, 8300, 8350, 8600, or 8650 computer, follow the instructions in this section.

The procedure does the following:

• Checks to see if you have enough space for the new VMB.EXE
• Copies the new VMB.EXE to the console media
• Updates the BOOT58 file for the VAX 8200, 8250, 8300, and 8350 computers

To update the console media, use the following procedure:

1. Log in to the SYSTEM account.
2. Enter the following commands to check if there is enough space for the new VMB.EXE. You need 120 blocks. If you are updating a VAX computer, use CSA1 for device-name.

   $ RUN SYS$SYSTEM:SYSGEN SYSGEN> CONNECT CONSOLE SYSGEN> EXIT $ EXCHANGE DIRECTORY device-name:VMB.EXE Directory of RT-11 volume TINES$CSA1: 13-NOV-2000 18:40 VMB.EXE 80 13-NOV-2000 Total of 1 file, 80 blocks. Free space 43 blocks, largest 23.

   
   If the size of the current VMB, plus the free space, does not equal at least 120 blocks, delete unneeded files on the console until you have 120 blocks available. In the above example, the size of the current VMB.EXE (80 blocks) plus the free space (43 blocks) equals 123 blocks, so files do not have to be deleted.
3. Enter the following command and press Return:

   $ @SYS$UPDATE:UPDATE_CONSOLE.COM

4. If you are updating the console media for a VAX 8600 or VAX 8650 computer, the new VMB.EXE is copied onto the console media.
   If you are updating the console media for one of the other VAX computers, the procedure uses the EXCHANGE procedure to copy the contents of the existing console media, merge the new files onto the copy of the console media, and create a new version of the console media. When the computer is ready to create the new version, it displays a message asking you to insert a scratch tape cassette or diskette. Take out the original console media and insert a new one.

VAX 9000 computers use a special version of VMB.EXE named VMB9AQ.EXE. The upgrade procedure automatically copies a new version of this file to the console hard disk. However, if for some reason you need to update the console hard disk, use the UPDATE_CONSOLE.COM command procedure described for the VAX 8200, 8250, 8300, 8350, 8600, and 8650 computers. The device name for the VAX 9000 console hard disk is CSA1.

8.10 Decompressing the System Libraries

Decompressing the system libraries gives the system faster access to the libraries. You can decompress all the system libraries or just some of them.

The additional amount of disk space required to decompress all the system libraries is about 22,600 blocks. To find out how much disk space you have, enter the following command and press Return:

$ SHOW DEVICE SYS$SYSDEVICE

Table 8-1 gives the approximate number of blocks consumed by each library after decompression.

You execute the LIBDECOMP.COM command procedure to decompress the system libraries. To run LIBDECOMP, log in to the SYSTEM account, enter the following command, and press Return:

$ @SYS$UPDATE:LIBDECOMP.COM

The following information is displayed:

                 OpenVMS Library Decompression Utility

     1  HELPLIB.HLB          15  SDA.HLB              28  PHONEHELP.HLB
     2  STARLET.OLB          16  SHWCLHELP.HLB        29  LIB.MLB
     3  ACLEDT.HLB           17  SYSGEN.HLB           30  STARLET.MLB
     4  ANLRMSHLP.HLB        18  ANALAUDIT$HELP.HLB   31  STARLETSD.TLB
     5  DBG$HELP.HLB         19  SYSMANHELP.HLB       32  SYS$STARLET_C.TLB
     6  DBG$UIHELP.HLB       20  TFF$TFUHELP.HLB      33  ERFLIB.TLB
     7  DISKQUOTA.HLB        21  EXCHNGHLP.HLB        34  VAXCCURSE.OLB
     8  EDFHLP.HLB           22  TPUHELP.HLB          35  VAXCRTL.OLB
     9  INSTALHLP.HLB        23  EVE$HELP.HLB         36  VAXCRTLG.OLB
    10  LATCP$HELP.HLB       24  EVE$KEYHELP.HLB      37  IMAGELIB.OLB
    11  MAILHELP.HLB         25  UAFHELP.HLB          38  DECCCURSE.OLB
    12  MNRHELP.HLB          26  TECO.HLB             39  DECCRTL.OLB
    13  EDTHELP.HLB          27  PATCHHELP.HLB        40  DECCRTLG.OLB
    14  NCPHELP.HLB

          A  ALL libraries to be decompressed
          E  EXIT this procedure

* Enter letter or number(s) of libraries to be decompressed
  (Separate multiple entries with a comma):

Enter the appropriate letter or the numbers of the libraries you want to decompress. To decompress all libraries, the process takes approximately one half hour.

If you prefer, you can execute LIBDECOMP interactively or as a batch job. If you use either of these methods, you can decompress up to 8 libraries each time you execute LIBDECOMP by listing the names of the libraries you want to decompress as parameters on the command line. (You can decompress all the libraries by omitting the /PARAMETERS qualifier.) Be sure to separate the library names with commas and do not include the file extension. For example, to decompress the VAXCRTL.OLB, DISKQUOTA.HLB, and LIB.MLB libraries as a batch job, enter the following command:

$ SUBMIT/NOTIFY/PARAMETERS=(VAXCRTL, DISKQUOTA, LIB)-
_$ SYS$UPDATE:LIBDECOMP

To decompress these same libraries interactively, enter the following command:

$ @SYS$UPDATE:LIBDECOMP VAXCRTL DISKQUOTA LIB

Note that, when you type the command for a batch job, you separate the library names with commas and enclose the list within parentheses. You do not use commas or parentheses on the interactive command line.

8.11 Testing the System with UETP

UETP, the user environment test package, is a software package that tests whether the OpenVMS VAX operating system is installed correctly. As part of the postupgrade procedure, you should run UETP to verify your upgrade.

Note that UETP needs at least 1200 free blocks on the system disk and is available only if you installed the optional save set VMS072.D. If you did not install the optional save set, you can add the UETP files to your system using VMSTAILOR. For information about using VMSTAILOR, see Chapter 10.

For complete information about UETP, refer to the OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems.

8.12 Increasing Free Space on the System Disk

This section describes how to increase the amount of free space on your system disk. You can gain free space by removing optional OpenVMS VAX files that you do not need from the system disk or by purging old versions of some system files.

8.12.1 Running the ANALYZE /DISK_STRUCTURE Utility

Certain disk structure inconsistencies may be introduced during the OpenVMS VAX upgrade operation. To check for these inconsistencies, enter the following command:

$ ANALYZE /DISK_STRUCTURE SYS$SYSDEVICE:

This command produces output in the following format:

            Error opening QUOTA.SYS
            No such file
            File (2849,7,1) DCLTABLES.EXE;31
                    marked for delete
            File (4270,3,1) SYS.EXE;2
                    marked for delete
            File (5485,9,1) SYS$NETWORK_SERVICES.EXE;1
                    marked for delete

If quotas are not in use on the system disk, ignore the "No such file" message for QUOTA.SYS. Most inconsistencies (including "marked for delete") can be repaired by entering the following command:

$ ANALYZE /DISK_STRUCTURE /REPAIR SYS$SYSDEVICE:

To remove files you do not need from the system disk, use VMSTAILOR. For example, if you are not running DECnet for OpenVMS, you do not need the network support files. For complete information about using VMSTAILOR to remove files, see Chapter 10.

If you are running DECwindows Motif, use DECW$TAILOR to add or remove DECwindows base support, workstation support, and fonts.

In most cases, you can purge the following OpenVMS system files to free space on your system disk. However, before you purge any of these files, read Appendix F to make sure you do not purge a file version you might want to keep.

SYS$SYSTEM:SHUTDOWN.COM
SYS$SYSTEM:STARTUP.COM
SYS$LIBRARY:ENCRYPSHR.EXE
SYS$LIBRARY:*RTL*.EXE
SYS$LIBRARY:*SHR.EXE
SYS$MANAGER:EDTINI.EDT
SYS$MANAGER:DBLSTRTUP.COM
SYS$MANAGER:*.TEMPLATE
SYS$EXAMPLES:XADRIVER.MAR
SYS$LIBRARY:CDDSHR.EXE
SYS$LIBRARY:EPC$FACILITY.TLB
SYS$MESSAGE:EPC$MSG.EXE
SYS$STARTUP:VMS$LAYERED.DAT

To purge a file, enter the PURGE command followed by the file specification. For example:

$ PURGE SYS$SYSTEM:SHUTDOWN.COM

The OpenVMS VAX operating system screens potential passwords for acceptability. The DCL command SET PASSWORD takes the user's proposed password, converts it to lowercase (if necessary), and compares it to entries in a system dictionary. If the proposed password is found in the dictionary, it is rejected as a valid user password, and the user must suggest another. Many system managers modify the system password dictionary to include words of significance to their site.

During the upgrade, the procedure replaces the existing system password dictionary with a new one. If you had modified the dictionary and want to restore your local additions, you must merge the file containing your additions with the new system file.

To add your site-specific passwords to the new system password dictionary, enable SYSPRV and merge your local additions by entering the following commands, where LOCAL_PASSWORD_DICTIONARY.DATA is the file that contains your additions:

$ SET PROCESS/PRIVILEGE=SYSPRV
$ CONVERT/MERGE/PAD LOCAL_PASSWORD_DICTIONARY.DATA -
_$ SYS$LIBRARY:VMS$PASSWORD_DICTIONARY.DATA

If you have installed DECwindows support software, there are several steps that you can take to customize the DECwindows environment. Depending on your configuration, DECwindows customization tasks include the following:

• Customizing the server startup
• Using the Transmission Control Protocol/Internet Protocol (TCP/IP) as a DECwindows transport
• Using transports for DECwindows other than those supplied by Compaq

Go to Chapter 9 for complete instructions for customizing your DECwindows support software.

After you complete the tasks described in Chapter 9, return to this chapter to continue with the remaining postupgrade tasks.

8.15 Preparing to Use the OpenVMS Management Station

The OpenVMS Management Station client/server software provides OpenVMS system management capabilities through a client application on a personal computer (PC) running Microsoft Windows.

When you upgraded your OpenVMS system, the OpenVMS Management Station server files were automatically installed on your OpenVMS system disk. However, to obtain complete support, you had to select the OpenVMS Management Station client software files during the OpenVMS upgrade procedure. Those files are required for creating the installation media that you use to install the client software on your PC.

Appendix G provides complete instructions for preparing your OpenVMS system and your PC to run the OpenVMS Management Station software.

Back up your system disk and then use either the VMSINSTAL command procedure or the POLYCENTER Software Installation utility to install layered products on your system. If the system contained Compaq TCP/IP Services for OpenVMS previous to the upgrade, you must reinstall it now.

For additional information about installing layered products, see the OpenVMS System Manager's Manual.

8.17 Backing Up the System Disk

Compaq recommends that you protect your work by performing the following operations:

• Use SYS$UPDATE:CONSCOPY.COM to back up the console media (if applicable).
• Make a standalone BACKUP kit on removable media and on the system disk.
  If your console media is a TU58 tape cartridge or an RX01 diskette, use the standalone BACKUP copy you made before you began the upgrade. (See Section 5.4.2.)
• Back up the system disk.

For complete information about these operations, refer to the upgrade and installation supplement for your VAX computer.

8.18 Running AUTOGEN

When you upgraded the OpenVMS VAX operating system, the procedure executed AUTOGEN to set the values of system parameters and the sizes of the page and swap files according to the system's workload.

In many cases, AUTOGEN can improve system performance by using dynamic feedback information from the running system. As a postinstallation task, you should run AUTOGEN again using the feedback mechanism to make further adjustments to system parameters.

When AUTOGEN runs after an upgrade, it uses the parameter values in SYS$SYSTEM:MODPARAMS.DAT. Note that hardcoded values in MODPARAMS.DAT affect AUTOGEN's calculations of the feedback parameters. For AUTOGEN to properly calculate minimum values, you should replace the hardcoded values in MODPARAMS.DAT with MIN_ values. The MIN_ prefix specifies the minimum value to which a parameter can be set by AUTOGEN.

If you are not satisfied with the parameter settings calculated by AUTOGEN, you can modify the parameter values by editing MODPARAMS.DAT as explained in the OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems.

After you have upgraded the operating system, run AUTOGEN again using the following procedure:

1. After 24 hours of operation, run AUTOGEN in feedback mode and reboot the system.
2. Run AUTOGEN in this same way, again, two working days later.

   Note For the VAX 9000 computer, AUTOGEN's initial parameter calculations are conservative. To obtain parameter values that match your system workload, you can run AUTOGEN in feedback mode a number of times. For more information, refer to the upgrade and installation supplement for your VAX 9000 computer.

3. Compaq 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.

For information about using AUTOGEN, refer to the OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems.

8.19 Postupgrade Checklist

• Verify the system time (described in Section 8.1)
• Restore the preferred node list for the queue manager (described in Section 8.2)
• Replace SYSUAF.DAT and VMS$AUDIT_SERVER.DAT (described in Section 8.3)
• Examine AUTOGEN output stored in the file AGEN$PARAMS.REPORT (described in Section 8.4)
• Examine the command procedure templates supplied with OpenVMS VAX Version 7.3 (described in Section 8.6)
• Examine MODPARAMS.DAT (described in Section 8.7)
• Update your console media (described in Section 8.8)
• Decompress the system libraries using LIBDECOMP.COM (described in Section 8.10)
• Run UETP (the user environment test package) to test the system (described in OpenVMS System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex Systems)
• Remove unwanted files and check the sizes of system files (described in Section 8.12)
• Restore your local additions to the system password dictionary (described in Section 8.13)
• Customize your DECwindows environment (described in Section 8.14)
• Build a standalone BACKUP kit (described in Section 8.17)
• Back up the console media (described in Section 8.17)
• Install layered products (described in Section 8.16)
• Back up the system disk (described in the upgrade and installation supplement for your computer)
• Run AUTOGEN and reboot the system after the first 24 hours of operation (described in Section 8.18)