Document revision date: 30 March 2001
[Compaq] [Go to the documentation home page] [How to order documentation] [Help on this site] [How to contact us]
[OpenVMS documentation]

OpenVMS VAX Version 7.3
Upgrade and Installation Manual


Previous Contents Index

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

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


Chapter 9
Customizing DECwindows Support Software

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:

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:

9.1.2 How to Override Incorrect Assumptions

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:


      $ DECW$DEFAULT_KEYBOARD_MAP == "DUTCH_LK201LH_TW" 
      

      Add a line similar to this for each workstation that does not have a North American keyboard layout, or add it to the common section for all workstations (if all the workstations use the same keyboard layout).

  6. To add support for the Transmission Control Protocol/Internet Protocol (TCP/IP) transport using the Compaq TCP/IP Services for OpenVMS product, add the following line:


    $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP" 
    

    Add this line to the section for each workstation that will be using TCP/IP, or add it to the common section for all workstations.
    To include support for other transports, add the last part of the transport image name to the list of transports. For example, suppose you want to add support for a customer-written transport that has the following image name:
    SYS$SHARE:DECW_TRANSPORT_FOO
    You would add the following line:


    $ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,FOO" 
    

  7. Reboot the workstations for which you customized the server startup.
  8. Customize security as described in the Using DECwindows Motif for OpenVMS manual.

After you start the server, a per-server logical name table is created on your system but is not added to the default logical name table search lists.

9.2 Using Compaq TCP/IP Services for OpenVMS

DECwindows contains support for the TCP/IP transport. This support requires Compaq TCP/IP Services for OpenVMS, a Compaq layered product. Before you can use the DECwindows TCP/IP transport interface, you must install Compaq TCP/IP Services for OpenVMS.

Note

Other vendors' implementation of TCP/IP transports use different call interfaces. For this reason, DECwindows support for TCP/IP is compatible only with Compaq TCP/IP Services for OpenVMS.

You can conserve memory and process slots by configuring Compaq TCP/IP Services for OpenVMS software for the minimum DECwindows requirement to support the X protocol. DECwindows only requires that INET_ACP be running. DECwindows does not require that the NFS server, the FTPD server, or the remote terminal servers be running.

For more information about TCP/IP concepts, refer to the Compaq TCP/IP Services for OpenVMS documentation. For information about how to configure the TCP/IP software, refer to the Compaq TCP/IP Services for OpenVMS Installation and Configuration manual.

Documentation for Compaq TCP/IP Services for OpenVMS is included on the OpenVMS Online Documentation CD-ROM. Hardcopy documentation must be purchased separately.

9.3 Using Other Transports with DECwindows

DECwindows supports DECnet--Plus, local, and TCP/IP transports. However, you can use other transports, such as new transports for layered products and transports from third-party vendors, with DECwindows by writing a DECwindows transport interface layer.


Previous Next Contents Index

  [Go to the documentation home page] [How to order documentation] [Help on this site] [How to contact us]  
  privacy and legal statement  
6630PRO_013.HTML