![[Digital logo]](../../IMAGES/DIGITAL-LOGO.GIF){kind=logo}
![[HR]](../../IMAGES/REDBAR.GIF)
If you are running DECwindows Motif, use DECW$TAILOR to add or remove DECwindows base support, workstation support, and fonts.
Note
Files installed on alternate devices cannot be tailored.
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:
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.
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.
Note
If you did not select the optional OpenVMS Management Station client software files during the installation or upgrade, you must add these files to your OpenVMS system disk before you follow the instructions in Appendix G. Use the OpenVMS Version 7.1 distribution media and VMSTAILOR to add the OpenVMS Management Station files to your system. (For information about using VMSTAILOR, see Chapter 10.)
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.
For additional information about installing layered products, see the OpenVMS System Manager's Manual.
If you installed the Digital TCP/IP Services for OpenVMS software during the installation or if you choose to install it now as a layered product, note that you must also install the mandatory security update kit included with this release.
The Digital TCP/IP Kit and the mandatory Security Update Kit are available in the following directory on the OpenVMS VAX CD-ROM:
[TCPIP_VAX_041]
If you choose to install the Digital TCP/IP Services for OpenVMS software, you must install both kits.
Digital recommends that you protect your work by performing the following operations:
For complete information about these operations, see the upgrade and installation supplement for your VAX computer.
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:
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, see the upgrade and installation supplement for your VAX 9000 computer.
For information about using AUTOGEN, see the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems.
Use the following checklist to make sure you perform all the necessary postupgrade tasks.
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.
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.
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:
If any of these assumptions is incorrect, you must override them as follows:
$ DECW$SERVER_DENSITY == "100"
$ DECW$SERVER_DENSITY == "75"
$ DECW$COLOR == "FALSE" $ DECW$BITONAL == "FALSE"
nn-nnnnn-xx.
| 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 |
$ DECW$DEFAULT_KEYBOARD_MAP == "DUTCH_LK201LH_TW"
$ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP"
$ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,FOO"
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.
DECwindows contains support for the TCP/IP transport. This support requires Digital TCP/IP Services for OpenVMS, a Digital layered product. Before you can use the DECwindows TCP/IP transport interface, you must install Digital 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 Digital TCP/IP Services for OpenVMS.
You can conserve memory and process slots by configuring Digital 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, see the Digital TCP/IP Services for OpenVMS: Management manual.
For information on how to configure the TCP/IP software, see the Digital TCP/IP Services for OpenVMS: Installation and Basic Configuation manual.
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.
For information about writing a transport interface, see the VMS DECwindows Transport Manual.
The transport interface image's filename must have the following format where name is the unique transport name:
DECW$TRANSPORT_name (for transports supplied by Digital)
DECW_TRANSPORT_name (for customer-written transports)
Install the image as a protected image in the SYS$SHARE directory (as defined by an executive mode logical name). Digital recommends that you install the image by adding the following line to SYS$MANAGER:SYSTARTUP_VMS.COM:
$ INSTALL CREATE SYS$SHARE:DECW_TRANSPORT_name/OPEN/SHARED- /HEADER_RESIDENT/PROTECTED
You can also include this command in a startup file that SYSTARTUP_VMS calls.
To use this transport with the DECwindows server, customize the server startup as described in Section 9.2.
DECwindows has an example transport interface based upon the Digital TCP/IP Services for OpenVMS layered product. It is similar to the DECwindows TCP/IP transport interface, except it includes its own source files and it uses a different port number (5000). You can run the example transport interface simultaneously with the TCP/IP transport interface.
If you have installed Digital TCP/IP Services for OpenVMS software, you can install and use the example transport by doing the following:
$ COPY DECW$EXAMPLES:DECW$TRANSPORT_EXAMPLE.EXE SYS$SHARE:/PROT=W:RE
$ INSTALL CREATE SYS$SHARE:DECW$TRANSPORT_EXAMPLE /OPEN /SHARED- /HEADER_RESIDENT /PROTECTED
$ DECW$SERVER_TRANSPORTS == "DECNET,LOCAL,TCPIP,EXAMPLE"
$ SET DISPLAY /CREATE /NODE=your_node /TRANSPORT=EXAMPLE
$ RUN SYS$SYSTEM:DECW$CLOCK
This chapter describes how to add or remove optional OpenVMS VAX files and DECwindows support files from your system disk using VMSTAILOR and DECW$TAILOR. You will need your OpenVMS VAX software media kit to tailor on files. Any site-specific customization that has been done to a class will be lost when that class is tailored off.
To add or remove unwanted OpenVMS VAX files from the system disk, use VMSTAILOR. For example, if you are not running DECnet for OpenVMS, and you do not need the network support files, you can remove those files using VMSTAILOR. If you later decide you want to run DECnet for OpenVMS, you can add the necessary files at any time using VMSTAILOR and your OpenVMS VAX distribution media. (Note that you cannot tailor files on or off an alternate device.)
VMSTAILOR has three phases:
6487P009.HTM OSSG Documentation 9-DEC-1996 10:54:08.34
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.