HP OpenVMS Systems Documentation

Compaq TCP/IP Services for OpenVMS
Release Notes

The FTP program is updated with the following corrections:

• The FTP commands ls and directory did not display files recursively. (That is, the contents of subdirectories were not displayed.)
  To activate recursive displays of directory contents, define the following logical name at the system level:

  $ ASSIGN/SYSTEM 1 TCPIP$FTPD_DIR_RECURSIVE

  
  On OpenVMS Version 7.2, if the file specification includes the path name preceding the file name and also contains a wildcard character, the directory listing is recursive.
  The top-level directory is always included in the display except when input file names do not contain a path, include a wildcard character, and end with a backslash (\) character.
• On systems with Version 7.2 of the Compaq C shareable library (DECC$SHR.EXE), the following commands failed to set the local default if the subdirectory had been assigned a logical name:

  $ SHOW LOGICAL NEW "NEW" = "MYNEW" (LNM$PROCESS_TABLE) $ FTP FTP> lcd new %TCPIP-E-FTP_NOSUCHFILE, no such file new: %Failed to set default directory to [.new:] Local directory now SYS$SYSROOT:[SYSMGR]

Compaq uses the Integrated Problem Management Tool (IPMT) to track problems reported by customers. When a problem report is created, it is given a unique identification number starting with "CFS." When the problem is logged for engineering attention, it receives a Problem Tracking Report (PTR) number.

This section describes problems that have been reported and corrected in this release of TCP/IP Services, including the CFS and PTR numbers for each.

Table 4-1 describes the customer-reported problems that have been corrected in the BIND resolver.

SYSTEM-F-NOPRIV, error trying to access CF control file

%SYSTEM-E-INSFMEM, insufficient dynamic memory

This chapter describes updates to the information in the TCP/IP Services for OpenVMS product documentation.

5.1 Management Guide Update

The following chapters are updated in these release notes:

• Chapter 5, Configuring and Managing BIND, is replaced by Appendix C in these release notes, for Alpha systems.
• Chapter 12, Configuring and Managing NTP, is replaced by Appendix B in these release notes.
• A new chapter, Configuring and Managing the IMAP Server for OpenVMS Mail, is provided in these release notes. See Appendix A.

In addition, the information in the Compaq TCP/IP Services for OpenVMS Management guide is updated as follows:

• Section 19.3.5 XDM_XSESSION.COM File, is misleading. The following changes will be made to this section:
  1. Existing Text:
     XDM's default operation is to create a Common Desktop Environment (CDE) using the commands from the SYS$SYSTEM:TCPIP$XDM_XSESSION.COM file:
     Replacement Text:
     XDM's default operation after login is controlled by the SYS$SYSTEM:TCPIP$XDM_XSESSION.COM file. This file first parses its P1 display parameter nodename[:server[.screen]] and creates the DECwindows display using the following command:

     $ SET DISPLAY/CREATE/NODE="''nodename'"/TRANSPORT=tcpip - _$ /SERVER='server/SCREEN='screen

     
     The default operation is to then create a Common Desktop Environment (CDE) using:
  2. Existing Text:

     $ DEFINE DECW$DISPLAY "''p1'" $ DEFINE display "''p1'" $ @CDE$PATH:XSESSION.COM

     
     Replacement Text:

     $ @CDE$PATH:XSESSION.COM

  3. Existing Text:
     At present, CDE is available only on Alpha systems in Version 1.2-4 or later and not at all on VAX systems. If the CDE command procedure XSESSION.COM is not found on the system, XDM looks for the DECwindows Desktop Session Manager startup command procedure, DECW$STARTSM.COM to initiate the session using the commands:
     Replacement Text:
     At present, CDE is available only on Alpha systems in version 1.2-4 or later of DECwindows Motif, and not at all on VAX systems. If the CDE command procedure XSESSION.COM is not found on the system, XDM looks for the DECwindows Desktop Session Manager startup command procedure, DECW$STARTSM.COM, to initiate the session using the command:
  4. Existing Text:

     $ SET DISPLAY/CREATE/NODE=nodename/TRANSPORT=TCPIP $ @SYS$MANAGER:DECW$STARTSM.COM

     
     Before executing either of these command procedures, XDM looks for an XDM_XSESSION.COM file in the user's SYS$LOGIN directory. If found, XDM executes the file. Users can create a DECterm by adding the following DCL commands to their XDM_XSESSION.COM file:

     $ SET PROC/PRIV=SYSNAM $ SET DISPLAY/CREATE/NODE=workstation_display/TRANSPORT=TCPIP - _$ /EXECUTIVE_MODE $ CREATE/TERMINAL/WAIT/WINDOW_ATTRIBUTES=(ICON=nodename, - _$ TITLE=window_title)

     
     For a complete description of the CREATE and SET DISPLAY commands and their qualifiers, use the DCL command HELP at the OpenVMS system prompt.
     Replacement Text:

     $ @SYS$MANAGER:DECW$STARTSM.COM

     
     Before executing either of these command procedures (but after performing the $SET DISPLAY), XDM looks for an XDM_XSESSION.COM file in the user's SYS$LOGIN directory. If the file is found, XDM executes that file instead, passing it both the full display specification nodename[:server[.screen]]" as P1, and just the node name as P2.
     Users then have full control over exactly what type of session they prefer to start. For example, to start a DECterm, the following DCL commands are placed into their XDM_XSESSION.COM file:

     $ CREATE/TERMINAL/WAIT/WINDOW_ATTRIBUTES=(ICON="''p2'",TITLE=window_title)

     
     For a complete description of the CREATE command and its qualifiers, use the DCL command HELP at the OpenVMS system prompt.
• Chapter 4, Routing, does not describe the change in the handling of identical routes between TCP/IP Services Version 5.0 and Version 5.1. In Version 5.0, routes were chosen by round-robin selection, but this feature was disabled by default. In Version 5.1, by default, they are chosen based on reference count and use count, thus achieving true load balancing among identical routes. If more than one default route is set, all default routes are used in load balancing; if a route fails, then attempts to use that route also fail.
• The chapter on Remote commands (R commands) omits mention of the TCPIP$RCP_SEND_FIX_FORMAT_AS_ASCII logical name.
  For more information, see Section 3.2.
• Section 13.4.3, SNMP Options, fails to mention the fact that an SNMP community name can be added using either the SET CONFIGURATION SNMP command or the SNMP configuration file. The community name can consist of any 7-bit printable ASCII character except asterisk (*). This behavior is consistent with RFC 1157.
• In Chapter 22, the description of the LPD configuration logical TCPIP$LPD_KEEPALIVE is incorrect. The logical is set using the following command:

  $ DEFINE/SYSTEM TCPIP$LPD_KEEPALIVE 1

• In Chapter 15, Configuring and Managing FTP, the description of the FTP configuration logical TCPIP$FTP_KEEPALIVE is incorrect. To set this configuration parameter, enter the following command:

  $ DEFINE/SYSTEM TCPIP$FTP_KEEPALIVE 1

  
  The SET SERVICE command cannot be used to set this configuration parameter.
• The NFS Client chapter, Section 21.1.2.1 contains the following sentences, which are incorrect:

  (The client does not provide ADFs for files with the .TXT and .C extensions, because these are STREAM_LF.) The client maintains these ADFs on the server.

  
  These sentences will be removed from the manual.
• Also in the NFS Client chapter, the example of the MOUNT command in Section 21.4.1 shows an incorrect command line. The first line of the example should be replaced by the following:

  TCPIP> MOUNT DNFS1:[A] /HOST=BART /PATH="/DKA0/ENG"

• In Chapter 13, Table 13-3, the logical name SNMP_SUPPRESS_LOGGING_TIMESTAMP is incorrectly documented. The name of the logical is TCPIP$SNMP_SUPPRESS_LOGGING_TIMESTAMP.
  Also, in Table 13-6, the logical name TCPIP$SNMP_TRACE is incorrectly documented. The name of the logical is SNMP_TRACE.

The information in the Compaq TCP/IP Services for OpenVMS User's Guide is updated as follows:

• This release supports the use of double quotes ("name") in the OpenVMS personal name. If the SMTP mailer encounters double quotes in the personal name, it changes them to single quotes ('name').

The information in the Compaq TCP/IP Services for OpenVMS Management Command Reference manual is updated as follows:

• The SHOW NFS_SERVER command displays NFS server statistics and parameters. You can specify the following qualifiers with the SHOW NFS_SERVER command:
  • /CONTINUOUS=seconds
    Optional. Defaults: Static display; /CONTINUOUS=4.
    Provides a dynamic display, with optional screen-update interval.
    To terminate the display, press Ctrl/Y.
  • /RPC
    Optional.
    Displays only RPC-related performance counters and statistics.
  • /SERVER
    Optional.
    Displays NFS server-related performance counters and statistics.
  • /VERSION=version
    Optional. Default: Display Version 2 and Version 3
    Displays version-specific NFS server performance counters and statistics.
    Versions can be specified as follows:

    /VERSION=V2	Specifies only Version 2.
    /VERSION=V3	Specifies only Version 3.
    /VERSION=(V2,V3)	Specifies both Version 2 and Version 3. This is the default if you omit the /VERSION qualifier.

• The SET NFS_SERVER commands allows you to specify NFS server configuration information. Contrary to the information in manual, the /THREADS qualifier is not a valid qualifier. To modify this value, use the sysconfigdb utility to add an entry to the SYSCONFIGTAB file, as described in Section 1.6.
• When you use the TCP/IP management command DISMOUNT/HOST, you must include the /ALL qualifier.
• If you specify the /MASK qualifier on the SET ROUTE command, you must also include the /NETWORK qualifier.
• Explanations of the use of the probe timer and the drop count in the description of the SET PROTOCOL command are corrected as follows:
  • The /PROBE_TIMER qualifier specifies, in seconds, the length of time that TCP/IP Services will wait for a response when establishing a new TCP connection, as well as the time between idle probes when the SO_KEEPALIVE option is set.
  • The /DROP_COUNT qualifier specifies the number of idle probes that can go unsatisfied before a TCP connection is closed.
• The description of the SET CONFIGURATION ENABLE [NO]SERVICE command is incorrect. The description should read as follows:
  These commands modify service-related information in the permanent configuration database that enable services for startup:
  • on each node (node-specific)
  • on every node in a cluster (cluster-wide)
  
  SET CONFIGURATION ENABLE SERVICE adds an entry for a service to the list of enabled services in the configuration database.
  SET CONFIGURATION ENABLE NOSERVICE deletes an entry for a service from the list of enabled services in the configuration database.
  The FORMAT section should read as follows:

  SET CONFIGURATION ENABLE [NO]SERVICE service [/COMMON ] [ /[NO]CONFIRM ]

  
  Note that the service parameter is required and must always be specified. There is no default for the service parameter.
  The PARAMETERS section should include the following:
  service
  Required.
  Specifies the service to add or delete from the configuration database.
  The QUALIFIERS section should include:

  /COMMON
  Optional. Default: node-specific service without /COMMON
  Modifies service-related information in the configuration database for the clusterwide enabling or disabling of services.
  
  /CONFIRM
  /NOCONFIRM
  Optional. Default: /CONFIRM with wildcards; otherwise, /NOCONFIRM
  Used only with SET CONFIGURATION ENABLE NOSERVICE to control whether a request is issued before each delete operation to confirm that the operation should be performed.
  The /CONFIRM qualifier requests user confirmation when deleting service records.
  Enter one of the following at the confirmation prompt:

  • Y to delete the record
  • N to retain the record

  
  The /NOCONFIRM qualifier eliminates all user confirmation when deleting service records.

  
  The examples and supporting descriptions should read as follows:
  1. TCPIP> SET CONFIGURATION ENABLE SERVICE TELNET
     In the configuration database, enable the TELNET service for startup on this node.
  2. TCPIP> SET CONFIGURATION ENABLE SERVICE FTP /COMMON
     In the configuration database, enable the FTP service for startup on every node in the cluster.
  3. TCPIP> SET CONFIGURATION ENABLE NOSERVICE *

     Enable service TELNET Remove? [N]:Y

     
     In the configuration database, disable any service enabled for startup on this node if confirmed by the user.

The online Help file for the TCP/IP management interface has been updated with the changes listed in this section. For online help, enter the following commands:

$ TCPIP 
TCPIP> HELP 

The information in the Compaq TCP/IP Services for OpenVMS Sockets API and System Services Programming manual should be updated as follows:

• Table 2-2 describes the default setting for the TCPIP_KEEPIDLE option incorrectly. The default setting for this option is 7200 seconds (14400 half seconds). In addition, the manual fails to mention that, in order to use the options in Table 2-2, your program must use the TCP.H file.

The TCP/IP Services Help files should be updated, as described in the following sections.

5.5.1 The netstat Help File

the following options should be added to the netstat Help file:

• -s
  This option displays statistics for each protocol.
• -pudp
  This option displays statistics for the UDP protocol.
• -ptcp
  This option displays statistics for the TCP protocol.
• -picmp
  This option displays statistics for the ICMP protocol.
• -ip
  This option displays statistics for the IP protocol.
• -b
  This option displays the contents of the Mobile IPv6 binding cache. When used with the -s option, it displays binding cache statistics.
• -f address_family
  This option limits reports to the specified address family. Specify one of the following:
  • inet6 for the AF_INET6 family
  • inet for the AF_INET family

The routing table display is updated with the following new flags:

• C indicates a cloning route that was created by the ROUTE command.
• c indicates a cloned route.
• f indicates fragment to path MTU size is disabled on this route
• I indicates a route that contains valid link-layer information.
• L indicates a loopback route that was created by the kernel.
• m indicates a route that was created by a Mobile IPv6 binding update.
• P indicates a route that was created by the Path MTU discovery process.
• p indicates that Path MTU discovery is disabled on this route.