DIGITAL_TCP/IP_Services_for_OpenVMS___________ Release Notes October 1997 This manual describes new features and changes to the software; installation, upgrade, and compatibility information; new and existing software problems and restrictions; and software and documentation corrections. Revision Information: This is a new manual. Operating Systems: OpenVMS Alpha Versions 6.2, 7.0, 7.1 OpenVMS VAX Versions 6.2, 7.0, 7.1 Software Version: DIGITAL TCP/IP Services for OpenVMS Version 4.2 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ October 1997 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. DIGITAL conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community. © Digital Equipment Corporation 1997. All rights reserved. The following are trademarks of Digital Equipment Corporation: ACMS, ALL-IN-1, DECdtm, DDCMP, DEC, DECnet, DECNIS, DECserver, DECsystem, DECwindows, DIGITAL, DNA, InfoServer, LAT, OpenVMS, PATHWORKS, POLYCENTER, ULTRIX, VAX, VAXstation, VMS, VMScluster, and the DIGITAL logo. The following are third-party trademarks: IBM and OS/2 are registered trademarks of International Business Machines Corporation. Sun, NFS, and PC-NFS are registered trademarks of Sun Microsystems, Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. All other trademarks and registered trademarks are the property of their respective holders. ________________________________________________________________ Contents Preface.................................................. v 1 New Features 1.1 Asynchronous Transfer Mode (ATM) Networking Support (OpenVMS Alpha)...................... 1-1 1.2 Point-to-Point Protocol (PPP) (OpenVMS Alpha)....................................... 1-2 1.3 Remote Magnetic Tape and CD-ROM (RMT/RCD) Server....................................... 1-2 2 Changes, Problems, and Restrictions 2.1 BIND Server.................................. 2-1 2.1.1 Configuration Procedure Now Named UCX$BINDSETUP.COM........................ 2-1 2.1.2 Database File Changes.................... 2-1 2.2 File Transfer Protocol (FTP)................. 2-1 2.2.1 Simple Directory Content Listing......... 2-2 2.2.2 File Names Now Fully Expanded............ 2-2 2.2.3 Multiline Responses Are Available........ 2-2 2.2.4 New SET DEFAULT Strings.................. 2-3 2.2.5 New Responses to Wildcarded DELETE Commands................................. 2-3 2.3 Installation Changes and Restrictions........ 2-3 2.3.1 Reinstall UCX After OpenVMS Upgrade...... 2-3 2.3.2 Move the UCX$SNMP_STARTUP.COM File After Upgrading UCX............................ 2-3 2.3.3 PPP File Installed During Installation... 2-4 2.3.4 UCX$FIXUP.COM No Longer Included......... 2-4 2.4 Management Commands.......................... 2-4 2.5 Network File System (NFS).................... 2-4 iii 2.5.1 Changes to the NFS Client................ 2-5 2.5.1.1 Privileges Required When Issuing MOUNT and DISMOUNT Commands.................. 2-5 2.5.1.2 New Option for the /CACHE_TIMEOUT Qualifier.............................. 2-6 2.5.2 Using the Default User ID (UID).......... 2-6 2.5.3 NFS Client and Server Restrictions....... 2-6 2.6 Point-to-Point Protocol (PPP) Requirement.... 2-7 2.7 Post Office Protocol (POP) Server............ 2-8 2.7.1 Define POP Logical Names in UCX$POP_SYSTARTUP.COM.................... 2-8 2.7.2 Link Idle Timeout No Longer Configured... 2-8 2.7.3 POP Problems............................. 2-8 2.8 RSH/SYSERROR Command Restriction............. 2-9 2.9 SET SERVICE/LOG_OPTIONS Command Restriction.................................. 2-9 2.10 Simple Mail Transfer Protocol (SMTP)......... 2-10 2.10.1 SMTP Addressing Changes.................. 2-10 2.10.2 New SMTP Informational Message........... 2-11 2.10.3 SMTP Addressing Syntax Guidelines........ 2-12 2.10.4 Corruption in SMTP Control Files......... 2-12 2.11 Simple Network Management Protocol (SNMP).... 2-13 2.12 Sun Remote Procedure Calls (RPCs)............ 2-13 2.13 UCX$RSH_KEEPALIVE: New Logical Name.......... 2-14 3 Corrections 3.1 BIND Server Corrections...................... 3-1 3.2 Documentation Correction to the DIGITAL TCP/IP Services for OpenVMS ONC RPC Programming Manual........................... 3-1 3.3 Engineering Change Order Included............ 3-1 3.4 POP Problem Corrected........................ 3-2 3.5 UCX$SHUTDOWN Information Messages Corrected.................................... 3-2 iv ________________________________________________________________ Preface The DIGITAL TCP/IP Services for OpenVMS (UCX) product is the DIGITAL implementation of the TCP/IP protocol suite and internet services for OpenVMS Alpha and OpenVMS VAX systems. The release notes in this manual apply to DIGITAL TCP/IP Services for OpenVMS Version 4.2. Print the Release Notes text file at the beginning of the installation procedure and read it before you install the product. Intended Audience These release notes are for: o UCX installers who are using the POLYCENTER Software Installation utility (for OpenVMS Alpha systems) or the VMSINSTAL procedure (for OpenVMS VAX systems). For complete installation information, see the DIGITAL TCP /IP Services for OpenVMS Installation and Configuration manual. o Managers of OpenVMS layered products o OpenVMS system managers o Network managers (who may or may not be familiar with UNIX) v Document Structure This manual contains the following chapters: o Chapter 1 introduces new features. o Chapter 2 discusses software changes, problems, and restrictions. o Chapter 3 outlines corrections to the software and documentation. Terminology This manual uses the following terminology: o The abbreviation for the product's name is UCX. o DIGITAL TCP/IP Services for OpenVMS is used to mean both: - DIGITAL TCP/IP Services for OpenVMS Alpha - DIGITAL TCP/IP Services for OpenVMS VAX o Software components - The auxiliary server is the DIGITAL TCP/IP Services for OpenVMS implementation of the UNIX internet daemon (inetd). - NFS is the DIGITAL TCP/IP Services for OpenVMS implementation of the Network File System (NFS) protocols, including the NFS Server, NFS Client, and PC-NFS. - TN3270 is the TELNET software that emulates IBM 3270 model terminals. o UNIX operating system UNIX refers to UNIX Version 4.3 of the Berkeley Software Distribution (BSD). The DIGITAL UNIX operating systems are fully compatible with UNIX BSD Version 4.3. o Networking terms - Host and node both mean a system connected to an internet. vi - The term Internet means the network, as defined by RFC 1208, consisting of large networks that use the TCP/IP protocol suite and provide universal connectivity, reaching the Defense Advanced Projects Research Agency (DARPA) Internet, MILNET, NSFnet, CERN, and many worldwide universities, government research labs, military installations, and business enterprises. The term internet means interconnected networks using the TCP/IP protocols, functioning as one, virtual network. Acronyms For a complete list of acronyms used throughout this and other manuals in the DIGITAL TCP/IP Services for OpenVMS documentation set, see the DIGITAL TCP/IP Services for OpenVMS Concepts and Planning guide. Conventions The following conventions apply to this book. __________________________________________________________ Convention_______Meaning__________________________________ UPPERCASE Indicates OpenVMS system output or user SPECIAL TYPE input. lowercase Indicates UNIX system output or user special type input, commands, options, files, directories, utilities, hosts, and users. italic type Indicates a variable. Indicates that you press the Return key. Indicates that you press the Control key while you press the key noted by x. [ ] In command format descriptions, indicates optional elements. You can enter as many as you want. { } In command format descriptions, indicates you must enter at least one listed _________________element._________________________________ vii Related Documents For complete information about DIGITAL TCP/IP Services for OpenVMS Version 4.2, refer to the following manuals in the documentation set. For a brief description of each manual, see the DIGITAL TCP/IP Services for OpenVMS Concepts and Planning guide. o DIGITAL TCP/IP Services for OpenVMS Concepts and Planning o DIGITAL TCP/IP Services for OpenVMS Installation and Configuration o DIGITAL TCP/IP Services for OpenVMS User's Guide o DIGITAL TCP/IP Services for OpenVMS Management o DIGITAL TCP/IP Services for OpenVMS Management Command Reference o DIGITAL TCP/IP Services for OpenVMS ONC RPC Programming o DIGITAL TCP/IP Services for OpenVMS System Services and C Socket Programming o DIGITAL TCP/IP Services for OpenVMS eSNMP Programming and Reference For additional information about the DIGITAL TCP/IP Services for OpenVMS product and services, access the DIGITAL OpenVMS World Wide Web site. Use the following URL: http://www.openvms.digital.com Reader's Comments DIGITAL welcomes your comments on this manual or any of the DIGITAL TCP/IP Services for OpenVMS documents. Send us your comments through any of the following channels: Internet openvmsdoc@zko.mts.dec.com viii Fax 603 881-0120, Attention: OSSG Documentation, ZKO3-4/U08 Mail OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698 How To Order Additional Documentation Use the information in the following table to order additional documentation or information. If you need help deciding which documentation best meets your needs, call 800-DIGITAL (800-344-4825). ________________________________________________________________ Location____Call__________Fax____________Write__________________ U.S.A. DECdirect Fax: 800-234- Digital Equipment 800-DIGITAL 2298 Corporation 800-344-4825 Mailstop: TAY2-2/11D 153 Taylor Street Littleton, MA 01460 Puerto 787-781-0505 Fax: 787-749- Local DIGITAL Rico 8300 subsidiary Canada DTN: 621- Fax: 613-592- Digital Equipment of 6005 1946 Canada, Ltd. 800-DIGITAL Box 13000 Kanata, Ontario, Canada K2K2A6 Attn: CICC Internationa- - Local DIGITAL subsidiary or approved distributor ix ________________________________________________________________ Location____Call__________Fax____________Write__________________ Internal DTN: 261- Fax: 800-741- U.S. Software Supply Orders 2010 6970 Business 603-791-2010 Digital Equipment Corporation 8 Cotton Road _________________________________________Nashua,_NH_03063-1260__ x 1 ________________________________________________________________ New Features This chapter introduces the new features that are provided in this release of the DIGITAL TCP/IP Services for OpenVMS Version 4.2 product: o Asynchronous Transfer Mode (ATM) networking support for OpenVMS Alpha systems (Section 1.1) o Point-to-Point Protocol (PPP) for OpenVMS Alpha Version 7.1 systems (Section 1.2) o Remote Magnetic Tape and CD-ROM (RMT/RCD) server for remote system access to local OpenVMS magnetic tape drives and CD-ROMs (Section 1.3) 1.1 Asynchronous Transfer Mode (ATM) Networking Support (OpenVMS Alpha) DIGITAL TCP/IP Services for OpenVMS Alpha now supports the use of ATM networking on OpenVMS Alpha systems. ATM is a transport protocol that is the international standard for cell relay, which is a high-speed packet switching technology requiring a large amount of bandwidth. For information about how to configure your OpenVMS Alpha system to use either LAN emulation over an ATM network or Classical IP over ATM, see the OpenVMS documentation set. New Features 1-1 1.2 Point-to-Point Protocol (PPP) (OpenVMS Alpha) DIGITAL TCP/IP Services for OpenVMS Alpha now supports point-to-point connections of serial lines (such as modems or dedicated lines) using the PPP datalink available with OpenVMS Alpha Version 7.1. Making connections using PPP is similar to connecting using the Serial Line Internet Protocol (SLIP). With PPP, the network interface is the modem connection. You can use any terminal device that is supported by the OpenVMS PPP data link. After you establish a PPP connection between hosts, you can issue commands over the line. If the remote system is configured as a gateway to a network, you can also reach other systems on the network. For information about how to configure a system and establish connections, see the DIGITAL TCP/IP Services for OpenVMS Management guide. 1.3 Remote Magnetic Tape and CD-ROM (RMT/RCD) Server DIGITAL TCP/IP Services for OpenVMS now includes an RMT /RCD server, which provides remote system access to local OpenVMS magnetic tape drives and CD-ROMs. The magnetic tape or CD-ROM appears to the RMT/RCD user as if it was mounted locally. The RMT/RCD server implements the UNIX commands rdump and restore. For information about how to use the RMT/RCD func- tionality, see the DIGITAL TCP/IP Services for OpenVMS Management guide. 1-2 New Features 2 ________________________________________________________________ Changes, Problems, and Restrictions This chapter provides general notes about changes, problems, and restrictions in DIGITAL TCP/IP Services for OpenVMS Version 4.2. 2.1 BIND Server The notes in the following sections outline changes to the BIND server. 2.1.1 Configuration Procedure Now Named UCX$BINDSETUP.COM With Version 4.2, the command procedure that you run to configure the BIND server has been modified and renamed. The new BIND server configuration file is SYS$MANAGER:UCX$BINDSETUP.COM. 2.1.2 Database File Changes The primary BIND server uses the SYS$SPECIFIC:[UCX$BIND]NAMED.LOCAL and SYS$SPECIFIC:[UCX$BIND]NAMED.CA files as a loopback address (for directing traffic back to itself) and to hold information about the root name servers, respectively. With Version 4.2, the NAMED.LOCAL and NAMED.CA files, which are installed as part of a new BIND server installation, have been updated. For information about the file contents, see the DIGITAL TCP/IP Services for OpenVMS Management guide. 2.2 File Transfer Protocol (FTP) The notes in the following sections outline changes to the FTP client and server functionality. Changes, Problems, and Restrictions 2-1 2.2.1 Simple Directory Content Listing For command lines that contain wildcards, FTP parsing now includes node, device, and directory information where appropriate. As a result, FTP provides ample path information so the client user can use the returned file names for subsequent operations. FTP now fully supports search lists. In previous versions of FTP, when you specified a search list, FTP would exclude the device and directory strings in the returned file names. Thus, the client could not distinguish files of the same name that were located in different directories specified in the search list. The inclusion of the device and directory strings lets the client access such files. 2.2.2 File Names Now Fully Expanded With Version 4.2, the server returns fully expanded file specifications wherever possible and appropriate. These specifications include the node, device, directory, name, type, and version numbers of files. 2.2.3 Multiline Responses Are Available RFC 959 specifies that the server should be able to return multiple lines of status output to a client. Wherever possible and appropriate, the FTP server now returns multiple lines of output, including OpenVMS error messages that previously were not returned. The messages help the client user diagnose and correct error conditions. RFC 959 also specifies that the client can command the server to disable multiline responses. Usually this situation occurs when applications use FTP to transfer files under program control. The password provided to the FTP server (by the client at connection time) must include a hyphen (-) as the first character of the password. As a result, the FTP server provides single line responses to the client. By default, the multiline feature is enabled. 2-2 Changes, Problems, and Restrictions The FTP server's STATUS output (for the SHOW STATUS command) indicates the status of the multiline message feature. The last line of the SHOW STATUS output specifies whether multiline responses are enabled or disabled. 2.2.4 New SET DEFAULT Strings The SET DEFAULT command accepts the solitary "~" character to specify that the server switch the session to the user's default login directory. For example, the following command brings the user to the default login directory: FTP> SET DEFAULT ~ 2.2.5 New Responses to Wildcarded DELETE Commands If you use the DELETE command with wildcarded file specifications to delete multiple files when the multiline response feature is enabled, FTP now displays the name of each deleted file. 2.3 Installation Changes and Restrictions The notes in the following sections provide important installation information. 2.3.1 Reinstall UCX After OpenVMS Upgrade If you upgrade from OpenVMS Version 6.2 to OpenVMS Version 7.0 or 7.1, you must reinstall the UCX software to ensure the correct image compatibility. 2.3.2 Move the UCX$SNMP_STARTUP.COM File After Upgrading UCX If you are upgrading UCX to Version 4.2 and you want to enable startup of the SNMP component by the auxiliary server, you need to copy the SYS$MANAGER:UCX$SNMP_ STARTUP.COM file to the SYS$SYSDEVICE:[UCX$SNMP] directory. Note that you can start SNMP manually by issuing the following command: $ @SYS$SYSDEVICE:[UCX$SNMP]UCX$SNMP_STARTUP For information about the operation of the auxiliary server, see the DIGITAL TCP/IP Services for OpenVMS Management guide. Changes, Problems, and Restrictions 2-3 2.3.3 PPP File Installed During Installation During the installation of Version 4.2, an updated OpenVMS PPP device driver is installed. This device driver enables successful PPP connections; it replaces the driver included with OpenVMS Version 7.1. 2.3.4 UCX$FIXUP.COM No Longer Included With Version 4.2, the UCX$FIXUP.COM file is no longer included in the kit. If the UCX$CONFIG.COM or UCX$STARTUP.COM procedures detect the SYS$MANAGER:UCX$FIXUP.COM file, they execute the UCX$FIXUP procedure, which deletes itself after completion. 2.4 Management Commands The management commands have the following restrictions: o SET NOROUTE command - Partial wildcards are not valid. For example: UCX> SET NOROUTE route* o SET SERVICE command - When you modify parameters to a service, disable and re-enable the service for the modifications to take effect. o DISABLE SERVICE command - Except for TELNET and remote login, 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. Issue an ENABLE SERVICE command. 2.5 Network File System (NFS) The notes in the following sections discuss the NFS functionality. 2-4 Changes, Problems, and Restrictions 2.5.1 Changes to the NFS Client For Version 4.2, the NFS client has been modified as follows: o The expected behavior for the MOUNT and DISMOUNT commands has changed. The default mount is considered a /SYSTEM mount instead of a /JOB mount. Privileges are now required unless you use the /SHARE qualifier. For more information about the required privileges, see Section 2.5.1.1. o The client supports shared mounting by nonprivileged users through use of the /SHARE qualifier. For information about the /SHARE qualifier, see the DIGITAL TCP/IP Services for OpenVMS Management guide. o A new READ_DIRECTORY option has been added to the /CACHE_TIMEOUT qualifier. For information about the READ_DIRECTORY option, see Section 2.5.1.2. 2.5.1.1 Privileges Required When Issuing MOUNT and DISMOUNT Commands Prior to Version 4.2, privileges were not required to mount and dismount DNFS volumes. In Version 4.2, this behavior has changed as follows: o The /GROUP qualifier makes the volume available to other users with the same group number in their UICs as the user entering the MOUNT command. The logical name for the device is placed in the group logical name table. You must have the OpenVMS privilege GRPNAM to use the /GROUP qualifier. o The /SYSTEM qualifier makes the volume available to all users of the system, as long as the UIC-based protections allows them access. The logical name for the device is placed in the system logical name table. You must have the OpenVMS user privilege SYSNAM to use the /SYSTEM qualifier. By default, the client places the logical name for the device in the system logical name table unless you specify the /GROUP or /SHARE qualifier. The client deletes the logical name from the appropriate logical name table when you dismount the volume. Changes, Problems, and Restrictions 2-5 If you do not have SYSNAM or GRPNAM privilege, you must use the /SHARE qualifier when mounting a file. See the following section for information about using the new /SHARE qualifier. 2.5.1.2 New Option for the /CACHE_TIMEOUT Qualifier The READ_DIRECTORY option is available for the MOUNT/CACHE_TIMEOUT command. This option forces the client to read the contents of the directory requested when the cache timeout occurs rather than relying on the directory's modified time. By reading the directory contents, the client can be aware of any changes to the number of files within the directory even if the directory's modify time was not updated. 2.5.2 Using the Default User ID (UID) Both the NFS server and the NFS client use a proxy database for access control. To provide universal access to world-readable files, you can use the default user ID (UID) and avoid the need to create a proxy for every NFS client user. DIGITAL strongly recommends that, for any other purpose, you provide a proxy with a unique UID for every NFS client user. Otherwise, client users may see unpredictable and confusing results when they try to create files. 2.5.3 NFS Client and Server Restrictions Version 4.2 of NFS has the following restrictions: o Issuing the BACKUP/VERIFY command might result in false verification error messages. o DIGITAL recommends that you do not access CMS libraries through NFS from remote nodes. o The NFS client with OpenVMS POSIX is not supported. You cannot map remote file systems for use by OpenVMS POSIX applications through the use of the NFS client. o The NFS client does not support attribute codes ATR$C_ ASCDATES and ATR$C_EXPDAT for dates later than 1999. 2-6 Changes, Problems, and Restrictions Because most applications and utilities use other attribute codes (for example: ATR$C_CREDATE, ATR$C_ REVDATE, and ATR$C_EXPDATE) to access the same date information, few will be affected by this restriction. For information about the attribute codes, see the OpenVMS I/O User's Reference manual. o Some NFS servers only allow a superuser to mount files and directories. If you mount a path on such a server, do not use automounting. Automounting does not work in such cases because even though a superuser makes the initial mount, subsequent requests from individual users are identified with their own UID/GID pair. The server rejects these requests because it expects the superuser UID/GID pair for identification. 2.6 Point-to-Point Protocol (PPP) Requirement To configure a PPP interface, you issue either the SET INTERFACE PPn or SET CONFIGURATION PPn command. When configuring an OpenVMS host as a PPP provider, you can specify an IP address for the remote host with the /DESTINATION qualifier to the SET INTERFACE command. This IP address is assigned to the remote host when a remote host requests a PPP connection, unless that remote host has already been configured with an address. When configuring your host in this way, you must also specify your local address with the /HOST qualifier. For example: $ UCX SET INTERFACE PP1 /HOST=120.3.2.1 /DESTINATION=120.3.2.5 In this example, the address 120.3.2.1 is the local host. When a remote host requests a connection, the local host assigns address 120.3.2.5 to the remote host. For information about setting up a PPP interface, see the DIGITAL TCP/IP Services for OpenVMS Management guide. Changes, Problems, and Restrictions 2-7 2.7 Post Office Protocol (POP) Server This section contains notes that pertain to the POP server functionality. 2.7.1 Define POP Logical Names in UCX$POP_SYSTARTUP.COM For Version 4.2, the correct place to define POP configuration logical names is in a SYS$MANAGER:UCX$POP_ STARTUP.COM file. With Version 4.1, the UCX$POP_RECV_STARTUP.COM file contained definitions for some POP configuration logical names with directions to uncomment the logical names if you wanted to configure a particular item. With Version 4.2, the UCX$POP_RECV_STARTUP.COM file does not contain the configuration logical names. If you defined the POP server configuration logical names in the UCX$POP_RECV_STARTUP.COM file, you should create a SYS$MANAGER:UCX$POP_SYSTARTUP.COM file and move the logical name definitions to this file instead. 2.7.2 Link Idle Timeout No Longer Configured With Version 4.2, there is no longer a default link idle timeout period. With Version 4.1, the default POP link idle timeout period was 2 minutes. 2.7.3 POP Problems The following problems exist in this release: o Both the UCX and IUPOP3 servers have problems parsing addresses that include personal names containing double quotes. o Both the UCX and IUPOP3 servers have problems parsing addresses that contain a space within the address. o The UCX POP server serves a maximum of 31 threads. Because of problems in the UCX auxiliary server's handling of nolisten services, the maximum number of concurrent connections to the UCX POP port (port 110) of each host is 31. The callable OpenVMS Mail utility limits user processes to 31 concurrent mail threads; 2-8 Changes, Problems, and Restrictions therefore, one POP server process can handle only 31 threads. A system could serve more than 31 concurrent POP connections by having multiple POP server processes running. However, the auxiliary server problem prevents the creation of additional POP server processes when one process reaches its maximum. When this problem is corrected, more than 31 concurrent POP connections can be served, because multiple POP server processes will be created. o The following POP server problems relate to the OpenVMS operating system: - Memory leaks in OpenVMS callable mail may exist. If the UCX POP server crashes with insufficient memory, you can lengthen the life of the server process between crashes by increasing the UCX$POP account's PGFLQUO. - On OpenVMS Version 6.2, the UCX POP server might exit with an access violation message. If the POP server reads a variable with fixed-length control (VFC) .MAI file on an OpenVMS VAX Version 6.2 system, the server displays an access violation message and exits. - On OpenVMS Version 6.2, the POP server might exit with a MAIL-W-NOMORERECS message if the mail message is lengthy. 2.8 RSH/SYSERROR Command Restriction On OpenVMS Version 6.2 systems (both Alpha and VAX), do not use the /SYSERROR qualifier to the RSH command because of a possible system crash. Instead, use the default /NOSYSERROR qualifier, which directs output to SYS$OUTPUT. 2.9 SET SERVICE/LOG_OPTIONS Command Restriction With Version 4.2, the [FILE=file name] option to the management command SET SERVICE/LOG_OPTIONS is not functioning. The event-logging messages are written to the default file for the requested service; you cannot define the file. Changes, Problems, and Restrictions 2-9 2.10 Simple Mail Transfer Protocol (SMTP) The notes in this section pertain to the SMTP functional- ity. 2.10.1 SMTP Addressing Changes Beginning with OpenVMS Version 6.2, OpenVMS Mail automatically interprets a destination address as an Internet address. You are no longer required to add the SMTP% prefix and quotes around the address. In addition, OpenVMS Mail automatically translates the following: o If the node component (username@node) of the address is fully qualified (it contains a period (.)), such as markson@billows.bldg2.com), OpenVMS Mail assumes the address is an Internet address and uses the SMTP protocol by default. If you want to use a different Internet protocol, you can define the alternate protocol with the MAIL$INTERNET_TRANSPORT logical name. o If the node component of the address is not fully qualified (does not contain a period), OpenVMS Mail translates the address for DECnet transport. For example, if you specified markson@billows as the destination address, the utility interprets it as BILLOWS::MARKSON and uses DECnet instead of SMTP. Beginning with OpenVMS Version 7.0, you can force OpenVMS Mail to use a specific protocol by defining the MAIL$INTERNET_MODE logical name. This condition is useful in cases where a mail address such as markson@billows can be interpreted as valid for either the Internet or DECnet protocol. You can assign one of the following values to the MAIL$INTERNET_MODE logical name in your LOGIN.COM file: o SMTP Mail always interprets the node component of an unqualified address as an Internet address specifi- cation. (SMTP is the default transport used unless you define an alternate Internet transport with the MAIL$INTERNET_TRANSPORT logical name.) o DECNET 2-10 Changes, Problems, and Restrictions Mail always interprets the node component of an unqualified address as a DECnet node specification. o HYBRID (the default) Mail uses an Internet protocol if the node component of the address contains a period. If there are no periods in the node component, Mail uses the DECnet protocol. For example, the following definition causes the Mail utility to interpret any address that does not include a period in the node component of the specification as an Internet address: $ DEFINE MAIL$INTERNET_MODE SMTP Therefore, with OpenVMS Version 7.0 and subsequent versions, if you want to avert having an unqualified Internet address translated for DECnet transport, you have three choices: o Fully qualify the address (for example, specify markson@billows.bldg2.com instead of markson@billows) o Include the SMTP% prefix (specify SMTP%"markson@billows) o Define the MAIL$INTERNET_TRANSPORT logical name as SMTP. For more information on OpenVMS Mail and how it interprets addresses, see the appropriate OpenVMS documentation. 2.10.2 New SMTP Informational Message With Version 4.2, when a user sends a mail message that contains a record greater than 1000 bytes, the following informational message is displayed: %UCX-I-SMTP_LINEWRAP, Line contains more then 1000 bytes, splitting into multiple lines Changes, Problems, and Restrictions 2-11 2.10.3 SMTP Addressing Syntax Guidelines SMTP does not set the RFC 822 CC: header for outbound mail. SMTP does not work correctly when a user, sending mail to multiple users, mixes local and remote addresses. To work around this problem, use the following syntax at the To: prompt: $ MAIL MAIL> SEND To: SMTP%"addr1,addr2,addr3" where each address is a fully qualified SMTP address. For example, mail a copy of the same file to the following people: o Users Julie and Mark on the local system o User John on remote host beach.ocean.com o User Ramesh on remote host lake.tarn.edu $ MAIL MAIL> SEND MEMO.TXT To: julie,mark,smtp%"john@beach.ocean.com,ramesh@lake.tarn.edu" Subj: For Your Review To use SMTP to send to the local recipients, keep the local recipients separate from the nonlocal recipients. At the To: prompt, enter: To: SMTP%"julie,mark",smtp%"john@beach.ocean.com,ramesh@lake.tarn.edu" 2.10.4 Corruption in SMTP Control Files Intermittently, the SMTP symbiont signals an error on a particular control file. The most common error message returned is SYSTEM-F-BADPARAM, although the problem can sometimes result in the access violation message SYSTEM- F-ACCVIO. During most of the occurrences, the symbiont process crashes, leaving a dump file. If you do not delete the queue entry for the control file that caused the crash, the entry will be the first entry processed when the queue is started after the crash, which causes the queue to crash again. If the job is put on hold and a UCX command SHOW MAIL/FULL is issued, the SHOW MAIL command either signals an error or hangs. 2-12 Changes, Problems, and Restrictions This problem is due to a periodic corruption that occurs in SMTP control files and happens more frequently with high-use systems (1000 or more control files processed per day) than with systems processing less mail. To work around the problem, run the SMTP queue watcher command file UCX$EXAMPLES:UCX$RESTART_SMTPQ.COM. The header comments of this file describe its use and operation. 2.11 Simple Network Management Protocol (SNMP) Under certain conditions, SET commands issued by an SNMP client (the network management station) for system contact and location (the SysLocation and SysContact objects, respectively) do not function correctly. Either the SNMP command does not return a success status or changes to the dynamic Management Information Base (MIB) values are not reflected in the configuration database (SYS$SYSTEM:UCX$CONFIGURATION.DAT) for the host on which the SNMP server processes are running. To make permanent changes to system contact and location information on the host, use the /CONTACT and /LOCATION qualifiers with the UCX command SET CONFIGURATION SNMP. For more information about configuring SNMP, see the DIGITAL TCP/IP Services for OpenVMS Management guide. 2.12 Sun Remote Procedure Calls (RPCs) DIGITAL TCP/IP Services for OpenVMS Version 4.0 im- plemented the Sun ONC Version 4.2 RPC protocol. UCX links this development software with DECC$SHR instead of VAXCRTL. To use RPC, you must now compile your programs using DEC C. OpenVMS VAX Systems When upgrading from UCX Version 3.3 or earlier to Version 4.2 on an OpenVMS VAX system, the installation procedure installs a new UCX$RPCXDR_SHR.EXE image and renames the existing copy of UCX$RPCXDR_SHR.EXE to UCX$RPCXDR_SHR.EXE_ OLD. Changes, Problems, and Restrictions 2-13 If any of your applications that use RPC were compiled and linked using UCX Version 3.3 or earlier, you must either rebuild the application using DEC C or revert to the previous UCX$RPCXDR_SHR.EXE file. 2.13 UCX$RSH_KEEPALIVE: New Logical Name The Remote (R) command RSH connects a user's terminal to a remote host so the user can issue a command or execute a shell script or command procedure at that system without logging in. With Version 4.2, the logical name UCX$RSH_KEEPALIVE is supported. This logical name detects idle and broken RSH connections. Defining it on the client host enables the SO_KEEPALIVE option in the socket connection, which causes the system that set the option to periodically test the connection with the remote system to be sure it is still valid. If the UCX$RSH_KEEPALIVE logical name is not defined, a user does not know about a broken connection until attempting to send data to the remote system. 2-14 Changes, Problems, and Restrictions 3 ________________________________________________________________ Corrections This chapter outlines corrections to the software and the documentation for DIGITAL TCP/IP Services for OpenVMS Version 4.2. 3.1 BIND Server Corrections The following corrections to the BIND server are included in Version 4.2 of the software: o The BIND server now generates a message to the log file that it found an incorrect root name server record. This message allows the network administrator to track any incorrect information that is preventing name servers from resolving queries and update the appropriate root server. o There is no longer a minimum cache time-to-live (TTL) value. 3.2 Documentation Correction to the DIGITAL TCP/IP Services for OpenVMS ONC RPC Programming Manual In the DIGITAL TCP/IP Services for OpenVMS ONC RPC Programming manual, the xdr_free function is incorrectly documented as returning a bool_t value. In fact, the function returns a void. 3.3 Engineering Change Order Included Version 4.2 of UCX includes the UCXECO8-041 ECO. For a list of corrections included in the ECO, refer to the ECO8 Release Notes. Corrections 3-1 3.4 POP Problem Corrected If a line of text from an OpenVMS Mail message is 255 characters long, the POP server no longer loses the last byte of information. 3.5 UCX$SHUTDOWN Information Messages Corrected Prior to Version 4.2, when you executed the shutdown procedure SYS$STARTUP:UCX$SHUTDOWN.COM, a number of components (FINGER, FTPD, METRIC, and NTP) issued UCX$component server stopped messages even when the components did not exist. With Version 4.2, upon shutdown, the components issue a message only if a server process exists and is stopped. 3-2 Corrections