$ 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"

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 DIGITAL TCP/IP Services for OpenVMS

DECwindows contains support for the TCP/IP transport. This support requires DIGITAL TCP/IP Services for OpenVMS, a Compaq layered product. Before you can use the DECwindows TCP/IP transport interface, you must install 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, refer to the DIGITAL TCP/IP Services for OpenVMS Management manual. For information about how to configure the TCP/IP software, refer to the DIGITAL TCP/IP Services for OpenVMS Installation and Configuration manual.

Documentation for DIGITAL 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.

9.3.1 Writing a Transport Interface

For information about writing a transport interface, refer to the VMS DECwindows Transport Manual.

The transport interface image's file name must have the following format where name is the unique transport name:

DECW$TRANSPORT_name (for transports supplied by Compaq)
DECW_TRANSPORT_name (for customer-written transports)

9.3.2 Installing the Transport Interface Image

Install the image as a protected image in the SYS$SHARE directory (as defined by an executive mode logical name). Compaq 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.1.

9.4 Using the Example Transport

DECwindows has an example transport interface based on 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:

1. Copy the example transport to the SYS$SHARE directory as follows:

   $ COPY DECW$EXAMPLES:DECW$TRANSPORT_EXAMPLE.EXE SYS$SHARE:/PROT=W:RE

2. Add the following line to SYS$MANAGER:SYSTARTUP_VMS.COM:

   $ INSTALL CREATE SYS$SHARE:DECW$TRANSPORT_EXAMPLE /OPEN /SHARED- /HEADER_RESIDENT /PROTECTED

3. Customize the private server startup as described in Section 9.1 for TCP/IP, except use the transport name "EXAMPLE". For example, you might add the following line:

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

4. Reboot the workstation, or restart DECwindows.
5. Customize TCP/IP security as described in the Using DECwindows Motif for OpenVMS manual, but use the transport name "EXAMPLE" instead of "TCPIP".
6. Create a DECterm window on the workstation and enter the following command:

   $ SET DISPLAY /CREATE /NODE=your_node /TRANSPORT=EXAMPLE

   
   Substitute the node name of your workstation for your_node.
   Remember that the same transport must be running on both the client and server. It is not necessary, however, for the client and the server to be on the same system.

7. Run any DECwindows application from the DECterm window. It now uses the example transport to display graphics on your workstation screen. For example, enter the following command to run the clock:

   $ RUN SYS$SYSTEM:DECW$CLOCK

This chapter describes how to add (tailor on) or remove (tailor off) 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.

10.1 Using VMSTAILOR

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.)

10.1.1 How VMSTAILOR Works

VMSTAILOR has three phases:

1. VMSTAILOR asks if you want to tailor your system by adding files (tailor on) or by deleting files (tailor off).
2. If you choose to tailor files on, VMSTAILOR lists each class of OpenVMS VAX files and asks if you want to include them on the system disk. If you choose to tailor files off, VMSTAILOR lists each class of files and asks if you want to delete them from the system disk.
3. VMSTAILOR adds or deletes the files you indicated from the system disk. If you are tailoring files on, you must load your OpenVMS VAX distribution media in a drive available to the system. If your distribution media consists of more than one piece, put the first piece of the media into the drive.

The following is a list of classes and subclasses of OpenVMS VAX files that can be added or deleted by using VMSTAILOR. For a complete list of OpenVMS VAX files and their functions, refer to the OpenVMS System Manager's Manual: Tuning, Monitoring, and Complex Systems.

• Network Support
  • Incoming Remote File Access files
  • Incoming Remote Terminal files
  • Network Test files
  • Remote Task Loading
• Programming Support
  • Debugger utility (DEBUG)
  • Image Dump utility (ANALYZE/PROCESS_DUMP)
  • RMS Analyze and FDL Editor utilities (ANALYZE/RMS, ANALYZE/FDL)
  • Message utility (MESSAGE)
  • Object and Shareable Image libraries
  • MACRO libraries
  • MACRO assembler
  • SDL intermediary form of STARLET.MLB
  • Fortran required files
  • VAX C object libraries
• OpenVMS RMS Journaling Files
• System Programming Support
  • Files-11 ODS-1,ISO 9660, High Sierra ACPs
  • Monitor utility
  • Delta/XDelta debugger
  • System Dump Analyzer utility (ANALYZE/SYSTEM, ANALYZE/CRASH)
  • System Symbol Table file (SYS.STB)
  • Miscellaneous Symbol Table files
• Secure User's Environment
  • File Access Control List utilities
  • Print and Batch Queue utilities
  • Input Queue Symbiont (Card Reader)
  • Accounting Log Report Generator utility
  • DECdtm
• Utilities
  • Mail utility
  • DUMP utility
  • RUNOFF utility
  • Phone utility
  • OpenVMS Help library
  • OpenVMS System Messages Help Library
  • Foreign Terminal Support
  • LAT-11 terminal server (via Ethernet)
  • Standalone BACKUP
  • Error Log Report Generator utility (ANALYZE/ERROR)
  • DECTPU utility
  • Terminal Fallback facility
  • TECO editor
  • EDT documentation
  • National Character Set utility (NCS)
• VMS Workstation Support (VWS)
  • Workstation device support
• BLISS require files
• Miscellaneous Files
  • System map
  • LPA-11 support
• User Environment Test Package
• Example Files

To remove unwanted files using VMSTAILOR, perform the following steps:

1. Log in to the SYSTEM account.
2. Enter the following command and press Return:

   $ RUN SYS$UPDATE:VMSTAILOR

   
   VMSTAILOR displays a description of the VMSTAILOR program and the following message:

   Do you want to tailor files "ON" or "OFF"?

3. Enter OFF to remove unwanted files and press Return.
   The VMSTAILOR program lists each group, or class, of files and its size in blocks. Files are grouped according to their function. For example, all the files required for network support are in one class. A file class is made up of many smaller groups called subclasses. You can eliminate an entire class of files, or you can eliminate one or more of its subclasses. For example:

   CLASS - Network support Size of entire class (with subclasses): 1499 Size of common files required for any subclass: 1249 Do you wish to select the entire class (default = NO)? . . .

4. Decide which file classes or subclasses you do not need to support your system. The VMSTAILOR program displays step-by-step instructions. Follow these instructions to specify which classes or subclasses of files you want to remove.
5. VMSTAILOR deletes the files you selected and displays the names of those files. After it finishes, AUTOGEN runs automatically to make the adjustments that are necessary after system files are deleted. AUTOGEN also reboots the system.

To add optional OpenVMS VAX files that you previously removed, or that you chose not to install during the OpenVMS VAX installation procedure, do the following:

1. Log in to the SYSTEM account.
2. Load your distribution media in a drive available to the system. For example, if your distribution media is on a TK50 tape cartridge, load the first tape cartridge in a TK50 drive that is available to the system. Make sure the drive is on line and ready.
   If you are adding files from a compact disc on an InfoServer, first determine whether the SYSGEN parameter SCSNODE is defined on your system (see Section 5.5) or start the DECnet software, and then refer to step 2 of Section 7.2.
3. Enter the following command and press Return:

   $ RUN SYS$UPDATE:VMSTAILOR

   
   VMSTAILOR displays a description of the VMSTAILOR program and the following message:

   Do you want to tailor files "ON" or "OFF"?

4. Enter ON to add files and press Return.
   The VMSTAILOR program lists each group, or class, of files and its size in blocks. Files are grouped according to their function. For example, all the files required for network support are in one class. A file class is made up of many smaller groups called subclasses. You can add an entire class of files, or you can add one or more of its subclasses. For example:

   CLASS - Network support Size of entire class (with subclasses): 1499 Size of common files required for any subclass: 1249 Do you wish to select the entire class (default = NO)? . . .

5. Decide which file classes or subclasses you need to add. VMSTAILOR displays step-by-step instructions. Follow these instructions to specify which classes or subclasses of files you want to add.
6. VMSTAILOR adds the files you specified and displays the names of the files. After the files have been added, AUTOGEN runs automatically to make the adjustments that are necessary after system files are added. AUTOGEN also reboots the system.

After adding files to the system disk, apply any updates that affect them. OpenVMS VAX update procedures create a .TXT file that contains a description of patched files. This file usually has the following format: SYS$UPDATE:VMSUn06n.TXT.

For example, assume that you do not need the OpenVMS Phone utility (PHONE) and you run VMSTAILOR to remove those files. Later, you decide you want to use Phone. Run VMSTAILOR to return the Phone files to the system disk; then, apply any OpenVMS VAX update that has occurred since Version 7.2 that affected the Phone utility.

10.1.4 Sample Session

Example 10-1 shows how to add all Network Support files and selected Programming Support files to a system disk.

Example 10-1 Sample VMSTAILOR Session

$ RUN SYS$UPDATE:VMSTAILOR . . . Do you want to tailor files "ON" or "OFF"? ON TAILOR-ON --------- You will now be prompted with a list of the classes and subclasses of OpenVMS VAX files that are optional. The size of each class and subclass is included in the list. This will help you decide whether or not you want to add a class or subclass to your system. Under some classes, there is a set of common files that is required in order for any subclasses to work. These files are added when you ask for either the entire class or any of its subclasses. Total size of the system disk is 2376153 blocks. Total space used on the system disk is 2241252 blocks. Total space left on the system disk is 134901 blocks. CLASS - Network support Size of entire class (with subclasses): 1499 Size of common files required for any subclass: 1249 Do you wish to select the entire class (default = NO)? YES CLASS - Programming Support Size of entire class (with subclasses): 14706 Size of common files required for any subclass: 0 Do you wish to select the entire class (default = NO)? Do you wish to select any of its subclasses (default = NO)? )YES Select the subclasses that you wish to provide: SUBCLASS - Debugger utility (DEBUG) (4690 blocks) [NO]: YES SUBCLASS - Image Dump utility (ANALYZE/PROCESS_DUMP) (48 blocks) [NO]: YES SUBCLASS - RMS Analyze and FDL Editor utilities (ANALYZE/RMS, ANALYZE/FDL)- (374 blocks) [NO]:YES SUBCLASS - Message utility (MESSAGE) (49 blocks) [NO]: SUBCLASS - Object and Shareable Image libraries (4311 blocks) [NO]: YES SUBCLASS - Macro libraries (2293 blocks) [NO]: SUBCLASS - Macro assembler (457 blocks) [NO]: SUBCLASS - SDL intermediary form of STARLET.MLB (1957 blocks) [NO]: SUBCLASS - FORTRAN require files (51 blocks) [NO]: SUBCLASS - VAX-C object libraries (471 blocks) [NO]: CLASS - RMS journaling files Size of entire class (with subclasses): 155 No subclasses in this tailor class. Do you wish to select the entire class (default = NO)? CLASS - System programming Support Size of entire class (with subclasses): 2286 Size of common files required for any subclass: 93 Do you wish to select the entire class (default = NO)? Do you wish to select any of its subclasses (default = NO)? CLASS - Secure User's Environment Size of entire class (with subclasses): 919 Size of common files required for any subclass: 0 Do you wish to select the entire class (default = NO)? Do you wish to select any of its subclasses (default = NO)? . . . Files have been selected Do you wish to add all of the options selected? YES Creating temporary command file, please wait... * Enter device containing OpenVMS distribution media: mua0: . . .

10.2 Using DECW$TAILOR

You can use DECW$TAILOR to add or remove some or all DECwindows X11 display server, base support, and fonts files from the system disk. For example, if you are not planning to use the DECwindows PEX (PHIGS Extensions to X) support, you can remove those files. Later, if you decide you want DECwindows programming support, you can add the files to the system disk using DECW$TAILOR and your DECwindows distribution media. You cannot tailor files on or off an alternate device.

DECW$TAILOR has three phases:

• DECW$TAILOR asks if you want to tailor your system by adding files (tailor on) or by deleting files (tailor off).
• If you choose to tailor files on, DECW$TAILOR lists each class of DECwindows files and asks if you want to include them on the system disk. If you choose to tailor files off, DECW$TAILOR lists each class of DECwindows files and asks if you want to delete them from the system disk.
• DECW$TAILOR adds or deletes the files you indicated from the system disk. If you are tailoring files on, you must load your DECwindows distribution media in a drive that is available to the system. For example, if your OpenVMS VAX distribution kit is on a TK50 tape cartridge, load the second tape cartridge, which contains the DECwindows support files, into a TK50 drive that is available to the system.

The following is a list of classes and subclasses of DECwindows files that you can add or delete using DECW$TAILOR. For a list of DECwindows files and their functions, see Appendix E.

• DECwindows base support files --- If you plan to install the separate DECwindows Motif for OpenVMS VAX layered product, you must add the base support files.
• DECwindows workstation support files --- If you are installing DECwindows support on a workstation or in a cluster that includes workstations or if you intend to install the DECwindows Motif for OpenVMS VAX layered product, you need the workstation support files. Otherwise, you do not need them.

  Note If you tailor device support files ON or OFF, the system reboots.

• 100 dots/inch video font files --- By default, some workstation monitors (for example, a VR150, VR160, or VR295) display 100 dots/inch, which gives you a more readable display when you run DECwindows applications. If your workstation monitor cannot display 100 dots/inch fonts (for example, a VR260 or VR290), you can save disk space by not selecting this option. For more information about the capabilities of your particular monitor, refer to the owner's guide for your monitor.
• 75 dots/inch video font files --- If your workstation monitor cannot display 75 dots/inch, you can save disk space by not selecting this option. For more information about the capabilities of your particular monitor, refer to the owner's guide for your monitor.

	privacy and legal statement
6521PRO_013.HTML