HP OpenVMS Systems Documentation

Compaq TCP/IP Services for OpenVMS
Release Notes

$ @SYS$STARTUP:TCPIP$LPD_STARTUP.COM 

Table 1-3 lists the LPD logical names and the associated options in the TCPIP$LPD.CONF file.

Table 1-4 describes the logical names that continue to be valid:

Table 1-5 lists the logical names that are obsolete.

This version of TCP/IP Services provides an editable text file, TCPIP$ETC:SERVICES.DAT, that allows you to associate Internet service names and aliases with the port number and protocol, in the same way that they are associated on UNIX systems using the /etc/services file. This provides network programmers with the ability to refer to services by name rather than hard-coded port numbers.

When you configure the BIND resolver using the TCPIP$CONFIG command procedure, the SERVICES.DAT file is written to the directory pointed to by the TCPIP$ETC logical name. This template file contains information about the format of the file.

The following Compaq C routines are defined to operate on the SERVICES.DAT file:

• getservbyname()
• getservbyport()
• getservent()
• setservent()
• endservent()

The getservbyname() and getservbyport() functions look first in the traditional (RMS indexed) services database that is referenced by the TCPIP$SERVICE logical name. If the requested service is not found there, TCPIP$ETC:SERVICES.DAT is searched before returning an error to the caller.

The NFS server and the NFS client support OpenVMS extended file specifications (EFS) on ODS-5 disk volumes.

You can use NFS server to export files on OpenVMS ODS-5 volumes. The traditional ODS-2 volumes continue to be supported. The NFS client can emulate an ODS-5 volume.

Note that the NFS server and NFS client support the ISO Latin-1 character set only.

If an ODS-5 volume is mapped and exported, the NFS server automatically supports EFS features and ignores the NAME_CONVERSION option if it is specified in the export record.

On ODS-2 volumes (with or without the NAME_CONVERSION option), files with all uppercase names are displayed on non-OpenVMS clients with all lowercase letters. On ODS-5 volumes, the file names are displayed by clients in the same case as they are displayed locally on the server host.

If an ODS-2 volume contains file names that were created using the NFS NAME_CONVERSION option and include lowercase or special characters that are invalid for ODS-2 file names, those file names displayed locally on the server host contain escape codes, as described in the Compaq TCP/IP Services for OpenVMS Management manual. If a SET VOLUME /STRUCTURE_LEVEL=5 command is performed on this volume, the names are displayed by clients with the escape codes exactly as they are displayed locally on the server host.

1.10.1 Enabling Extended File Specifications

Extended file specifications are provided by the ODS-5 file system. To mount an ODS-5 volume, add the /STRUCTURE=5 qualifier to TCP/IP management command MOUNT. For example:

$ TCPIP 
TCPIP> MOUNT DNFS0: BOOK1 BEATRICE - 
_TCPIP> /PATH="/INFERNO" /HOST="FOO.BAR.EREWHON" - 
_TCPIP> /STRUCTURE=5 /SYSTEM 

The /STRUCTURE qualifier accepts the following values:

• 5 to indicate ODS-5
• 2 to indicate ODS-2 (the default)

For more information about the MOUNT/STRUCTURE command, display the online Help by entering the following command:

TCPIP> HELP MOUNT/STRUCTURE 

$ SHOW DEVICE/FULL 
...
Disk DNFS1:, device type Foreign disk type 7, is online, mounted, 
file-oriented device, shareable, accessed via DFS 
...

If you do not include the /STRUCTURE qualifier on the MOUNT command, the NFS client assumes that the file system structure being accessed is an ODS-2 volume. You can change this default by defining the following logical name:

TCPIP$NFS_CLIENT_MOUNT_DEFAULT_STRUCTURE_LEVEL 

You can use this logical name to ensure that all NFS disks on the system have ODS-5 support enabled. Set the value of the logical to 2 for ODS-2 (the default), or 5 for ODS-5. To override this logical, include the /STRUCTURE qualifier to the TCP/IP management command MOUNT.

The NFS client supports the extended character set supported by the OpenVMS operating system. The NFS client does not support NUL (ASCII 0). The length of a file name is limited to 232 characters, including the file name, dot, file extension, semicolon, and version number.

Refer to the OpenVMS product documentation for more information about extended file specification support.

1.11 FTP Server and FTP Client Support for UNIX Path Names (Alpha Only)

The FTP server and the FTP client have been enhanced to support UNIX path names. The FTP client can be used to access files using UNIX paths, and the FTP server can interpret the path names.

1.11.1 Specifying UNIX Path Names with FTP

For ODS-5 volumes, the FTP client and FTP server accept a path name argument in UNIX format. The following FTP commands accept UNIX path names:

• APPEND
• DELETE
• DIRECTORY
• GET
• PUT
• RENAME
• VIEW

For display, most UNIX path names are translated to OpenVMS format (for example, with the DIRECTORY command). However, UNIX path names are not translated to OpenVMS format in the following type of message:

150 Opening data connection for file-name IP-address

For the FTP client and server to support these ODS-5 features, the Compaq C shareable library (SYS$SHARE:DECC$SHR.EXE) must be updated to an ECO built after October 2000, including:

• VMS712_ACRTL-V0200
• VMS721H1_ACRTL-V0200
• VMS721_ACRTL-V0300
• VMS73_ACRTL-V0100

The following list describes the way certain characters are handled on ODS-5 volumes.

• All characters supported by ODS-5 volumes are valid. When you specify files in UNIX format, do not use the caret (^) escape character to quote special characters. For example, specify funny[path name.txt.bkp;1 , not funny^[path name^.txt.bkp;1 .
• The question mark (?) and asterisk (*) characters are interpreted as UNIX wildcard characters. OpenVMS interprets these characters as single-character wildcard characters. The OpenVMS command interpreter accepts the percent sign (%) in the same way. However, the percent sign is a valid UNIX file name character.
• UNIX regular expressions (enclosed in brackets ([...])) are not supported.
• In some cases, specifying a file name (the portion of the path after the final slash) with a dot may be ambiguous (for example, ls wow/my.file ).
• When the tilde (~) and slash (/) characters are specified alone, the OpenVMS system processes them as equivalent to SYS$LOGIN. However, a specification such as ~/x.x is not valid.
• When you copy a file to or from the OpenVMS FTP server, the character string .. (as used, for example, in the UNIX command cd .. ) is interpreted by the OpenVMS FTP server as [-] . Similarly, the character string . is interpreted as [] .
  Note, however, that character strings [-] and [] are not valid directory specifications on a UNIX server. These characters are interpreted by the UNIX server as file name characters.
• For the following commands, quotation marks are required around path names that start with a slash:
  • APPEND
  • CLOSE
  • DELETE
  • DIRECTORY
  • GET
  • PUT
  • VIEW
• Specifying a dot in the path name when the dot is intended to indicate the OpenVMS subdirectory can lead to indeterminate results.
• OpenVMS logical names are often specified with a trailing colon (for example, SYS$HELP:); however, this format can lead to problems with ODS-5 volumes. For example, my$topdir/subdir is interpreted as [.mytopdir.subdir] ; it will not be interpreted as my$topdir:[subdir] .
  To specify a logical name for a directory name, include a leading slash character and enclose the directory name in quotation marks.

The TCP/IP Services software allows you to configure and manage network services that are not supplied with the TCP/IP Services software (user-written services). The following sections provide information about managing user-written services.

1.12.1 Starting and Stopping User-Written Services

TCP/IP Services supplies command procedures for starting and stopping user-written services. To start a user-written service, enter the following command:

$ SYS$STARTUP:TCPIP$CUSTOMER_SERVICE_STARTUP service-name

For service-name, specify the name of the service as defined using the TCP/IP management command SET SERVICE.

To stop the user-written service, enter the following command:

$ SYS$STARTUP:TCPIP$CUSTOMER_SERVICE_SHUTDOWN service-name

This section describes how to configure user-written services to use both TCP and UDP protocols. Use the TCP/IP Services management command SET SERVICE to configure the protocols for services.

You must enter a separate SET SERVICE command for each protocol. Follow these steps:

1. Set up the service using the following command:

   $ TCPIP TCPIP> SET SERVICE service-name /PROTOCOL=TCP - _TCPIP> /USER_NAME=user-name /PROCESS_NAME=process - _TCPIP> /PORT=port-number /FILE=startup-file

   
   where:
   • service-name is the name of the user-written service you are adding.
   • user-name is an OpenVMS user account name defined in the SYSUAF file.
   • process is the name of the service's process.
   • port-number is the service's port number.
   • startup-file is the service's startup file specification.
2. To add the UCP protocol, enter a second SET SERVICE command. Include the /PROTOCOL=UCP qualifier, and repeat the following required information from the first SET SERVICE command:
   • The service name (the command parameter)
   • OpenVMS user account name (the /USER qualifier)
   • The service's process name (the /PROCESS_NAME qualifier)
   • The service's port number (the /PORT qualifier)
   • The service's startup file specification (the /FILE qualifier)
   • The service's internet address, if the service is bound to a particular internet address (the /ADDRESS qualifier)

For more information about the SET SERVICE command, access online help by entering the following command:

TCPIP> HELP SET SERVICE 

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

2.1 Configuring IPv6

The following sections describe procedures specific to systems where IPv6 is to be enabled.

2.1.1 Information for Users of the IPv6 Early Adopter's Kit

If you are running any version of the TCP/IP Services V5.0 IPv6 early adopter's kit (EAK), remove the EAK and then install the current version of the TCP/IP Services software. You must then run the TCPIP$IP6_SETUP.COM command procedure. For more information, refer to the Compaq TCP/IP Services for OpenVMS Guide to IPv6.

The definition of a sockaddr structure has been changed. This change breaks binary compatibility for IPv6 applications that were compiled using the TCP/IP Services Version 5.0 EAK. You must recompile and relink your applications after you install the current version of TCP/IP Services.

2.1.2 Warning Message in TCPIP$CONFIG.COM

If have run the TCPIP$IP6_SETUP.COM procedure to enable IPv6, and then you run the TCPIP$CONFIG.COM command procedure, TCPIP$CONFIG.COM displays the following warning message when you select the Core environment option:

                           WARNING 
 
This node has been configured for IPv6.  If you make any additional 
changes to the configuration of the interfaces, you must run 
TCPIP$IP6_SETUP again and update your host name information in 
BIND/DNS for the changes to take effect. 

The following sections describe product startup problems.

2.2.1 Loading the Routing Database at Startup

If the BIND resolver has been configured to point only to the local host and no host name is associated with a route entry in the local hosts database, then the loading of the permanant routes database during TCP/IP Services startup fails.

To avoid this problem, define any hosts associated with the routes database in the local hosts database before you start TCP/IP Services.

2.2.2 Startup DUPLNAM Messages

When you start TCP/IP Services, the following DUPLNAM messages may appear:

%TCPIP-E-DYNPROXERR, cannot add record to proxy database  (TCPIP$PROXY) in dynamic memory 
-SYSTEM-F-DUPLNAM, duplicate name 
%TCPIP-E-DYNPROXERR, cannot add record to proxy database  (TCPIP$PROXY) in dynamic memory 
-SYSTEM-F-DUPLNAM, duplicate name 
%TCPIP-I-LOADSERV, loading TCPIP server proxy information 
%TCPIP-I-SERVLOADED, auxiliary server loaded with 0 proxy records 
-TCPIP-I-SERVSKIP, skipped 0 communication proxy records 
-TCPIP-I-SERVTOTAL, total of 8 proxy records read 
%TCPIP-S-STARTDONE, TCP/IP Services startup completed at  7-JUN-2000 16:03:51.48 

You can ignore these messages. They are the result of a change in the current version of TCP/IP Services.

In previous versions of TCP/IP Services, the proxy database required that all names for a particular host be entered in the hosts database. For example, the host names johnws and johnws.abc.com needed to be in the hosts database if any NFS requests were made using either of the host names.

In the current release of TCP/IP Services, the proxy information that is loaded automatically includes all of a host's addresses and alias names. Therefore, the first entry for a host succeeds; any subsequent matching entries that differ only in the host's alias name generate DUPLNAM messages.

Proxy records for the host under multiple host names succeed, because all names (including the duplicates) are loaded.

There is only one record for each host. Therefore, if you remove a proxy entry under any of the host's names, all of the addresses and aliases for that host are removed. Subsequent removal attempts under any of the host's other names return an error.

2.3 System Page Table Entries Parameter (VAX Only)

On VAX systems, make sure the AUTOGEN parameter SPTREQ is set to at least 6000. Run SYSMAN to check the minimum SPTREQ value, as follows:

$ RUN SYS$SYSTEM:SYSMAN 
 
SYSMAN> parameter show sptreq 
%SYSMAN, a USE ACTIVE has been defaulted on node VMSVAX 
 
Node VMSVAX:   Parameters in use: ACTIVE 
Parameter Name    Current    Default    Minimum    Maximum Unit  Dynamic 
--------------    -------    -------    -------    ------- ----  ------- 
SPTREQ               8000       3900       3000         -1 Pages 
 
SYSMAN> 

To modify the minimum SPTREQ, run the AUTOGEN command procedure as described in the OpenVMS System Management Utilities Reference Manual: A-L. Set the minimum SPTREQ value to 6000.

2.4 Starting the Product After a Minimum OpenVMS Boot

The product configuration and startup command procedures (TCPIP$CONFIG.COM and TCPIP$STARTUP.COM) fails if you perform any kind of boot other than a full boot. Therefore, booting OpenVMS with MIN, INST, or UPGRADE is not supported.

The TCPIP$CONFIG.COM command procedure fails on systems that do not have a SYSUAF database and a RIGHTSLIST database. These OpenVMS files must be created before you configure TCP/IP Services.

2.5 Upgrading from TCP/IP Services Version 4.x

The following sections describe actions you can take to preserve the behavior of the software when you upgrade from an older version of TCP/IP Services (UCX) to the current version.

2.6 Removing Prior Versions of this Product

This section provides important information you should review before installing the current version of TCP/IP Services.