Document revision date: 19 July 1999

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

8.12.2 Using VMSTAILOR and DECW$TAILOR

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

8.13 Restoring Your System Password Dictionary

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

8.14 Customizing DECwindows Support Software

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 DIGITAL TCP/IP Services 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: 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: Tuning, Monitoring, and Complex Systems.

8.19 Postupgrade Checklist

Use the following checklist to make sure you perform all the necessary postupgrade tasks.

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

This chapter describes how you can customize DECwindows support software. The DECwindows components provided on the OpenVMS VAX kit supply DECwindows base support and workstation support files only. If you have not installed either of these DECwindows components on your system, skip this chapter.

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 with DECwindows other than those supplied by Compaq

Note that the OpenVMS VAX operating system no longer includes the VMS DECwindows product. To get full DECwindows support, you must also install the separate DECwindows Motif for OpenVMS VAX layered product, which supports both the Motif and XUI environments.

9.1 Customizing the Server Startup

By default, the DECwindows server no longer logs successful connect/disconnect messages to the DECW$SERVER_#_ERROR.LOG file. To enable these messages, define the symbol DECW$SERVER_CONNECT_LOG in the DECW$PRIVATE_SERVER_SETUP.COM file to be "T" and restart the server. Note that abnormal or unsuccessful connect/disconnect messages are still logged by the server.

9.1.1 Assumptions

The startup command procedures automatically determine most of the configuration variables for the DECwindows display server. However, there are items that the command procedures cannot determine, so they make the following assumptions:

• The startup procedures normally assume that you have a 75 dots/inch monitor (such as a VR260 or VR290). However, if you are installing on a VAXstation 4000, the startup procedures assume that you have a 100 dots/inch monitor.
• If you have a GPX, SPX, or LCG workstation, the startup procedures assume that you have a color monitor.
• The startup procedures normally assume that you have a North American keyboard layout (you have an LK201--AA or an LK201--LA keyboard). If you are installing on a VAXstation 4000, the startup procedures assume that you have an LK401--AA keyboard.
• The startup procedures assume that the server will use only DECnet software and local transports.

If any of these assumptions is incorrect, you must override them as follows:

1. Make a copy of the file SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.TEMPLATE and rename it to a .COM file type. The comments in this file show how to customize individual workstations by adding a section of DCL commands for each workstation. You can also add DCL commands to the common section of the server startup file. By doing this, you ensure that the customizations you make affect all workstations that use the server startup file.
2. If your screen supports 100 dots/inch, add the following line:

   $ DECW$SERVER_DENSITY == "100"

   
   Add this line to the section for each workstation that has a 100 dots/inch monitor, or add it to the common section for all workstations (if all the workstations have 100 dots/inch monitors).

3. If you have upgraded to a VAXstation 4000 but still have a 75 dots/inch monitor, add the following line:

   $ DECW$SERVER_DENSITY == "75"

4. The section for any workstation with color graphics and a monochrome screen should contain the following lines:

   $ DECW$COLOR == "FALSE" $ DECW$BITONAL == "FALSE"

5. To override the default keyboard layout, determine the correct name from the model number of your LK201 keyboard, as follows:
   1. Turn the keyboard upside down, and look for a label that specifies the model number. The model number should be in a format similar to LK201-xx.
      If the model number is listed as LK201 without any additional characters, the information you need is on another part of the label. Look for a number that has the following format:

      nn-nnnnn-xx.

   2. Use the xx part of this number to choose a keymap name from Table 9-1. The table is arranged based on the dialect that each keyboard is designed for. Choose the keymap ending in _DP for the data processing keyboard layout, or the keymap ending in _TW for the typewriter layout.

      Table 9-1 DECwindows Keymap

      Dialect	Model	DECwindows Keymap Name
      Austrian/German	LK201-(AG,LG,BG,MG)	AUSTRIAN_GERMAN_LK201LG_DP
      		AUSTRIAN_GERMAN_LK201LG_TW
      	LK201-(NG,PG)	AUSTRIAN_GERMAN_LK201NG_DP
      		AUSTRIAN_GERMAN_LK201NG_TW
      	LK401-(AG)	AUSTRIAN_GERMAN_LK401AG_TW
      Belgian/French	LK201-(AP,LP,BP,MP)	BELGIAN_FRENCH_LK201LP_DP
      		BELGIAN_FRENCH_LK201LP_TW
      Belgian/French	LK401-(AP)	BELGIAN_FRENCH_LK401AP_DP
      		BELGIAN_FRENCH_LK401AP_TW
      British	LK201-(AE,LE,BE,ME)	BRITISH_LK201LE_DP
      		BRITISH_LK201LE_TW
      British	LK401-(AA,PA)	BRITISH_LK401AA_DP
      		BRITISH_LK401AA_TW
      Canadian/French	LK201-(AC,LC,BC,MC)	CANADIAN_FRENCH_LK201LC_DP
      		CANADIAN_FRENCH_LK201LC_TW
      Canadian/French	LK401-(AC,LC,BC,MC)	CANADIAN_FRENCH_LK401AC_DP
      		CANADIAN_FRENCH_LK401AC_TW
      Czech	LK401-(BV)	CZECH_LK401AV
      Danish	LK201-(AD,LD,BD,MD)	DANISH_LK201LD_DP
      		DANISH_LK201LD_TW
      	LK201-(ED,RD,FD)	DANISH_LK201RD_DP
      		DANISH_LK201RD_TW
      Danish	LK401-(AD,LD,BD,MD)	DANISH_LK401AD_DP
      		DANISH_LK401AD_TW
      Dutch	LK201-(AH,LH,BH,MH)	DUTCH_LK201LH_DP
      		DUTCH_LK201LH_TW
      	LK201-(NH,PH)	DUTCH_LK201NH
      	LK401-(NH,PH)	DUTCH_LK401AH
      Finnish	LK201-(AF,LF,BF,MF)	FINNISH_LK201LF_DP
      		FINNISH_LK201LF_TW
      	LK201-(NX,PX)	FINNISH_LK201NX_DP
      		FINNISH_LK201NX_TW
      Finnish	LK401-(AF,LF,BF,MF)	FINNISH_LK401AF_DP
      		FINNISH_LK401AF_TW
      Flemish	LK201-(AB,LB,BB,MB)	FLEMISH_LK201LB_DP
      		FLEMISH_LK201LB_TW
      Flemish	LK401-(AB,LB,BB,MB)	FLEMISH_LK401AB_DP
      		FLEMISH_LK401AB_TW
      Hungarian	LK401-(BQ)	HUNGARIAN_LK401_BQ
      Icelandic	LK201-(AU,LU,BU,MU)	ICELANDIC_LK201LU_DP
      		ICELANDIC_LK201LU_TW
      Italian	LK201-(AI,LI,BI,MI)	ITALIAN_LK201LI_DP
      		ITALIAN_LK201LI_TW
      Italian	LK401-(AI,LI,BI,MI)	ITALIAN_LK401AI_DP
      		ITALIAN_LK401AI_TW
      North American	LK201-(AA,LA,BA,MA)	NORTH_AMERICAN_LK201LA
      North American	LK401-(AA,LA,BA,MA)	NORTH_AMERICAN_LK401AA
      Norwegian	LK201-(AN,LN,BN,MN)	NORWEGIAN_LK201LN_DP
      		NORWEGIAN_LK201LN_TW
      	LK201-(EN,RN,FN)	NORWEGIAN_LK201RN_DP
      		NORWEGIAN_LK201RN_TW
      Norwegian	LK401-(AN,LN,BN,MN)	NORWEGIAN_LK401AN_DP
      		NORWEGIAN_LK401AN_TW
      Polish	LK401-(BP)	POLISH_LK401_BP
      Portuguese	LK201-(AV,LV,BV,MV)	PORTUGUESE_LK201LV
      Portuguese	LK401-(AV,LV,BV,MV)	PORTUGUESE_LK401AV
      Russian	LK401-(BT)	RUSSIAN_LK401_BT
      Slovakian	LK401-(CZ)	SLOVAK_LK401_CZ
      Spanish	LK201-(AS,LS,BS,MS)	SPANISH_LK201LS_DP
      		SPANISH_LK201LS_TW
      Spanish	LK401-(AS,LS,BS,MS)	SPANISH_LK401AS_DP
      		SPANISH_LK401AS_TW
      Swedish	LK201-(AM,LM,BM,MM)	SWEDISH_LK201LM_DP
      		SWEDISH_LK201LM_TW
      	LK201-(NM,PM)	SWEDISH_LK201NM_DP
      		SWEDISH_LK201NM_TW
      Swedish	LK401-(AM,LM,BM,MM)	SWEDISH_LK401AM_DP
      		SWEDISH_LK401AM_TW
      Swiss/French	LK201-(AK,LK,BK,MK)	SWISS_FRENCH_LK201LK_DP
      		SWISS_FRENCH_LK201LK_TW
      Swiss/French	LK401-(AK,LK,BK,MK)	SWISS_FRENCH_LK401AK_DP
      		SWISS_FRENCH_LK401AK_TW
      Swiss/German	LK201-(AL,LL,BL,ML)	SWISS_GERMAN_LK201LL_DP
      		SWISS_GERMAN_LK201LL_TW
      Swiss/German	LK401-(AL,LL,BL,ML)	SWISS_GERMAN_LK401AL_DP
      		SWISS_GERMAN_LK401AL_TW
      Combined US/UK	LK201-(EE,RE,PE)	UK_LK201RE
      		US_LK201RE
      Combined US/UK	LK401-(EE,RE,PE)	UK_LK401AA
      		US_LK401AA

   3. After you choose a keymap name, modify the server startup file. For example, to change the keyboard layout to a Dutch typewriter layout, add the following line to the server startup file:

      ---

      Previous

      Next

      Contents

      Index

      	privacy and legal statement
      6521PRO_012.HTML