DIGITAL TCP/IP Services for OpenVMS

Document revision date: 28 June 1999

DIGITAL TCP/IP Services for OpenVMS
Release Notes

Contents

1.9 New NTP Implementation: xNTP Version 3

This release provides a new implementation of the Network Time Protocol (NTP) based on xNTP Version 3. Version 3 retains compatibility with Version 1 and 2 servers. This means, for example, that a host running DIGITAL TCP/IP Services for OpenVMS Version 4.2 will synchronize to a host running DIGITAL TCP/IP Services for OpenVMS Version 5.0.

NTP reads the file TCPIP$NTP.CONF at startup to determine synchronization sources and operating modes. You can make run-time alterations with utility programs provided with this release. Highlights of this version include:

Query utilities
The standard query program, TCPIP$NTPQ, queries NTP servers about their current state and requests changes to that state.
The special query program, NTPDC, provides extensive state and statistics information and can be used to set configuration options at run time. Run this program in interactive mode or with command line arguments.
Authentication support
Servers involved must agree on the key identification used to authenticate messages. Keys and related information are specified in a key file.
Date and time utility
TCPIP$NTPDATE sets the local date and time by polling the specified server. Accuracy depends on the number of servers, the number of polls created each time it is run, and the interval between runs.
Run NTPDATE manually or from the host startup script to set the clock at boot time before NTP starts. NTPDATE will not set the date if NTP is already running on the same host.
Trace utility
The trace utility, TCPIP$NTPTRACE, follows the chain of NTP servers back to their master time source.

For more information about configuring and managing NTP, see the DIGITAL TCP/IP Services for OpenVMS Management guide.

1.10 New SNMP Implementation: SNMP Version 2

This release implements the community-based Simple Network Management Protocol, formally named SNMPv2c (and commonly called SNMPv2), as specified in RFCs 1901 through 1908. SNMPv2 relies on the older SNMPv1 security concept of community-based security where authentication is based on a simple, unencrypted community name.

SNMPv2 includes improvements that help networks reduce SNMP traffic overhead, make the prototol applicable to a wider variety of server and client requirements, and increase performance.

The GetBulk request allows for the retrieval of large amounts of data. Instead of issuing multiple GetNext requests, a management station can enter a single GetBulk request to obtain the entire contents of a portion of a Management Information Base (MIB), such as a routing table.
Support for 64-bit counters (through the Counter64 data type) that accommodate rapidly increasing variables, such as octet counters, in high-speed networks.
Support for the following MIB definition groups (RFC 1907) in a subagent residing in the same image as the eSNMP master agent:
snmp set system

Highlights of the SNMPv2 implementation for TCP/IP Services include:

Easy configuration through TCPIP$CONFIG.
The SNMPv2 protocol, commands, and data items specified in RFCs 1901 through 1908.
Coexistence with the SNMPv1 protocol (RFC 1908).
Implementation of the Host Resources MIB File System table (hrFSTable; RFC 1514), where applicable to OpenVMS.
New utility programs for sending and receiving trap messages (TCPIP$SNMP_TRAPSND.EXE and TCPIP$SNMP_TRAPRCV.EXE).
New preprocessed MIB definition files (.MY), a MIB converter to help you develop MIBs and subagents. The associated files are located in the [.SNMP] subdirectory of TCPIP$EXAMPLES.
New logical names for controlling timeout and iteration features in standard and extension (custom) subagents.
Additional information in log files including warning and trace messages.
An enhanced MIB browser program, snmp_request, that includes new GetBulk request functionality and an option that emulates standard mibwalk programs.
You can now enable authentication traps by issuing the management command SET CONFIGURATION SNMP/FLAGS=AUTHEN_TRAPS. To modify your existing SNMP configuration, enter the management command SET CONFIGURATION SNMP and associated qualifiers.
The standard MIB implementation is now in compliance with the SNMPv2 standard. The deprecated ARP group in MIB-II is no longer supported and the sysORTable is now implemented.
The Chess example subagent code and build procedures have been improved.
You can now use SNMPv2 features when you build custom extension subagents, and you can include the subagents in the standard SNMP startup and shutdown procedures.
Logging and other messages have been improved to be more helpful for problem resolution.

For more information about SNMP files, programming, logical names, and configuration, see the DIGITAL TCP/IP Services for OpenVMS Management guide.

1.11 Support for OpenVMS External Authentication

Only the FTP and REXEC facilities support OpenVMS external authentication (described in the OpenVMS Version 7.1 New Features manual). Previously, a user would need to log into the OpenVMS system after changing passwords to use the new password with FTP or REXEC.

When using OpenVMS external authentication support:

REXEC now requires the use of uppercase user names on all versions of OpenVMS
FTP requires the use of uppercase user names on OpenVMS Version 7.1.

1.12 New TELNET Port Driver QIO Interface

The TELNET port driver (TNDRIVER) provides terminal session support for TCP/IP stream connections using the following protocols: RAW, NVT, RLOGIN, and TELNET. Either a remote device or application can be present at the remote endpoint of the connection.

A user program can manage a TELNET connection via the standard OpenVMS $QIO system service using the IO$_TTY_PORT and the IO$_TTY_PORT_BUFIO function codes. Chapter 4 describes these function codes and their arguments.

1.13 Enhanced Error Messages

In this release, the product's error messages have been enhanced as follows:

Improved message text corrects errors and provides clearer descriptions and user action.
A consolidated message file converts several individual files to one centralized message database simplifying language translation efforts (internationalization and localization support).
Redundant and obsolete messages have been removed.

Note

These enhancements will cause the numeric values assigned to messages (for example, $STATUS) to change.

1.14 New TCP/IP Message Database Available for Help Message

With Version 5.0, you can display online information about a number of TCP/IP Services messages through the OpenVMS centralized Help Message utility (MSGHLP).

When you type a command on the terminal or execute an image that results in an error, Help Message translates the value stored in $STATUS and displays it when you enter the HELP/MESSAGE command.

For example, if you enter an invalid keyword to the DCL command SHOW, an error message is displayed. You can obtain further information about the message by issuing the command HELP/MESSAGE.

$ TCPIP SET HOST MOLLY %TCPIP-E-HOSTERROR, cannot process host request -TCPIP-E-INSKEY, insufficient information $ HELP/MESSAGE INSKEY INSKEY, insufficient information Facility: TCPIP, Management Control Program Explanation: You attempted to enter a record into a database, but you did not specify enough information. User Action: Reenter the command with the necessary qualifiers.

With Help Message, you can also:

Obtain message information by issuing keywords and partial information
Move message databases to new locations
Delete messages from any database to conserve space
Add comments to Compaq supplied messages
Create new databases
Define search and accessibility paths so that different levels of users can access appropriate databases

Note

To use the HELP/MESSAGE function for TCP/IP Services, it is necessary to have started TCPIP at least once.

To access the TCP/IP Services HELP/MESSAGE database before the product starts, define the logical name MSGHLP$LIBRARY.

1.15 Installation Change (VAX Only)

The VMSINSTAL procedure is no longer used to install the product on VAX systems. The POLYCENTER Software Installation Software (PCSI) is now used for both Alpha and VAX systems.

1.16 Cluster Alias Handling

The TCP/IP Services product still supports setting up ARP-based cluster aliases using the /CLUSTER qualifier on the SET INTERFACE command. Expanded internal logic has been added to handle these aliases in the environment of the new protocol stack. Although the ARP-based alias feature remains available, its implementation is slightly different.

In previous versions, it was possible for an application to bind a socket to the cluster alias address even when the host involved was not the cluster impersonator. This sometimes led to unexpected behavior and is no longer permitted. Similarly, when a user initiated a TCP connection to the cluster alias address from any alias participant, that connection would loop back to the local node, even when that node was not the impersonator. For this version of the product, we have eliminated such confusion by configuring the alias IP address in the protocol stack only upon becoming the impersonator.

1.17 Timezone Configuration

In this release, the TCP/IP Services product uses the system service SYS$GETUTC() to find the timezone differential information used by the operating system. TCPIP$CONFIG automatically verifies the timezone information in this way; no user input is required.

In prior releases, the startup procedure set the output logical name MCC_TDF and set timezone information with the logical names UCX$TZ, UCX$NTP_TZ, and UCX$TDF. Corresponding logical names do not exist in the Version 5.0 release. TCPIP$STARTUP.COM no longer sets the MCC_TDF logical name.

Universal Coordinated Time (UTC) must be configured on the system or TCP/IP Services applications may report incorrect times. The OpenVMS System Management documentation describes how to set and show UTC information.

The SET CONFIGURATION and SHOW CONFIGURATION TIME commands continue to operate (for compatibility with command files) but the values set and displayed with these commands are no longer used by the TCP/IP Services product. These commands may be removed in a future version of the product. The TIMEZONE entry in TCPIP$CONFIG.COM is also retained for compatibility with previous versions of the TCP/IP Services product.

1.18 Socket Programming Interface Enhancements

This release implements the socket programming interface (Versions 4.3 and 4.4 BSD). To access the 4.4 BSD interface, use the _SOCKADDR_LEN option.

DIGITAL TCP/IP Services for OpenVMS System Services and C Socket Programming provides more information about the socket API.

1.19 Obsolete Management Control Program Commands

The Version 5.0 product makes obsolete the management commands and command-qualifier pairs described in Table 1-2. (Related SET CONFIGURATION and SHOW commands are similarly obsolete.)

Table 1-2 Obsolete Management Control Program Commands
Command Explanation

BIND, SHOW BIND, UNBIND MAP, SHOW MAP, and UNMAP commands have replaced these commands.

SET COMMUNICATION /DEVICE_SOCKETS No longer applicable with new kernel.

SET COMMUNICATION /INTERFACES No longer applicable with new kernel.

SET COMMUNICATION /IRP New memory management in V5.0 eliminates need to set quotas for internet I/O request packets (IRPs).

SET COMMUNICATION /LARGE_BUFFERS New memory management in V5.0 eliminates the need to allocate static and dynamic buffers; memory buffers are now one size (512 bytes long).

SET COMMUNICATION /NON_UCX_BUFFERS Non-UCX buffers no longer specified in OpenVMS nonpaged pool free list.

SET COMMUNICATION /REMOTE_TERMINAL=LARGE_BUFFER No longer needed. Memory buffers are now one size (512 bytes long).

SET COMMUNICATION /REMOTE_TERMINAL=UCB No longer applicable with new kernel.

SET COMMUNICATION /REMOTE_TERMINAL=VIRTUAL No longer applicable in new kernel.

SET COMMUNICATION /ROUTES No longer applicable with new kernel.

SET COMMUNICATION /SMALL_BUFFERS New memory management in V5.0 eliminates the need to allocate static and dynamic buffers; memory buffers are now one size (512 bytes long).

SET COMMUNICATION /TYPE New memory management in V5.0 eliminates the need to specify large buffer types.

SET CONFIGURATION COMMUNICATION /ALLOW_LOG

SET CONFIGURATION COMMUNICATION /FORCE_LOG

SET CONFIGURATION COMMUNICATION /SERVICE

SET PROTOCOL ARP /CACHE No longer applicable with new kernel.

SET PROTOCOL ARP /COMPLETE_TIMER No longer applicable with new kernel.

SET PROTOCOL ARP /INCOMPLETE_TIMER No longer applicable with new kernel.

SET PROTOCOL IP /CHECKSUM No longer applicable with new kernel.

SET PROTOCOL RAW_IP /QUOTA No longer applicable with new kernel.

SET PROTOCOL TCP /CHECKSUM No longer applicable with new kernel.

SET PROTOCOL TCP /LOOPBACK No longer applicable with new kernel.

SET PROTOCOL TCP /PUSH No longer applicable with new kernel.

SET PROTOCOL UDP /BROADCAST No longer applicable with new kernel.

SET PROTOCOL UDP /CHECKSUM No longer applicable with new kernel.

ZERO INTERFACE /COUNTERS No support for zeroing kernel counters in new kernel.

**Table 1-2 Obsolete Management Control Program Commands**
Command	Explanation
BIND, SHOW BIND, UNBIND	MAP, SHOW MAP, and UNMAP commands have replaced these commands.
SET COMMUNICATION /DEVICE_SOCKETS	No longer applicable with new kernel.
SET COMMUNICATION /INTERFACES	No longer applicable with new kernel.
SET COMMUNICATION /IRP	New memory management in V5.0 eliminates need to set quotas for internet I/O request packets (IRPs).
SET COMMUNICATION /LARGE_BUFFERS	New memory management in V5.0 eliminates the need to allocate static and dynamic buffers; memory buffers are now one size (512 bytes long).
SET COMMUNICATION /NON_UCX_BUFFERS	Non-UCX buffers no longer specified in OpenVMS nonpaged pool free list.
SET COMMUNICATION /REMOTE_TERMINAL=LARGE_BUFFER	No longer needed. Memory buffers are now one size (512 bytes long).
SET COMMUNICATION /REMOTE_TERMINAL=UCB	No longer applicable with new kernel.
SET COMMUNICATION /REMOTE_TERMINAL=VIRTUAL	No longer applicable in new kernel.
SET COMMUNICATION /ROUTES	No longer applicable with new kernel.
SET COMMUNICATION /SMALL_BUFFERS	New memory management in V5.0 eliminates the need to allocate static and dynamic buffers; memory buffers are now one size (512 bytes long).
SET COMMUNICATION /TYPE	New memory management in V5.0 eliminates the need to specify large buffer types.
SET CONFIGURATION COMMUNICATION /ALLOW_LOG
SET CONFIGURATION COMMUNICATION /FORCE_LOG
SET CONFIGURATION COMMUNICATION /SERVICE
SET PROTOCOL ARP /CACHE	No longer applicable with new kernel.
SET PROTOCOL ARP /COMPLETE_TIMER	No longer applicable with new kernel.
SET PROTOCOL ARP /INCOMPLETE_TIMER	No longer applicable with new kernel.
SET PROTOCOL IP /CHECKSUM	No longer applicable with new kernel.
SET PROTOCOL RAW_IP /QUOTA	No longer applicable with new kernel.
SET PROTOCOL TCP /CHECKSUM	No longer applicable with new kernel.
SET PROTOCOL TCP /LOOPBACK	No longer applicable with new kernel.
SET PROTOCOL TCP /PUSH	No longer applicable with new kernel.
SET PROTOCOL UDP /BROADCAST	No longer applicable with new kernel.
SET PROTOCOL UDP /CHECKSUM	No longer applicable with new kernel.
ZERO INTERFACE /COUNTERS	No support for zeroing kernel counters in new kernel.

1.19.1 Command Output

Certain management commands now output UNIX style displays instead of the OpenVMS displays you may be used to seeing. For example, in previous versions, the command SHOW PROTOCOL UDP produced a display similar to the following:

UCX> SHOW PROTOCOL UDP UDP Bad header checksums: 6 Incomplete headers: 0 Bad data length fields: 0 Socket buffer drops: 0 Unknown broadcast port drops: 9881 Total received datagrams: 233066 Dropped: 0

For this release, the same command produces the following:

TCPIP> SHOW PROTOCOL UDP udp: 12272 packets sent 1126540 packets received 0 incomplete headers 0 bad data length fields 0 bad checksums 0 full sockets 1114425 for no port (1114399 broadcasts, 0 multicasts) 0 input packets missed pcb cache

1.20 FTP Enhancements

FTP now supports Extended File Specifications, including support for long file names and extended deep directories. (See the OpenVMS Version 7.2 New Features manual for more information about this OpenVMS feature.)

Support for long file names is automatically enabled in the FTP server and cannot be disabled. This behavior may be unexpected because typically, to enable long file name support, you must add a line in the file SYLOGIN.COM or LOGIN.COM for each user. If you do not require the long file names support feature, you can continue to use ODS-2 file names.

The FTP COPY and DIRECTORY commands work as expected with uppercase file names running on OpenVMS 7.1 but require OpenVMS Version 7.2, to handle file names with lowercase letters.

1.21 New Location for Startup Files

The location and name of the files invoked to activate server components has been changed to TCPIP$SYSTEM:TCPIP$component_name_RUN.COM. For example, the TFTP startup file is TCPIP$SYSTEM:TCPIP$TFTP_RUN.COM.

1.22 Changes to the TCP/IP Services Startup Procedure

The TCPIP$STARTUP.COM procedure now checks the value of the SYSGEN parameter STARTUP_P1. If it is MIN, UPGRADE, or INST, the procedure prints a message and exits immediately, setting $SEVERITY to FATAL.

The message for a MIN boot is:

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

This behavior prevents TCP/IP Services from starting when the TCPIP$STARTUP.COM procedure detects that portions of OpenVMS required for correct operation are not present.

In the usual situation where STARTUP_P1 is blank, TCPIP$STARTUP.COM will initialize the TCP/IP software.

1.23 NFS Server Changes

The following describes NFS server changes for Version 5.0:

In earlier versions on Alpha systems, the NFS server sent messages to the device specified by the logical name UCX$CFS_FATAL_MESSAGES (_OPA0, by default). This behavior has changed. On Alpha systems, messages are now sent to OPCOM. The device defined by TCPIP$CFS_FATAL_MESSAGES is used only if there is a failure on the $SNDOPR system service request.
On VAX systems, the server always sent messages to OPCOM. This behavior is now consistent across architectures.
Copying a file from an OpenVMS client to an OpenVMS server is now more efficient.
Some OpenVMS utilities, such as COPY, can determine the finished size of a file before it is created. Those utilities typically pre-extend the file to its final size and then write data sequentially into the allocated blocks without updating the end-of-file mark until the file is completely written and closed.
Earlier versions of the NFS server ignored any indication on the part of the OpenVMS client to set the allocated size any higher than the minimum needed to contain the written blocks, and it always adjusted the end-of-file mark to the highest byte written. This meant that while the client was sequentially writing the file, the server would normally have to extend the file for every write, and the server would have to update the file header with the new end-of-file mark for every write.
In Version 5.0, the NFS server pre-extends the file if the application or utility running on the OpenVMS client requests it and if TCPIP$CFS_KEEP_ALLOC is set to 1. With an OpenVMS client, the server does not update the end-of-file mark until it gets an explicit request to do so, unless the client application did not pre-extend the file. The new behavior produces a very noticeable performance improvement for pre-extended files.
Note that the OpenVMS client always reports the allocated size as equal to the used size. This means that with the Version 5.0 server, if you specify DIRECTORY /SIZE=ALL, the OpenVMS client will show both sizes as zero until the copy is completed.
The default value for TCPIP$CFS_KEEP_ALLOC is changed from 0 to 1.
With a TCPIP$CFS_KEEP_ALLOC setting of 0, whenever the server updates the file attributes, if the allocated blocks are more than needed to accommodate the location of the end-of-file mark, the extra blocks are truncated. With a TCPIP$CFS_KEEP_ALLOC setting of 1, the server never decreases the allocated size of a file.

1.24 SMTP Changes

The SMTP changes for this release are as follows:

The SMTP symbiont now exits with TCPIP$_FACNOTSTART if you try to start an SMTP queue before TCPIP$SMTP_STARTUP.COM is run.
With this release, the SMTP queue name changes from UCX$SMTP_nodnam_* to TCPIP$SMTP_nodnam_*.
The SMTP username changes from UCX_SMTP to TCPIP$SMTP. (The underbar (_) is replaced with a dollar sign ($) for consistency with other product components.)

1.25 LPD Changes

With this release, the LPD queue name changes from UCX$LPD_QUEUE to TCPIP$LPD_TCPIP$LPD_QUEUE.

The LPD username changes from UCX_LPD to TCPIP$LPD (The underbar (_) is replaced with a dollar sign ($) for consistency with other product components.)

1.26 TELNET Virtual Terminals

The command SET COMMUNICATION/REMOTE_TERMINAL=VIRTUAL is no longer available. Instead of using this command, define the following logical names with a value of TRUE to turn on the corresponding VTA support.

TCPIP$RLOGIN_VTA
TCPIP$TELNET_VTA