DIGITAL TCP/IP Services for OpenVMS Client Components Configuration Menu Configuration options: 1 - FTP Disabled 2 - LPR/LPD Disabled 3 - NFS Client Disabled 4 - REXEC and RSH Disabled 5 - RLOGIN Disabled 6 - SMTP Disabled 7 - TELNET Disabled A - Configure options 1 - 7 [E] - Exit menu Enter configuration option: A [Return]

Enable the client components you plan to use, or enter option A to configure options 1 through 7. The following FTP client script is an example of the display for each client component:

FTP CLIENT Configuration Service is not enabled. FTP CLIENT configuration options: 1 - Enable service on this node [E] - Exit FTP_CLIENT configuration Enter configuration option: 1 [Return] The FTP SERVER is enabled. * Do you want to configure the FTP SERVER [NO] ? [Return]

After you configure the client components (and their related server components, if applicable), the Server Components menu is displayed:

DIGITAL TCP/IP Services for OpenVMS Server Components Configuration Menu Configuration options: 1 - BIND Disabled 2 - BOOTP Disabled 3 - TFTP Disabled 4 - FTP Disabled 5 - LPR/LPD Disabled 6 - NFS Disabled 7 - PC-NFS Disabled 8 - PORTMAPPER Disabled 9 - TELNET/RLOGIN Disabled 10 - SNMP Disabled 11 - NTP Disabled 12 - METRIC Disabled 13 - POP Disabled 14 - FINGER Disabled 15 - RMT Disabled 16 - LBROKER Disabled 17 - DHCP Disabled A - Configure options 1 - 17 [E] - Exit menu Enter configuration option: A [Return]

Enable the server components you plan to use, or enter option A to configure options 1 through 17.

The following BIND server configuration script is an example of a display for server components, although some components prompt you for additional information.

BIND SERVER Configuration Service is not defined in the SYSUAF. Service is not defined in the TCPIP$SERVICE database. Service is not enabled. BIND SERVER configuration options: 1 - Enable service on this node [E] - Exit BIND configuration Enter configuration option: 1 [Return] The TCPIP$AUX identifier already exists with value 3655. Checking for BIND template files in SYS$SPECIFIC:[TCPIP$BIND] Creating template SYS$SPECIFIC:[TCPIP$BIND]TCPIP$BIND_CONF.TEMPLATE Creating file SYS$SPECIFIC:[TCPIP$BIND]127_0_0.DB Creating file SYS$SPECIFIC:[TCPIP$BIND]ROOT.HINT

After you configure the server components, press Return to go to the main Configuration menu. Enter option 4, Optional Components.

3.2.5 Configuring the Optional Components

You may need to configure optional product components if you plan to do one or more of the following:

• Run PATHWORKS or DECnet over TCP/IP.
• Run or develop applications that use the Stanford Research Institute's (SRI) QIO application programming interface (API).
• Allow Anonymous FTP access.

When you enter option 4 from the Main Configuration menu, the Optional Components menu displays the following menu options:

DIGITAL TCP/IP Services for OpenVMS Optional Components Configuration Menu Configuration options: 1 - Configure PWIP Driver (for DECnet-Plus and PATHWORKS) 2 - Configure SRI QIO Interface (INET Driver) 3 - Set up Anonymous FTP Account and Directories A - Configure options 1 - 3 [E] - Exit menu

Enter the options that are appropriate for your system: the PWIP driver, the SRI QIO interface, or Anonymous FTP accounts or directories.

• If you want to run PATHWORKS or DECnet over TCP/IP, configure the PWIP driver by entering option 1.
• If you run or develop applications that use the SRI QIO API, enter option 2. Alternatively, you can load the interface by entering the following command:

  $ @SYS$MANAGER:TCPIP$LOAD_INETDRIVER

• If you want to allow Anonymous FTP access, enter option 3 to set up an Anonymous FTP account and directories. Make sure you obtain the necessary user information code (UIC; see Section 1.2.8) and determine guest user privileges.

If you are an experienced TCP/IP Services user, you may want to bypass the configuration menus to enable or disable functionality, as follows:

1. Log in to the SYSTEM account.
2. Run the command procedure and include appropriate options and keywords in the command line:

   $ @SYS$MANAGER:TCPIP$CONFIG [option] {DISABLE | ENABLE} [CLUSTER]

   
   The options and keywords are:

   ALL	Configures the core environment and all client and server components.
   CLUSTER	Configures all specified components clusterwide (except for the BIND server and SMTP, which you cannot configure clusterwide).
   CLIENT	Configures all client components and related software.
   ENABLE	Enables the specified components.
   DISABLE	Disables the specified components.
   MINIMUM	Configures the domain, Internet interfaces, remote login, FTP client, FTP server, TELNET client, and TELNET server.
   SERVER	Configures all server components and related software.
   WORKSTATION	Configures the BIND resolver, the domain, dynamic routing, Internet interfaces, time zone, remote login, remote shell, remote executive, FTP client, FTP server, TELNET client, TELNET server, and SMTP.

   
   For example, the following command enables the client components for the entire cluster:

   $ @SYS$MANAGER:TCPIP$CONFIG CLIENT ENABLE CLUSTER

   Note The procedure implements two levels of enabling and disabling: clusterwide and single node (except for the BIND server and SMTP, which are configured and enabled as node-specific only).

You must start TCP/IP Services after you configure the standard software and optional components, but before you run tests or customize the environment.

Start TCP/IP Services on your system as follows:

1. Access the main Configuration menu:

   $ @SYS$MANAGER:TCPIP$CONFIG

2. Enter option 6 (Startup DIGITAL TCP/IP Services for OpenVMS).

You can verify the configuration by running the installation verification procedure (IVP).

You should run the IVP if the following apply:

• You loaded the Product Authorization Key (PAK), and you want to verify that the lower-layer software and the Portmapper service are installed correctly.
• You did not load the PAK, but you want to verify that TCP/IP Services is installed correctly for DECwindows to display the TCP/IP Services applications.
• You require the software to transfer device socket packets that continuously vary in size between a sender and a receiver.
• You need to test the Portmapper service with a pair of client/server programs. The IVP reports the time it took to run the test to SYS$OUTPUT.

Before you run the IVP, make sure TCP/IP Services has started and you have SYSPRV, OPER, NETMBX, and TMPMBX privileges.

Run the IVP as follows:

1. Run the command procedure:

   $ @SYS$MANAGER:TCPIP$CONFIG

2. Enter option 7 (Run tests), and then enter option 1 (Internet IVP) from the Test menu. If the IVP does not complete successfully, the procedure displays error messages. All IVP errors use the same format as OpenVMS system messages. For example:

   %TCPIP-E-IDENT, explanation of error.

   
   Table 3-2 lists some common problems that cause IVP error messages. If the recommended action does not correct the problem, contact your Compaq support representative.

   Table 3-2 Troubleshooting IVP Errors

   Problem	Corrective Action
   Network configuration is incorrect.	Shut down TCP/IP Services and rerun the configuration procedure.
   Startup fails.	Check the system parameters in the MODPARAMS.DAT file and adjust them if necessary. (See Section 1.2.7.) Shut down and restart TCP/IP Services.
   The installation kit is defective.	Request a replacement kit.
   The IVP fails because the PAK is missing.	Register a DIGITAL TCP/IP Services for OpenVMS PAK.

3. To run the IVP any time after exiting the configuration procedure, run the IVP command procedure as follows:

   $ @SYS$TEST:TCPIP$IVP

After you run TCPIP$CONFIG and enable the functionality and components appropriate for your network, you need to complete additional configuration tasks to enable access to product applications. TCP/IP Services provides a management command interface and logical names you can use to modify or customize the software for your environment.

The additional configuration tasks include:

• Populating databases (for example, for BIND and DHCP)
• Setting up user accounts
• Setting up communication and NFS proxies
• Defining print queues
• Setting up, exporting, and maintaining file systems
• Tuning the system for optimum performance

For information about these and other configuration tasks, see the DIGITAL TCP/IP Services for OpenVMS Management guide.

3.7 Automatically Starting and Stopping TCP/IP Services

To allow TCP/IP Services software to start automatically when the system starts up and to stop automatically when the system shuts down, edit the SYS$COMMON[SYSMGR]:SYSTARTUP_VMS.COM file and include the following commands:

@SYS$STARTUP:TCPIP$STARTUP @SYS$STARTUP:TCPIP$SHUTDOWN

Because the UCX$STARTUP.COM and UCX$SHUTDOWN.COM files are no longer applicable, delete any definition of them from SYS$COMMON[SYSMGR]:SYSTARTUP_VMS.COM.

For TCP/IP Services to start after you log in to your OpenVMS account, the OpenVMS systemwide login procedure (typically SYS$MANAGER:SYLOGIN.COM) must have World read and execute protections (W:RE).

To display the current protections, enter:

$ DIRECTORY SYS$MANAGER:SYLOGIN.COM /PROTECTION

If the protections are not W:RE, enter:

$ SET PROTECTION=(W:RE) SYS$MANAGER:SYLOGIN.COM

3.8 Specifying TCP/IP Services as the Transport for DECwindows Applications

To enable TCP/IP Services as the transport interface for DECwindows applications, add the following line to the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM command procedure:

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

Then restart DECwindows:

$ @SYS$STARTUP:DECW$STARTUP RESTART

If DECnet or DECnet-Plus software runs on the system, start it.

To display DECwindows applications from a DECwindows client (remote host) to a DECwindows server (your workstation), proceed as follows:

1. Set up security on the remote host.
2. Add the remote client to the local hosts database.
3. Add the following line to SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM:

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

4. Set the display for the applications to the remote host:

   $ SET DISPLAY/CREATE/NODE=remote_host/TRANSPORT=TCPIP