Document revision date: 28 June 1999

After this release, the TCP/IP Services product will no longer be distributed on TK50 tape cassettes or magnetic tape.

Use this chapter in conjunction with the manual DIGITAL TCP/IP Services for OpenVMS Installation and Configuration.

2.1 Removing Prior Versions of this Product

This section provides important information you should review before installing the TCP/IP Services Version 5.0 product.

2.1.1 VAX Systems Only

The command procedure SYS$UPDATE:UCX$CLEANUP.COM is typically used to clean up a previous version of the TCP/IP Services product. However, running this procedure when TCP/IP V5.0 is installed will remove files necessary for the operation of the product.

Compaq strongly recommends you remove this command procedure after installing the TCP/IP Services Version 5.0 kit.

2.1.2 Alpha Systems Only

Follow all installation instructions.

2.2 Some UCX Files Remain After Installation

After installing and starting the Version 5.0 product, you may notice some files with a UCX$ prefix (most other files provided by this product use the prefix TCPIP$). The existence of these files (see Table 2-1) is normal and expected. They allow for a smoother transition from UCX to TCP/IP Services Version 5.0.

Table 2-1 UCX Files Remaining After Installation

File	Description
SYS$LIBRARY:UCX$IPC_SHR.EXE	Allows the DEC C Run-Time Library (RTL) to use TCPIP sockets.
SYS$COMMON:[SYSEXE]UCX$UCP.EXE	An empty (zero block) marker file which allows some layered products which use an unsupported test for the presence of the DIGITAL TCP/IP Services for OpenVMS to continue to operate.
SYS$COMMON:[SYSEXE]UCX$SERVICE.DAT	An empty (zero block) marker file may be created if the file does not exist when TCPIP$STARTUP.COM executes. The file specified by the logical name TCPIP$SERVICE (which defaults to SYS$COMMON:[SYSEXE]TCPIP$SERVICE.DAT) contains the actual service information.
SYS$STARTUP:UCX$STARTUP.COM SYS$STARTUP:UCX$CONFIG.COM	These files print an informational message to SYS$OUTPUT, then execute the corresponding TCPIP file. This allows the DIGITAL TCP/IP Services for OpenVMS product to continue to operate until the system manager changes command files to use the new TCPIP prefix.
SYS$SYSTEM:UCX$LPD_SMB.EXE	Maintains backward compatibility for LPD print queue.
SYS$SHARE:UCX$ESNMP_SHR.EXE	Shareable image required for user-written subagents written under previous versions of the product.

2.3 Verifying the SNMP Configuration

A separate installation verification procedure (IVP) exists for SNMP. To verify your configuration, complete these steps:

1. Be sure that your process has the following privileges: TMPMBX,NETMBX,SETPRV
2. Run the command procedure:

   $ @SYS$MANAGER:TCPIP$CONFIG

3. Enter option 7 (Run tests), and then option 2 from the Digital TCP/IP Services for OpenVMS TEST Menu.
   Note that unlike the Internet IVP, the SNMPIVP requires that you shut down TCPIP/IP Services. This restriction means that it is not possible to use option A (Tests 1 - 2) in TCPIP V5.0.
4. To run the SNMPIVP any time after exiting the configuration procedure, use the following command:

   $ RUN SYS$COMMON:[SYSTEST.TCPIP]TCPIP$SNMPIVP.EXE

If you boot OpenVMS with the SYSGEN parameter STARTUP_P1 defined to something other than the default blank string, not all portions of OpenVMS may be started. A check has been added to the TCP/IP Services files SYS$STARTUP:TCPIP$STARTUP.COM to detect when OpenVMS has been booted in an alternate manner.

This check works as follows:

If the startup procedure SYS$STARTUP:TCPIP$STARTUP.COM detects a MIN, INST, or UPGRADE boot, it gives a message and exits, setting $SEVERITY to FATAL. For example, the following message is displayed if a MIN boot is detected.

%TCPIP-F-NONETSTART, Network not started due to MIN boot

This check helps ensure that conditions required for proper operation of DIGITAL TCP/IP Services for OpenVMS are met. For example, if one has installed OpenVMS and DIGITAL TCP/IP Services from a CD-ROM or an Infoserver and is still booted from that medium, the boot type will be INST. TCPIP$CONFIG cannot write configuration files to the current SYS$SYSTEM: (the CD-ROM or Infoserver device).

2.5 Misleading Screen Displays When Configuring Client Components

The configuration procedure TCPIP$CONFIG displays misleading information when you select the FTP, LPD, or NFS menu option from the Client Components menu.

For example, after selecting the FTP option from the Client Components configuration menu, the following script is displayed indicating that the FTP server is being configured:

FTP SERVER Configuration Service is not enabled FTP SERVER configuration options:

The display is misleading. The FTP client will be configured, not the FTP server.

2.6 Preserving LPD Startup and Shutdown Behavior

Your LPD startup and shutdown command procedures may contain site-specific edits. You must manually preserve these edits when upgrading to TCP/IP Services Version 5.0 from a previous version . The procedure for preserving your edits differs for OpenVMS Alpha systems and OpenVMS VAX systems. Follow the instructions below to preserve your site-specific startup and shutdown command procedure files.

2.6.1 OpenVMS Alpha Users

When you install TCP/IP Services Version 5.0 over an earlier version of the product, follow the instructions displayed on your screen to preserve your edits in the LPD startup and shutdown command procedures.

The following shows a sample screen display.

The following product will be installed to destination: DEC AXPVMS TCPIP V5.0-9 DISK$ALPHASYS:[VMS$COMMON.] UCX product already installed. *********************************************************************** Another version of TCP/IP is installed. You must execute the following three commands before continuing with this installation: $ BACKUP SYS$COMMON:[SYSMGR]UCX$LPD_STARTUP.COM; - SYS$COMMON:[SYSMGR]TCPIP$LPD_STARTUP.COM; $ BACKUP SYS$COMMON:[SYSMGR]UCX$LPD_SHUTDOWN.COM; - SYS$COMMON:[SYSMGR]TCPIP$LPD_SHUTDOWN.COM; $ PRODUCT REMOVE UCX ***********************************************************************

After following these instructions, and completing the installation of TCP/IP V5.0, your site-specific edits to the LPD startup and shutdown files are found in:

• SYS$COMMON:[SYSMGR]TCPIP$LPD_STARTUP.COM_OLD
• SYS$COMMON:[SYSMGR]TCPIP$LPD_SHUTDOWN.COM_OLD

Now merge your site-specific edits into:

• SYS$COMMON:[SYSMGR]TCPIP$LPD_STARTUP.COM
• SYS$COMMON:[SYSMGR]TCPIP$LPD_SHUTDOWN.COM

To preserve your site-specific startup and shutdown information, you must install TCP/IP Services Version 5.0 then copy the site-specific edits from:

• SYS$COMMON:[SYSMGR]UCX$LPD_STARTUP.COM
• SYS$COMMON:[SYSMGR]UCX$LPD_SHUTDOWN.COM

To the following files:

• SYS$COMMON:[SYSMGR]TCPIP$LPD_STARTUP.COM and
• SYS$COMMON:[SYSMGR]TCPIP$LPD_SHUTDOWN.COM

When merging edits, do not append the commands to start and stop the queue UCX$LPD_QUEUE. This queue has been replaced with TCPIP$LPD_QUEUE, and the commands for TCPIP$LPD_QUEUE will already be in the LPD startup and shutdown command procedure files.

After merging the edits, set the value of the /PROCESSOR qualifier in the LPD client queue startup commands that you have just appended to point to TCPIP$LPD_SMB rather than UCX$LPD_SMB.

LSE Command> SUB/ALL "ucx$lpd_smb" "tcpip$lpd_smb"

2.7 Preserving SNMP Startup and Shutdown Behavior

After you upgrade to this version of TCP/IP Services, you must perform one of the following actions to ensure correct SNMP startup:

• If SNMP had been configured under a previous TCP/IP Services installation (UCX) and you want to retain the previous configuration, run SYS$MANAGER:TCPIP$CONFIG.COM and select the option to automatically convert UCX configuration files.
• After you upgrade to this version of TCP/IP Services, run SYS$MANAGER:TCPIP$CONFIG.COM. If SNMP is still enabled, disable SNMP then enable it again. This is necessary for the proper operation of this component.

If you customized versions of the files UCX$SNMP_STARTUP.COM and UCX$SNMP_SHUTDOWN.COM (used to start and stop extension subagents), save your customized files to a different directory before upgrading to Version 5.0. If you do not perform this step, your customized changes will be lost.

After installing TCP/IP Services, manually merge your saved changes into the new files created after installation. See the DIGITAL TCP/IP Services for OpenVMS Management for more information.

2.8 Reenabling BOOTP After Configuring DHCP

To return to using BOOTP after initially configuring DHCP, perform the following steps:

1. Run TCPIP$CONFIG and select the Server menu option.
2. Select the BOOTP menu option.
3. Select Enable.

Be sure your BOOTP configuration database file (TCPIP$BOOTP.DAT) still exists.

This method leaves the DHCP files intact so you can easily return to DHCP.

2.9 Special Note for Field Test Users of GATED and DHCP

Since external field test, the location for GATED files has changed. GATED files are now located in SYS$SYSDEVICE:[TCPIP$GATED]. During field test, they were located in the directory SYS$SYSTEM.

If you have previously configured DHCP on your system, you will have invalid service database flags set for DHCP. You must manually delete the service database entry and then run TCPIP$CONFIG to recreate the entry.

1. Shut down the DHCP server. Enter:

   $ @SYS$MANAGER:TCPIP$DHCP_SHUTDOWN

2. Remove the entries for DHCP. Enter:

   $ TCPIP SET NOSERVICE DHCP

3. Run TCPIP$CONFIG. Enter:

   $ @SYS$MANAGER:TCPIP$CONFIG

   
   Select the Server components menu item, select DHCP, and enable the service for this host.

4. Exit the configuration procedure and enter the following commands to start and enable DHCP:

   $ @SYS$STARTUP:TCPIP$SERVICE_SETUP DHCP $ TCPIP ENABLE SERVICE DHCP

If you were using DHCP on multiple cluster nodes, you must repeat these steps on each system running DHCP.

2.10 Setting Up the TCP/IP Services Message Database

At installation, the TCP/IP Services database is installed at SYS$COMMON:[SYSHLP]TCPIP.MSGHLP$DATA.

To include this database with the OpenVMS message database:

1. Define the logical name MSGHLP$LIBRARY to point to all the databases in the directory:

   $ DEFINE/SYSTEM MSGHLP$LIBRARY SYS$COMMON:[SYSHLP]*.MSGHLP$DATA

2. Enter a command to make sure the TCP/IP database is now recognized. For example:

   $ HELP/MESSAGE FTP SESDCN, FTPD: Session disconnection from 'host' at 'time' Facility: TCPIP, FTP Server Explanation: This message appears when a session is disconnected, stating the name of the client initiating the disconnection and the time of the disconnection. User Action: None. Press RETURN to continue ...

   
   In this example, Help Message displays one by one, all the messages with FTP as part of the message ID.

This chapter provides general notes about changes, problems, and restrictions in DIGITAL TCP/IP Services for OpenVMS Version 5.0.

3.1 Handling Security Information (ARB Support)

The OpenVMS SYSGEN parameter ARB_SUPPORT is new in OpenVMS V7.2. For the TCP/IP Services product to operate properly, this value must be greater than or equal to 2. The file SYS$STARTUP:TCPIP$STARTUP.COM checks this value when the product is started. If the value is not within the required range, the file gives a message and exits, setting $SEVERITY to FATAL.

For example, for a value of ARB_SUPPORT of 0, one would see:

%TCPIP-F-NONETSTART, Network not started _TCPIP-F-UNSUPPORTED, sysgen parameter ARB_SUPPORT value 0 < required mininum 2

This restriction allows the proper handling of security information and prevents unpredictable system operation.

3.2 Cluster Timer Not Supported

For this release, the cluster timer command SET COMMUNICATION /CLUSTER_TIMER is not supported. Once a cluster member becomes the impersonator, it will remain the impersonator until TCP/IP is shut down or the system crashes.

3.3 Zeroing TCP/IP Counters

In the V5.0 release, there is no support for zeroing counters. In previous releases, this was accomplished with the ZERO INTERFACE /COUNTERS command.

If you want to see change over a period of time, you must take a snapshot with a timestamp, wait, take another snapshot with a timestamp and compare the difference.

3.4 Security Driver

Support for the security driver is no longer available.

3.5 Management Control Program

The management control program provides a command line interface for managing the TCP/IP Services environment. Type the DCL command TCPIP to access the management control program and enter commands.

3.5.1 Command Output Changes and Customer-Developed Command Procedures

Because certain management commands now output UNIX style displays, any customer-developed command procedures that parse command output will not work.

3.5.2 Command Restrictions

The following restrictions apply:

• SET INTERFACE /CLUSTER
  You must set the cluster network mask and cluster broadcast masks at the same time you define a cluster alias with the SET INTERFACE /CLUSTER command. In earlier releases, you could add or modify the network and broadcast masks after defining the alias name.
• SET INTERFACE PPn
  The /HOST qualifier is now required when setting up a PPP interface. This qualifier was optional in the previous release.
• Miscellaneous problems with commands
  When troubleshooting any problems you encounter using TCP/IP Services applications (for example, FTP, RSH, or TELNET), check to see if the network software or the application has been started. The error messages you receive may be misleading in that they do not indicate the network is not running.
• SET INTERFACE
  If you fail to enter all of the required parameters and qualifiers with the SET INTERFACE command, the management control program may behave in an unexpected manner. To correct any problems, exit the management control program, restart, and reenter the SET INTERFACE command.
• SHOW INTERFACE
  The SHOW INTERFACE command displays an incorrect MTU value. The correct value can be obtained by entering the UNIX command ifconfig -a.
• SET NAME_SERVICE /PATH
  This command required SYSNAM privilege. If you enter the command without the appropriate privilege at the process level, the command will not work but you will not be notified. If you enter the command at the system level, the command will not work but you will receive an error message.
• SET SERVICE command
  When you modify parameters to a service, disable and reenable the service for the modifications to take effect.
• DISABLE SERVICE command
  Except for TELNET and RLOGIN, this command disables the specified service but does not stop the current process if one exists.
  To stop and restart the current process:
  1. Wait until the process exits or stop it with the DCL command STOP PROCESS /ID=n.
  2. Enter an ENABLE SERVICE command.
  3. Run the startup command procedure.
  
  For TELNET and RLOGIN, this command stops the current process.
  Do not use this method with DHCP. Instead, issue DHCPSIGTERM (defined in SYS$MANAGER:TCPIP$DHCP_SETUPCOMMANDS.COM). See the DIGITAL TCP/IP Services for OpenVMS Management guide for more information.
• TRACEROUTE does not work from the management control program. To use this UNIX utility, run the command procedure SYS$MANAGER:TCPIP$DEFINE_COMMANDS.COM and run TRACEROUTE at the DCL prompt.

A host running the TCP/IP Services NTP cannot receive broadcast or multicast messages from an NTP server. This problem does not affect the host's ability to send broadcast or multicast messages to NTP clients.

In this release, the NTP server has a stratum limit of 15. It will not synchronize to any time server that reports a stratum of 15 or greater. This may cause problems if you try to synchronize to a server running the UCX NTP server, if that server has been designated as "free-running" (with the 'local-master' command). For proper operation in such a case, the 'local-master' designation must be specified with a stratum no greater than 14.

3.7 Error Messages

Some error messages may contain extra blank lines.

$ ftp xxx %TCPIP-E-FTP_HSTINF, cannot get host information for XXX from database -RMS-E-RNF, record not found $

3.8 FTP Problems and Restrictions

This section describes FTP problems and restrictions.

3.8.1 GET/FDL Command

When connected to a system that is not running OpenVMS, the following command fails:

FTP> GET/FDL a/b/c.d

In error, FTP attempts to return the file /FDL.

The workaround to this problem is to enter the command using the following sequence:

FTP> cd a/b/ FTP> GET/FDL c.d

3.8.2 Window Size Logical Name No Longer Defined

The FTP client and server no longer define the logical name TCPIP$FTP_WNDSIZ when TCPIP$STARTUP.COM is executed. This change allows FTP to take advantage of the larger default TCP window size in TCP/IP Services Version 5.0.

If the logical name is defined, the FTP client and server use that value, within the bounds (approximately 1K to 64K).

Lowering the value of TCPIP$FTP_WNDSIZ might be useful with low-speed or error-prone transmission media, or both.

The current default values are approximately half the default value for TCP/IP Services Version 4.2 in VMS_Plus mode and approximately four times greater otherwise. This change should be transparent to most users. However, users who perform transfers between OpenVMS systems and systems that are not running OpenVMS over poor-quality network links should monitor performance after upgrading to TCP/IP Services Version 5.0.

3.8.3 Extended File Specifications in a Mixed Operating System Environment

With FTP, file names must be valid on the target operating system. It may help to clarify this requirement in the context of Extended File Specification names when certain characters in a file name must be escaped.

For example, the file A^;b.Dat;3 requires a caret escape before the left semicolon. The transfer and display of this file name between systems running OpenVMS Version 7.2, with process-parse style enabled and referencing an ODS5 disk, exhibits expect behavior. The file is displayed as A^;b.Dat;3, and the following command results in the file A^;b.Dat; on the local system:

FTP> get A^;b.Dat

The number to the right of the ending semicolon varies depending on the version of any previously existing files of that name in the directory.

When operating between an OpenVMS system and a system that is not running OpenVMS, the the FTP server displays the file as A^;b.Dat.3 (.3 rather than ;3).

When entering a GET command for a file A;b.Dat from a UNIX system, for example, you must specify the carets in the output specification:

FTP> GET A;b.Dat A^;b.Dat

The following command results in a file specification error:

FTP> GET A;b.Dat

When entering a PUT command, you must manually remove the caret escapes from the output specification:

FTP> PUT A^;b.Dat A;b.Dat

	privacy and legal statement
6551_002.HTML