TCPware for OpenVMS Version 5.3 Release Notes June 1998 These Release Notes describe enhancements, changes, and corrections made for the release of TCPware for OpenVMS Version 5.3. Process Software Corporation Framingham, Massachusetts ________________________ June 1998 __________ Copyright ©1998 by Process Software Corporation, Framingham, Massachusetts The material in this document is for informational purposes only and is subject to change without notice. It should not be construed as a commitment by Process Software Corporation. All Rights Reserved. Printed in the U.S.A. Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. TCPware is a registered trademark of Process Software Corporation. Other registered trademark and trademark information is included on the copyright page of the TCPware User's Guide. Contents_________________________________________________________ Preface_______________________________________________________vii Chapter_1__New_Features_and_Enhancements_in_Version_5.3__________ 1.1 * Pseudo Devices.......................................1-3 1.1.1 Adding a Pseudo Device.......................1-3 1.1.2 NETCU START/IP Information...................1-3 1.1.3 Characteristics of Pseudo Devices............1-4 1.1.4 When to Use Pseudo Devices, Secondary Addresses, and Interface Routes.........................1-5 1.2 * Daylight Savings Time Support........................1-5 1.2.1 Time Zone Configuration and Hardware Clock Overview.....................................1-6 1.2.2 TCPware Time Zone Support....................1-6 1.2.3 Compiled-in Time Zone Rules..................1-7 1.2.4 User-Defined Time Zone Rules.................1-8 1.2.5 Format of COUNTRY Specification..............1-8 1.2.6 Format of ZONE Specification.................1-9 1.2.7 Format of RULE Specification................1-10 1.2.8 Loadable Time Zone Rules Provided with TCPware.....................................1-10 1.2.9 Setting Time Zone and Time Offset Information.................................1-13 1.2.9.1 Using CNFNET to Configure Time Zone Information...........................1-13 1.3 Configuration, Startup, and Shutdown..................1-14 1.4 Domain Name Services..................................1-15 1.5 Drivers...............................................1-15 1.6 FTP-OpenVMS Client...................................1-16 1.7 * FTP-OpenVMS Server..................................1-16 1.8 HELP..................................................1-17 1.9 IMAP Server Support...................................1-18 1.10 INETDRIVER Services...................................1-18 1.11 Installation..........................................1-18 1.12 Kerberos..............................................1-19 1.13 Network Control Utility...............................1-19 1.14 NFS-OpenVMS Client....................................1-21 1.15 NetWare Services......................................1-21 1.16 Network Time Protocol.................................1-22 iii 1.17 NFS-OpenVMS Client and Server.........................1-22 1.18 ONC RPC Programming...................................1-22 1.19 Remote Copy Program...................................1-23 1.20 SMTP-OpenVMS..........................................1-23 1.21 SMUX Support..........................................1-23 1.22 Startup and Shutdown..................................1-23 1.23 TCPDUMP Utility.......................................1-24 1.24 TELNET-OpenVMS Client.................................1-24 1.25 TELNET-OpenVMS Server.................................1-25 1.26 TELNET Programming Library............................1-26 1.27 Terminal Server Print Services........................1-26 1.28 TFTP Utility..........................................1-26 1.29 TIMED.................................................1-26 1.30 WebCNF................................................1-26 1.31 Year 2000 Support.....................................1-26 Chapter_2__Corrections_Made_in_Version_5.3_______________________ 2.1 BGDRIVER...............................................2-1 2.2 DNIPDRIVER.............................................2-1 2.3 Domain Name Services...................................2-1 2.4 Dynamic Host Configuration Protocol....................2-2 2.5 FINGER Service.........................................2-2 2.6 FTP-OpenVMS Client and Server..........................2-3 2.7 * GateD................................................2-4 2.8 * IMAP Server..........................................2-4 2.9 INETDRIVER.............................................2-6 2.10 Installation and Removal...............................2-6 2.11 IPDRIVER...............................................2-7 2.12 Kerberos...............................................2-7 2.13 Line Printer Services..................................2-7 2.14 LPD Server.............................................2-8 2.15 NetWare Services.......................................2-8 2.16 NETCU.................................................2-10 2.17 * Network Control Process.............................2-10 2.18 Network Time Protocol.................................2-11 2.19 NFS-OpenVMS Client and Server.........................2-11 2.20 NSLOOKUP Utility......................................2-12 2.21 Packet Filtering......................................2-12 2.22 Post Office Protocol..................................2-13 2.23 PWIPDRIVER............................................2-13 2.24 * RMT Server..........................................2-13 iv 2.25 * RSH.................................................2-13 2.26 Remote Copy Program...................................2-14 2.27 RSH Server............................................2-14 2.28 SMTP-OpenVMS..........................................2-14 2.29 SNMP Services.........................................2-15 2.30 * Socket Library Services.............................2-15 2.31 TALK Utility..........................................2-15 2.32 TCPDRIVER Services....................................2-15 2.33 TCPDUMP Utility.......................................2-15 2.34 TELNET-OpenVMS........................................2-17 2.35 TIMED.................................................2-18 2.36 TRACEROUTE Utility....................................2-18 2.37 VMS Communications Interface Support..................2-18 2.38 WebCNF................................................2-19 Chapter_3__Changes_to_the_TCPware_Documentation_Set______________ 3.1 Chapter-by-Chapter Descriptions........................3-1 3.1.0.1 Reorganization.........................3-4 3.2 HELP Files............................................3-10 3.3 Documentation PostScript Files on CD-ROM..............3-10 Tables___________________________________________________________ 1 Document Conventions ..........................viii 1-1 Compiled-In Time Zone Rules.....................1-7 2-1 New IMAP Configuration Directives in User's .IMAPRC.........................................2-4 2-2 System-wide TCPWARE:.IMAPRC Directives..........2-5 v v Preface__________________________________________________________ Audience These Release Notes are important for all TCPware for OpenVMS users. Read these Release Notes before you install, upgrade, or use TCPware for OpenVMS Version 5.3-3. Purpose These Release Notes document the changes made in the release of TCPware for OpenVMS Version 5.3. The information is cumulative and describes the release of Version 5.3-2 and this maintenance release of Version 5.3-3. Information about Version 5.3-3 is preceded in text by an asterisk. Organization The information in these Release Notes is organized as follows: o Chapter 1, New Features and Enhancements in Version 5.3, describes new features added to and enhancements made to Version 5.3. o Chapter 2, Corrections Made in Version 5.3, describes the defects in previous versions of TCPware that are fixed in Version 5.3. o Chapter 3, Changes to the TCPware Documentation Set, describes the changes to and corrections in the TCPware documentation set. The sections of each chapter are organized alphabetically by topic or TCPware module. Related Information Information related to TCPware and the topics in these Release Notes is available from the following sources: o The TCPware documentation set (online and printed versions) o Software Product Description vii o Online TCPWARE Help o NETCU Quick Reference Card o Installation Quick Reference Card Note The Installation Quick Reference card refers to installing the "TCPWARE052" product. Specify the "TCPWARE053" product instead. Disk space is greater than specified on the card. Use the disk space speci- fications in the Installation and Configuration document. Conventions The Release Notes follow the conventions listed in Table 1. Note that italics and boldface are visible in PostScript (.PS) output only. Table_1:__Document_Conventions________________________________ * Precedes information that pertains to this maintenance release. D/E xxx These are the numbers Process Software uses and PIR internally to track reported problems about and xxx requested enhancements to our products. You can use these numbers to confirm whether a problem or enhancement has been addressed, or to request more details about a specific change to the product. UPPERCASE OpenVMS commands, files, or processes Letters italic Input or message variables, commands entered in type lowercase, or documentation references bold type User input [ ] Optional elements { | } One of the two elements enclosed in braces and separated by the vertical bar is required Note Important information for the user TCPware The TCPware for OpenVMS product OpenVMS The OpenVMS operating system for VAX and Alpha ____________platforms_________________________________________ viii Chapter__1_______________________________________________________ New Features and Enhancements in Version 5.3 This chapter briefly describes new features in or enhancements to releases of TCPware Version 5.3: Version 5.3-2 and Version 5.3-3. The information for Version 5.3-3 is preceded in text by an asterisk. See Chapter 2 for a description of fixed defects and Chapter 3 for documentation changes. Highlights of Major New Features The following table describes briefly the new features added to Version 5.3-3 and lists the Release Notes section to reference. ______________________________________________________________ New_Feature______Description_______________________________See Pseudo Devices Pseudo devices are a way to configure Section 1.1 a physical device to have multiple Internet addresses. Daylight Support for Daylight Savings Time (DST) Section 1.2 Savings Time enables you to configure time zone and Support__________DST_information._____________________________ New Features and Enhancements in Version 5.3 1-1 The following table describes briefly the new features in TCPware Version 5.3-2 and lists the Release Notes section to reference. These new features are documented in the TCPware manual set for Version 5.3 (see Chapter 3). ______________________________________________________________ New_Feature______Description_______________________________See... Internet IMAP supplements POP3 as a mail server Section 1.9 Message for remote PC systems. IMAP contrasts Protocol with POP3 in that IMAP retains the mail (IMAP) support on the server instead of copying it to the client. SNMP Mul- SNMP Services includes support for Section 1.21 tiplexing SMUX, which allows an application to (SMUX) service add to the Management Information Base support (MIB). TELNET Client TELNET-OpenVMS Client support for Section 1.24 Permanent NTA permanent NTA devices was enhanced. You support update can now close the TCP connection when the channel is deassigned, and create an NTA device even if not connected. Year 2000 All TCPware components support four- Section 1.31 tested digit dates for the year 2000 and _________________beyond.______________________________________ Note TCPware supports the following operating systems: o OpenVMS VAX V5.5-2 and later o OpenVMS Alpha V6.1 and later Earlier versions of OpenVMS and VMS VAX are no longer supported. For information on installing TCPware in a mixed environment (VAX and Alpha) so that you can share data files across platforms, please see the Process Software Customer Service web site, http://www.process.com/support/tcpware/faqs/faqs.htp (click "Mixed platform Clusters"), or contact Pro- cess Software Technical Support. 1-2 New Features and Enhancements in Version 5.3 1.1 * Pseudo Devices Pseudo device support is a new feature in TCPware 5.3-3. Pseudo devices are a way to configure a physical device to have multiple Internet addresses. Pseudo devices are typically used when a system is connected to a network that has several network numbers assigned to it. Pseudo devices can also be used in place of secondary addresses (for example, when a system has multiple addresses on the same network). When starting a pseudo device, you specify the local Internet address, network mask, and the physical device to which the pseudo device is connected. 1.1.1 Adding a Pseudo Device CNFNET has been updated to allow for configuring pseudo devices. The TCPware line-id for a pseudo device is PSD-n, where n is 0 to 255. To configure one or more pseudo devices via CNFNET, include the line-id or line-ids for the pseudo devices when prompted to enter the line identifications for all the network devices. Be sure to enter the pseudo device line-id after the physical device line-id. CNFNET prompts you for the standard information (Internet address, host name, and subnet mask) and for the physical device line-id for the pseudo device. 1.1.2 NETCU START/IP Information You can also start pseudo devices by using the NETCU START/IP command. The format of the START/IP command for pseudo devices is: START/IP PSD-n Internet-Address Real-Line-ID o n is the pseudo device line-id number (from 0 to 255). The number is not meaningful, but must be unique to all other pseudo devices, and is simply used to identify the instance of the pseudo device. o Internet-Address is the Internet address of the TCPware system on the network. o Real-Line-ID is the line-id of the physical device. Note the following with respect to standard START/IP qualifiers: o The /MASK qualifier can be used to specify the network mask for the network. New Features and Enhancements in Version 5.3 1-3 o The /ARP, /FLAGS, and /UNNUMBERED qualifiers are not allowed and result in an error if specified. o The /MTU qualifier, if specified, is ignored as the MTU used is that of the physical device. Example: NETCU START/IP ISA-0 192.168.1.1 NETCU START/IP PSD-0 192.168.2.1 ISA-0 In this example, a pseudo device is started that is associated with the ISA-0 device (this is the Ethernet network to which the system is connected). The Ethernet network has two IP network numbers assigned to it (192.116.1.0 and 192.168.2.0) and the system has two Internet addresses assigned to it, one on each network, 192.168.1.1 and 192.168.2.1. 1.1.3 Characteristics of Pseudo Devices Pseudo devices are interchangeable and usable just like physi- cal devices. However, there are a few special characteristics that are important to point out: o Multicast joins/leaves are redirected to the physical device as they need to be reflected there. o NETCU SHOW NETWORK shows no transmit/receive counts for pseudo devices. The physical device reflects the transmit/receive activity. o Pseudo devices are automatically removed whenever the physical device is removed (such as by a NETCU STOP/IP line-id command). o Starting a pseudo device on a pseudo device (by specifying a pseudo device line-id as the Real-Line-ID for a NETCU START/IP command) is allowed; however, the underlying physical device is actually used. o Packet filtering is not available for pseudo devices as these devices never receive any packets (the physical de- vice does). Therefore, you must do all packet filtering on the physical device and must take this into consideration when creating the packet filter list. Attempting to issue a NETCU SET FILTER or NETCU SHOW FILTER command on a pseudo device returns an error message. o Once a pseudo device is started, there is no indication available as to the physical device with which it is associated. o The line-id value for pseudo devices is 00nn0042 (hex), where n is the unit number (PSD-n). 1-4 New Features and Enhancements in Version 5.3 o For proper operation of pseudo devices (and TCPware in general), the LPB-0 (loopback) device must exist. The LPB-0 device is technically not optional. 1.1.4 When to Use Pseudo Devices, Secondary Addresses, and Interface Routes TCPware continues to support secondary addresses (NETCU ADD SECONDARY) and interface routes (NETCU ADD ROUTE) in addition to the new pseudo devices. Some recommendations as to which method to use and the conditions under which to use them are described next. o If a TCPware system is connected to a network via a single interface that has multiple networks numbers assigned to it: - Use a pseudo device for each network number on which the TCPware system has an Internet address (other than the one that is used to start the physical device). - Use an interface route for each network number on which the TCPware system does not have an Internet address. For an interface route, specify the line-id of the physical device in place of the gateway address parameter. o If a TCPware system has multiple addresses on a single network number: o Use either pseudo devices or secondary addresses for the additional addresses. Using a pseudo device has some advantages and is therefore recommended (especially if a DNS Server is running on the system). o To use the cluster alias failover support: o The secondary address feature must be used. Note If your site is using secondary addresses you might want to consider whether switching to pseudo devices makes sense for these addresses. 1.2 * Daylight Savings Time Support Support for automatic Daylight Savings Time (DST) changes has now been added to the existing method of specifying time zone information. This new feature enables you to configure time zone and DST information, which can be used by the Network Time Protocol (NTP) to automatically change the system clock and the time offset information. New Features and Enhancements in Version 5.3 1-5 This option has been added to the time zone configuration process used with CNFNET. The Installation and Configuration Guide for Version 5.3 contains information about the existing method. The new CNFNET procedure is described in these Release Notes in Section 1.2.9. To understand time zone configuration, time zone offset, and the hardware clock in relation to choosing the time zone settings you need, please read the following sections. 1.2.1 Time Zone Configuration and Hardware Clock Overview By convention, the hardware clock is usually set to the local time, but network protocols represent time in Greenwich Mean Time (GMT), also known as Universal Coordinated Time (UTC). To convert between local time and GMT, TCPware uses built-in rules or rules provided by the system manager. Each country or geographical area has its own names for time zones and its own rules for Daylight Savings Time (DST). The names for these time zones and rules are not necessarily unique; for example, "EST" could refer to the United States Eastern Standard Time, the Canadian Eastern Standard Time (which used different DST rules), or the Australian Eastern Standard Time (which is a different offset from GMT as well). TCPware uses the name of the local time zone specified by a system manager to calculate the offset between the local time and GMT, so it is important that an appropriate set of time zone rules be selected for your area. TCPware assumes that the hardware clock is always set exactly to local time. For a smooth transition to and from Daylight Savings Time (DST), the hardware clock must be reset at the appropriate time. If NTP is used to synchronize the clock to a time server, NTP automataically resets the clock when the Daylight Savings Time transition occurs. Note that using a military time zone or an explicit GMT offset disables automatic Daylight Savings Time transitions. 1.2.2 TCPware Time Zone Support It is not possible to consider every country or area in which TCPware might be used, and because the Daylight Savings Time rules are subject to change by local governmental action, you can write your own site-specific time zone rules. Time zone rules are either compiled-in or defined in the time zone rule definition file and converted by the time zone rule logical at startup, or by entering a specific NETCU command (DEFINE TIMEZONE). 1-6 New Features and Enhancements in Version 5.3 o Compiled-in rules are geographically centered around the United States but also include foreign time zones having names that do not conflict with the U.S. time zones. o User-defined rules are specified by using the NETCU command DEFINE TIMEZONE. Use the NETCU command to override the compiled-in rules. TCPware includes a database of the most common loadable rules; you can select these rules as is, or modify them to conform to the correct local time zone rules. When TCPware searches the time zone rules looking for a zone, it first searches the loaded rules in the order they are selected, then searches the compiled-in rules by loading rules that override them. In addition to the standard one-letter U.S. military time zones and time zones of the form GMT+hh:mm or GMT-hh:mm, there are compiled-in time zone rules supported by TCPware, which are shown in Table 1-1. 1.2.3 Compiled-in Time Zone Rules When a time zone is compiled-in, the logical "TCPWARE_ TIMEZONE_NAME" specifies which rule is to be compiled in; for example, EST. The compiled-in time zone rules are listed in the following table. Table_1-1:__Compiled-In_Time_Zone_Rules_______________________ GMT Offset Time_Zone_Name___(hours)_____DST_Rules___Area_or_Country______ EST or EDT -5 U.S. Eastern United States Federal CST or CDT -6 U.S. Central United States Federal MST or MDT -7 U.S. Mountain United Federal States PST or PDT -8 U.S. Pacific United States Federal YST or YDT -9 U.S. Yukon Federal HST -10 none Hawaii NST or NDT -3:30 Canadian Canadian Newfoundland AST or ADT -4 Canadian Canadian Atlantic New Features and Enhancements in Version 5.3 1-7 Table_1-1_(Cont.):__Compiled-In_Time_Zone_Rules_______________ GMT Offset Time_Zone_Name___(hours)_____DST_Rules___Area_or_Country______ JST +9 none Japan SST +8 none Singapore GMT +0 none Greenwich Mean Time GMT or BST +0 British Britain WET or WET-DST 0 European Western Europe MET or MET-DST +1 European Middle Europe CET or CET-DST +1 European Central Europe (Middle Europe) EET or EET-DST +2 hours European Eastern Europe NZST or NZDT +12 New New Zealand _____________________________Zealand__________________________ 1.2.4 User-Defined Time Zone Rules Loadable time zone rules provided with TCPware are in the text file TCPWARE:TIMEZONES.DAT. You can add user-written time zone rules to the file TCPWARE:TIMEZONES.LOCAL to override the zones in TIMEZONES.DAT. The user-defined time zone rule format has three parts: o COUNTRY is a collection of time zones (ZONES); for example, the country US selects all U.S. time zones. This provides a convenient way to select groups of time zones. o ZONE is a specification of a particular time zone, including the name of the zone, the GMT offset, the DST rules in effect, and the name to use while DST is in effect. o RULE is a rule for determining when DST is in effect. 1.2.5 Format of COUNTRY Specification COUNTRY countryname zonename [zonename . . .] The COUNTRY specification gives the name of the geographical area and the names of the time zones associated with it. This provides a way to group time zones so they can be selected more conveniently. 1-8 New Features and Enhancements in Version 5.3 The following example shows the definition of the country "US" listing the zones corresponding to the United States. The example for Arizona is slightly different, showing the zone "US/Arizona" instead of "US/Mountain". (US/Arizona is the definition of a Mountain time zone that does not observe Daylight Savings Time.) Country US US/Eastern US/Central US/Mountain US/Pacific US/Yukon US/ Country - US/Arizona US/Eastern US/Central US/Arizona US/Pacific US/Yukon US/H 1.2.6 Format of ZONE Specification ZONE zonename gmtoffset rulename standard-name dst- name [COMPILED_IN] The ZONE specification describes a time zone: o zonename is the name by which this zone can be selected, or the name by which it is referred to in a COUNTRY specification. o gmtoffset is this zone's standard time offset from GMT. o rulename is the name of the RULE specification that determines when DST is in effect for this zone. The rulename may be an underscore (_) to indicate that this zone does not use DST. o standard-name and dst-name are the names by which this zone is referred to during standard time, and during Daylight Savings Time, respectively. These are the names by which DEFINE TIMEZONE selects the local time zone. If there are no DST rules, the dst-name should be specified as an underscore (_). The optional COMPILED_IN keyword indicates that this rule is compiled-in and need not be loaded, as long as no other rules conflict with it. If you edit a COMPILED_IN ZONE specification, youmust remove the COMPILED-IN keyword to force the ZONE speicification to be loaded. The first of the following examples shows the definition of the normal United States Mountain time zone. The second example, for Arizona, shows the definition of a Mountain time zone that does not observe Daylight Savings Time. Zone US/Mountain -7:00 US MST MDT COMPILED_IN Zone US/Arizona -7:00 _ MST New Features and Enhancements in Version 5.3 1-9 1.2.7 Format of RULE Specification RULE rulename startyear ruletype save start-date end-date The RULE specification describes a set of rules for determin- ing the times DST is in effect: o rulename is the name of the RULE specification in ZONE specifications. o startyear is the year during which this DST rule takes effect. The rule remains in effect until a later startyear is specified in a rule with the name rulename. o ruletype specifies the type of DST rules. There are three permitted values: o DST indicates normal Northern Hemisphere Daylight Savings Time rules, which change at the time and date indicated. o REV_DST indicates normal Southern Hemisphere Daylight Savings Time rules. o NULL indicates that no Daylight Savings Time is in effect during the specified years. o save indicates the difference between Standard Time and DST. The following example illustrates the United States Federal Daylight Savings Time rules: Rule US 1987 DST 1:00 First Sunday April 2:00 Last Sunday October 2:00 Rule US 1976 DST 1:00 Last Sunday April 2:00 Last Sunday October 2:00 Rule US 1975 DST 1:00 23 February 2:00 Last Sunday October 2:00 Rule US 1974 DST 1:00 6 January 2:00 Last Sunday October 2:00 Rule US 1970 DST 1:00 Last Sunday April 2:00 Last Sunday October 2:00 1.2.8 Loadable Time Zone Rules Provided with TCPware The next table shows the loadable rules provided in the TCPWARE:TIMEZONES.DAT file; you may modify or augment as appropriate for your location. ______________________________________________________________ Time Zone Country_Name__Rule_Name________Name________GMT_Offset_(hours)_ GMT GMT 0 UT UT* 0 US-Military US-Military/Z* Z 0 US-Military US-Military/A* A -1 1-10 New Features and Enhancements in Version 5.3 ______________________________________________________________ Time Zone Country_Name__Rule_Name________Name________GMT_Offset_(hours)_ US-Military US-Military/B* B -2 US-Military US-Military/C* C -3 US-Military US-Military/D* D -4 US-Military US-Military/E* E -5 US-Military US-Military/F* F -6 US-Military US-Military/G* G -7 US-Military US-Military/H* H -8 US-Military US-Military/I* I -9 US-Military US-Military/K* K -10 US-Military US-Military/L* L -11 US-Military US-Military/M* M -12 US-Military US-Military/N* N 10 US-Military US-Military/O* O 2 US-Military US-Military/P* P 3 US-Military US-Military/Q* Q 4 US-Military US-Military/R* R 5 US-Military US-Military/S* S 6 US-Military US-Military/T* T 7 US-Military US-Military/U* U 8 US-Military US-Military/V* V 9 US-Military US-Military/W* W 10 US-Military US-Military/X* X 11 US-Military US-Military/Y* Y 12 US US/Eastern* EST/EDT -5 US US/Central* CST/CDT -6 US US/Mountain* MST/MDT -7 US US/Pacific* PST/PDT -8 US US/Yukon* YST/YDT -9 US US/Hawaii* HST -10 New Features and Enhancements in Version 5.3 1-11 ______________________________________________________________ Time Zone Country_Name__Rule_Name________Name________GMT_Offset_(hours)_ US/East- US/East- EST -5 Indiana Indiana* US/Arizona US/Arizona* MST -7 Canada Canada/NewfoundlaNST/NDT -3:30 Canada Canada/Atlantic* AST/ADT -4 Canada Canada/Eastern EST/EDT -5 Canada Canada/Central CST/CDT -6 Canada Canada/Mountain MST/MDT -7 Canada Canada/Pacific PST/PDT -8 Canada Canada/Yukon YST/YDT -9 Canada Canada/SaskatchewCST -6 Israel Israel IST/IDT +2 Australia Australia/TasmaniEST/EST 10 Australia Australia/QueenslEST 10 Australia Australia/North CST 9:30 Australia Australia/West WST 8:00 Australia Australia/South CST 9:30 Australia Australia/VictoriEST/EST 10 Australia Australia/NSW EST/EST 10 Australia Australia/YancowiCST/CST 9:30 Europe Britain GMT/BST 0 Europe Europe/Western* WET/WET- 0 DST Europe Europe/Middle* MET/MET- 1 DST Europe Europe/Central* CET/CET- 1 DST Europe Europe/Eastern* EET/EET- 2 DST Poland MET/MET- 2 DST 1-12 New Features and Enhancements in Version 5.3 ______________________________________________________________ Time Zone Country_Name__Rule_Name________Name________GMT_Offset_(hours)_ Turkey EET/EET- 3 DST Japan Japan* JST +9 Singapore Singapore* SST +8 New_Zealand___NewZealand*______NZST/NZDT___+12________________ *This time zone is also compiled in. 1.2.9 Setting Time Zone and Time Offset Information Using CNFNET, you need to specify your local time zone information as it relates to the offset from Universal time. You can choose to either: o Specify a time zone offset or name as a fixed value that you must set manually for each Daylight Savings Time change. o Choose to have the Network Time Protocol (NTP) server change the system clock and time offset automatically according to information you provide. This first method has been available with prior versions of TCPware and the process has not changed. The second version, for automatic changes, is a new feature that has been added to the existing configuration prompts. The following describes the CNFNET process for configuring the time zone information. 1.2.9.1 Using CNFNET to Configure Time Zone Information CNFNET displays the following information and prompts: You need to specify local time zone information. Time zones may be specified as a fixed value, which must be set manually for the Daylight Savings Time change, or you can use the NTP (Network Time Protocol) server to change the system clock and time offset Do you want have to have NTP set the time zone and time offset automatically [N]? o If you accept the default (N), then the screen displays: Offset from Universal time in hours and minutes: +HHMM (east) or -HHMM (west) Universal time zone: UT, UTC, GMT North American time zone: EST, EDT, CST, CDT, MST, MDT, PST, PDT Military time zone: Any single letter A through Z except J New Features and Enhancements in Version 5.3 1-13 You may enter a non-standard time zone name, although this is discouraged for Internet use. If you use a non-standard name, you are prompted to enter the offset from Universal time as well. Enter the offset from UT or the local time zone name [UT]: -0500 If you enter an unknown time zone name, you are prompted for the Universal time offset for the time zone. For the offset from Universal time, enter +HHMM or -HHMM, for the number of hours (HH) and minutes (MM) the time is offset. The + is for east of the Central Meridian and the - is for west of the Central Meridian. Your entry must be five characters long, so include any leading or trailing zeros. o If you enter Y at the prompt in the first display, then the following appears on the screen: Enter the time zone name and time zone rules (if different from default rules). TCPWARE:TIMEZONES.DAT contains a list of available time zone rules, or local definitions may be defined in TCPWARE.TIMEZONES.LOCAL. Enter the time zone name : EST Enter the time zone rule : When you use CNFNET to configure time zones, you are prompted for information that defines symbols in the TCPWARE_ CONFIGURATION.COM file. o Zone Name o Time Zone Rule You can skip the Time zone rule prompt when a compiled-in time zone is specified. Define your local time zone information according to its offset from Universal time. You can either manually change the offset as needed or configure the offset to be done automatically. If you have it done automatically, you need to run NTP. Enter your local time zone's offset from Universal time or its symbolic time zone abbreviation (see Table 1-1). 1.3 Configuration, Startup, and Shutdown o The TCP-OpenVMS core configuration includes a prompt at which you can enter your Maintenance Agreement (MAS) number, available from your Software Maintenance and Support Agreement with Process Software. A @TCPWARE:CNFNET MAS component configuration is also available to enter this 1-14 New Features and Enhancements in Version 5.3 value. Once entered, you can display it using the NETCU SHOW VERSION/ALL command (PIR 788). o CNFNET includes steps for configuring IMAP (see Sec- tion 1.9) and SMUX (see Section 1.21). o When using the CNFNET menus, CNFNET now prompts to save changes when restarting from the main menu. o The NFS Server configuration includes a bit 8 (mask value 128) for the security mask (NFS_SECURITY) option. This value disables PCNFSD's deletion of printed files from the spool directory (see also Section 1.17) (PIR 923). 1.4 Domain Name Services o Certain NameD statistics and cache dump, reload, and debug setting commands were added in NETCU. (See Section 1.13 for details.) o The TCPWARE_NAMED_MAX_CACHE_TTL system logical was added to define the maximum time-to-live (TTL) on a resource record placed in memory cache. Up to now, the maximum was one week (604800 seconds); if the TTL was set higher, it would cache data for only one week. Because this value was too high for some systems with heavily used name servers and limited memory, the TCPWARE_NAMED_MAX_CACHE_TTL can be set to a more appropriate value (PIR 830). For example: $ DEFINE/SYSTEM/EXEC TCPWARE_NAMED_MAX_CACHE_TTL 86400 This resets the maximum TTL to 86400 seconds (one day). To put the change into effect, restart the server or use the NETCU RELOAD NAMED command (note that reloading affects new caching only). o The Resolver purges all but the last three versions of the DNS_CLIENT.LOG and DNS_ERROR.LOG files. o The maximum wait time for the TCPWARE_DNS process to start was increased from 10 to 60 seconds (PIR 880). 1.5 Drivers o SOCK_DGRAM sockets (for BGDRIVER, INETDRIVER, and UDP- DRIVER) can bind to a broadcast address. While this is useful to receive packets sent to just that broadcast ad- dress, you cannot use the socket to send datagrams, since the broadcast address is not a valid source address in a datagram. New Features and Enhancements in Version 5.3 1-15 1.6 FTP-OpenVMS Client o * The FTP Client no longer automatically converts the user name, password, and account to lowercase if they were not supplied on the OPEN or USER command line and thus prompted for. If the user is prompted for these parameters, they must enter them in the proper case, since quotes are no longer needed to maintain case. (D/E 265) Warning If users have not been using the correct case to enter the parameters, they could find that they need to now. o The PUT and COPY/REMOTE commands support use of asterisk (*) wildcards after a semicolon (;) in remote file specifications. This creates the same version in the destination file as in the source file (instead of creating a new version). If the server is not OpenVMS, the version number is part of the filename. TCPware does not issue a warning if the server host already has a higher numbered version. Also, if the server host already has the version specified, TCPware overwrites the old file with that version. 1.7 * FTP-OpenVMS Server o * In the previous release of TCPware, a feature was added to the FTP server so it would be more "UNIX-friendly" and accommodate pathname specifications in some Web browsers. The server recognizes the forward slash (/) and, if the client is not an OpenVMS machine, the NLST command returns a directory filename without a .DIR extensions and returns an error message when retrieving a directory file. This change means that a space character is required between the filespec and any OpenVMS file transfer type qualifier. This release of TCPware (Version 5.3-3) includes an enhancement that allows you to disable this feature so that the FTP server can accept a VMS mode transfer qualifier without requiring the space character between the filespec and the qualifier. To disable the feature, define the following logical: $ DEFINE/SYSTEM TCPWARE_FTPD_NOUNIX_SYNTAX "TRUE" To return to the default behavior, remove this logical (D/E 345). 1-16 New Features and Enhancements in Version 5.3 o * A recent change to the FTP server behavior causes the server to strip the .DIR extension from the file name of a directory when the NLST function is requested. This has been causing some problems for clients that rely on the .DIR extension to designate a directory file. Therefore, an enhancement was made to the FTP server to look for the existence of the logical TCPWARE_FTPD_KEEP_DIR_EXT and, if defined, not remove the .DIR extension. To use this new feature, define the system/exec mode logical: $ DEFINE/SYSTEM/EXEC TCPWARE_FTPD_KEEP_DIR_EXT TRUE To return to the default behavior, remove this logical (D/E 1054). o * In TCPware 5.2, a security enhancement was made so that Server-FTP reports a 501 Bad parameter value error if a port less than 1024 is specified. Some FTP clients, how- ever, choose to use a privileged port for the destination of data transfer. An enhancement was made in this release of TCPware so you can disable this security feature. To disable the feature, define the following logical: $ DEFINE/SYSTEM/EXEC TCPWARE_FTPD_ALLOW_PRIV_PORT "TRUE" To return to the default behavior, remove this logical (D/E 686). o * Some users may have had a problem getting a directory listing with the FTP server because the name specified for the subprocess exceeded the limits VMS allows. This has been corrected (D/E 867). o The FTPSAMPLE.C sample program was updated. o The TCPWARE_FTP_MAXREC logical was added to the FTP Server so that you can override the 8192-byte maximum record size default for ASCII file transfers (PIR 873). 1.8 HELP o The TCPware HELP files available online also include MESSAGES help for information on common error messages and how to diagnose them (see Chapter 3). New Features and Enhancements in Version 5.3 1-17 1.9 IMAP Server Support o TCPware added support for the Internet Message Access Protocol (IMAP) server. IMAP is a method of accessing messages from a mail server as if the storage were local. The IMAP mail server resides on the local OpenVMS system and typically serves remote PC users. TCPware's implementation is based on IMAP version 4, Revision 1. IMAP contrasts with the Post Office Protocol (POP3) server by retaining messages on the server, instead of copying them onto the client (and deleting them from the server). TCPware configuration asks the following questions in setting up the IMAP server: - Do you want to enable the IMAP server? - Enter the user (account) the IMAPD process should execute as. - Do you want to enable message caching? - What is the desired message logging level? (NONE, ERROR, INFO, DEBUG) 1.10 INETDRIVER Services o The INETDRIVER_CLIENT.C and INETDRIVER_SERVER.C sample programs were added. 1.11 Installation o The TCPware installation procedure (VMSINSTAL) checks previous images of each installed component (PIR 865). If you select not to install a component that was installed with a previous version, a message to remove the component using the TCPWARE_REMOVE command appears during VMSINSTAL; for example: * Do you want to install NFS-OpenVMS Client (TCP/IP Services) [YES]? NO A previous version of NFS-OpenVMS Client is currently installed, and may no longer be functional. You can remove the old component by issuing the command: @TCPWARE:TCPWARE_REMOVE CNFS * Do you want to install NFS-OpenVMS Server (TCP/IP Services) [YES]? 1-18 New Features and Enhancements in Version 5.3 o The VMSINSTAL procedure always prompts for TCPWARE_ COMMON: and TCPWARE_SPECIFIC: definitions. If they are already defined, the current values are used as defaults. Otherwise, SYS$COMMON: and SYS$SPECIFIC:, respectively, are the default definitions (PIR 894). 1.12 Kerberos o The default expiration date for the Kerberos database (KDB) was changed to 31-DEC-2099 23:59:59 for year 2000 compliance (see Section 1.31). 1.13 Network Control Utility o The NETCU ADD EXPORT command for the NFS-OpenVMS Server now includes the UPPERCASE keyword for the /FILENAME qualifier (PIR 850). UPPERCASE changes the default case for exported filenames from lowercase to uppercase, for SRI filename mappings only. The full syntax of the command is: $ NETCU ADD EXPORT /FILENAME=(SRI, UPPERCASE) Examples of filename conversions: VMS Name Lowercase Uppercase -------- --------- --------- foobar.txt foobar.txt FOOBAR.TXT $foobar.txt FOOBAR.TXT foobar.txt foo$bar.txt fooBAR.TXT FOObar.txt o The NETCU RELOAD EXPORT command was added to implement changes to the NFS-OpenVMS Server EXPORT database. Use this command on all NFS servers in the cluster. (See also Section 1.17 (PIR 772). o The DEBUG commands now include the /DECODE qualifier that shows all packets in the TCPDUMP format. For example, the DEBUG/IP command shows all IP packets in TCPDUMP output format. You can combine it with any other qualifier except /OCTAL and /DECIMAL, since TCPDUMP output is in hex format. The /LINE qualifier does not apply in this case. o The following NameD related commands were added: - DUMP NAMED STATS - Dumps the current NameD statistics in the TCPWARE:NAMESERVER.LOG file. New Features and Enhancements in Version 5.3 1-19 - DUMP NAMED CACHE - Dumps the current contents of the NameD cache to a file, TCPWARE:NAMED_DUMP.DB, in RFC 883 format. - RELOAD NAMED - Reloads the DNS name server's database files, if needed, by reading the NAMED.BOOT file and checking the zone information. - SET NAMED DEBUG - Rereads the TCPWARE_NAMED_OPCOM_ SEVERITY, TCPWARE_NAMED_LOGFILE_SEVERITY, and TCPWARE_ DNS_DEBUG logicals. - SET NAMED NODEBUG - Overrides the current debug settings from the TCPWARE_DNS_DEBUG logical. o The following NETCU commands were added for the INET devices: - SET INET_TCP PROBE_TIMER value - SET INET_TCP DROP_TIMER value - SHOW INET_TCP PROBE_TIMER - SHOW INET_TCP DROP_TIMER These commands perform similar functions for the INET devices as the SET BG_TCP and SHOW BG_TCP commands added in TCPware Version 5.2 for the BG devices. The commands also affect services added using the STREAM protocol (PIR 890). o The NETCU REMOVE SERVICE command now prompts for the port and protocol parameters. They used to be optional and by omitting them, all services on all ports and protocols were removed. The /ALL qualifier was added to take the place of this functionality. Use /ALL to remove all services on all ports and protocols (PIR 925). o The NETCU SHOW CONNECTIONS command now includes the /LOCAL and /REMOTE qualifiers to include the address and port for incoming and outgoing connections, respectively. o The SHOW VERSION /ALL command now shows versions of the NetWare images and includes display of the user's Maintenance Agreement (MAS) number, if entered during configuration (PIR 788). 1-20 New Features and Enhancements in Version 5.3 1.14 NFS-OpenVMS Client o The NFS Client now includes the /NOVERSION qualifier for the NFSMOUNT command to enforce a limit of one version for a file (PIR 368). The command is: $ NFSMOUNT /NOVERSION server "nfs-path" [[mountpoint ]logical]] With /NOVERSION in effect, unversioned files stay un- versioned, and new files are unversioned along with any subsequent upgrades (providing consistency with most NFS servers). When higher versions exist, no more are created and the lowest is purged with each file upgrade. /NOVER- SION is disabled when connected to a TCPware NFS server. (/VERSION is normally the default, allowing multiple file versions.) To prepare a directory for use with /NOVERSION, purge and rename its files (making sure to back them up first): $ PURGE *.* $ RENAME *.*;* *.*;1 1.15 NetWare Services NetWare Services have been retired and after June 30, 1998 are no longer supported. Note FSS-OpenVMS does not support the latest version of Novell's Client 32 software. Also, since OpenVMS disk quota information is not passed to NetWare users, the DOS free disk space value on the FSS drive is meaningless. o The default location of the FSS-OpenVMS system vol- ume changed from SYS$SYSDEVICE:[FSS_SYS_VOLUME] to SYS$SPECIFIC:[FSS_SYS_VOLUME]. However, if the former already exists from a previous TCPware version, it re- mains the default. If both directories already exist, the SYS$SPECIFIC: location becomes the default. You can still specify any other location during CNFNET (PIR 415). o The FSS_CONSOLE utility now includes the DISABLE FORGE_ DOSTIME and ENABLE FORGE_DOSTIME commands. ENABLE FORGE_ DOSTIME enables "forging" the current DOS file date and time when copying or renaming a file to the OpenVMS FSS volume. This allows you to preserve the original date and time for a file rather than adopting the system date and New Features and Enhancements in Version 5.3 1-21 time during the copy or rename. DISABLE FORGE_DOSTIME is the default (PIR 519). o The FSSadmin utility now supports Windows NT 3.51 and 4.0 workstations. o The FSS-OpenVMS now supports creating a new folder on the FSS-mapped drive in the Windows95 Explorer (PIR 893). 1.16 Network Time Protocol o The slewalways configuration file command was added to NTP. NTPD normally steps the clock when there is a relatively large time error to adjust. The slewalways command directs the local NTP server to always slew the clock. This command is useful to avoid an abrupt one-hour clock change when daylight savings time (DST) changes occur, in which case NTPD slews the clock over a period of about 10 hours. o The multicastclient configuration file command was removed. 1.17 NFS-OpenVMS Client and Server o The NFS Server now supports ISO 9660 format CD-ROMs in addition to Files-11 ODS-2 structure disks (PIR 756). o The NFS Server NFS_SECURITY basic parameter now includes a bit mask 8 value of 128 that disables PCNFSD deletion of printed files from the spool directory (PIR 923). o The NETCU ADD EXPORT command now includes the UPPERCASE keyword for the /FILENAME qualifier. (See Section 1.13 for further details.) (PIR 850) o The NETCU RELOAD EXPORT command was added (see Section 1.13 for further details). The TCPWARE_NFS_DYNAMIC_EXPORT logical was also added to reload updates to the shared database on the cluster (PIR 772). Use the TCPWARE_NFS_DYNAMIC_EXPORT logical as follows: $ DEFINE/SYSTEM/EXEC TCPWARE_NFS_DYNAMIC_EXPORT CLUSTER 1.18 ONC RPC Programming o The ONC RPC Management Routines now include the getr- pcbynumber and getrpcbyport routines. The Client Routines also include the clntraw_create routine. 1-22 New Features and Enhancements in Version 5.3 1.19 Remote Copy Program o The Remote Copy Program's RCP command was enhanced with the /VMS qualifier. The default is /VMS=TCPWARE, in which case RCP attempts a TCPware-style VMS mode transfer. This retains VMS file attributes across copies. Use /VMS=MULTINET for a transfer involving a MultiNet machine. The existing /NOVMS qualifier still disables maintaining VMS file attributes during a third-party copy (PIR 874). 1.20 SMTP-OpenVMS o The TCPWARE_SMTP_NOPREFIX logical was added to suppress the SMTP% prefix from being prepended to incoming addresses. This is useful for OpenVMS Version 6.2 and later systems that detect SMTP mail addresses and invoke the appropriate transport, rendering the prefix unnecessary (PIR 869). Define the TCPWARE_SMTP_NOPREFIX logical as follows (restart the SMTP component to put the logical definition into effect): $ DEFINE/SYSTEM/EXEC TCPWARE_SMTP_NOPREFIX * 1.21 SMUX Support o TCPware now supports the SNMP Multiplexing (SMUX) protocol. SMUX is an SNMP subagent extension protocol (described in RFC 1227). Each SMUX subagent or peer registers a Management Information Base (MIB) subtree with the SNMP Agent. The SMUX protocol passes requests for objects residing in a registered MIB subtree from the SNMP Agent to the subagent. The subagent then passes the SNMP query results back to the SNMP Agent. The practical limit to the number of peers is 30. The TCPware configuration (CNFNET) now asks whether you want to activate the SNMP SMUX service on your host. 1.22 Startup and Shutdown Note Editing the TCPWARE_CONFIGURE.COM file is unsup- ported and can lead to errors in CNFNET operation. A comment to the effect was added to the TCPWARE_ CONFIGURE.COM file (PIR 777). New Features and Enhancements in Version 5.3 1-23 1.23 TCPDUMP Utility o TCPDUMP was upgraded to: - Comply with TCPDUMP Version 3.3.1a2 - Support the IPV6, UDP6, TCP6, ICMP6, RSVP, and RSVP6 protocols - Support ISO protocols CLNS, CLNP, ESIS, ISIS, TPIP, TUBA, and IDRP - Support the ATM NHRP protocol - Support NFSv3 - Add the IPX keyword for filter expressions - Add two new TCPDUMP options: o -g (or /NETWORK) - Translates network and broadcast addresses to domain names o -z (or /ASCII) - Displays each packet in hex with the ASCII text equivalent o TCPDUMP drops fewer packets when using the Ethernet device, and decodes additional protocols (such as TALK and TELNET). 1.24 TELNET-OpenVMS Client o The CLOSE_DASSGN keyword was added to the TELNET /CRE- ATE=(PERMANENT) command so that you can close the TCP connection when all process channels are deassigned (PIR 905). Common usage for CLOSE_DASSGN is: TELNET /CREATE=(PERM,RETRIES=0,CLOSE_DASSGN) node port CLOSE_DASSGN specifies that when there are no channels assigned to the NTA device, the underlying TCP connection closes. The default is to keep the connection open. Setting RETRIES=0 means that when either end closes the TCP connection, there are no automatic reconnects. However, the associated TELNET client NTA device was enhanced to try reconnecting without delay for one time, when a write operation occurs to the permanent NTA device. If RETRIES is NOT set to 0, automatic retries occur when the connection closes. If all retries fail and the NTA device is written to, TCPware attempts the specified number of retries. 1-24 New Features and Enhancements in Version 5.3 Here is a typical command to create a TELNET connection to a printer (note that /RAW was used to avoid sending TELNET options negotiation data): TELNET /RAW /CREATE=(PERM,RETRIES=0,CLOSE_DASSGN) node port After TELNET creates a permanent NTA device with an underlying TCP connection, the NTA device's reference count drops to 0 and the TCP connection closes. When a write operation is started to the NTA device, TCPware makes one attempt to reestablish the TCP connection. Meanwhile, TCPware holds the data being written so that it can send it when reconnected. If reconnects fail, TCPware drops the write data. When the application deassigns the channel to the NTA device, its TCP connection closes again. o The NOTCONNECTED_OK keyword was added to the TELNET /CREATE=(PERMANENT) command so that you can create a permanent NTA device even if a TCP connection cannot be set up initially (PIR 905). Common usage for NOTCONNECTED_OK is: TELNET /CREATE=(PERM,NOTCONN) node port With this change, if the problem is in connecting and not in resolving the node name, and if you use the NOTCON- NECTED_OK keyword, then TCPware creates a disconnected NTA device with the "unavailable" device characteristic. Reconnects occur as before. 1.25 TELNET-OpenVMS Server o The TCPWARE_TELNETD_FLAGS logical that can be set in the TELNET_CONTROL.COM file now has an additional bit 9 (mask value 512) that, if set, tries to return the ACCPORNAM string as a hostname,port value (exam- ple: bart.process.com,1094). If it cannot return the hostname, it returns an address,port value (example: 192.168.1.2,1094). However, bit 9 is ignored if bit 8 (mask value 256) is set on (PIR 795). The ACCPORNAM field is limited to 63 bytes, so that if the resulting string is longer, TCPware can truncate or even drop the port number. The TELNET_CONTROL.COM file includes the following line that, when uncommented, sets bit 9: $ ! TELNETD_FLAGS == TELNETD_FLAGS .OR. 512 ! Add port number to ACCPORNAM New Features and Enhancements in Version 5.3 1-25 1.26 TELNET Programming Library o The TELNET_SAMPLE.C sample program was added. 1.27 Terminal Server Print Services o The INIT/QUEUE/ON qualifier now includes the EXPNTAB option to allow expansion of tab characters to the equivalent number of space characters in print files (PIR 842). 1.28 TFTP Utility o TFTPD now retransmits a data packet if the client retrans- mits its last acknowledgement (ACK) (PIR 891). 1.29 TIMED o The TIMEDC CLOCKDIFF command now takes IP addresses along with hostnames. 1.30 WebCNF o WebCNF now reports logical values for IMAP, LPS, NFS, SMTP, and SNMP. 1.31 Year 2000 Support o All date references in the TCPware components were tested to ensure integrity in the year 2000 and beyond. Dates are now in four-digit format. Caution The OpenVMS operating system has a documented delta time limit that can cause a serious error in some applications and OpenVMS components beginning on or around 19-MAY-1997. DIGITAL provides Engineering Change Orders (ECOs) that removes the delta time limit. Applications and OpenVMS components most likely to experience errors are those that pass delta time arguments with values exceeding 9999 days on system- supplied date routines. The most likely date that these errors occur is 19-MAY-1997:00:00, which is 10,000 days after the common UNIX time origin of 1-JAN-1970. 1-26 New Features and Enhancements in Version 5.3 DIGITAL strongly recommends that all customers running the affected versions of OpenVMS install one of the following ECOs: o OpenVMS Alpha Version 6.1 through Version 7.0: ALPLIBR05_070 o OpenVMS VAX Version 5.5 through Version 7.0: VAXLIBR06_070 Systems running OpenVMS Alpha Version 7.1 and OpenVMS VAX Version 7.1 are not affected and do not need to install the ECO. The following OpenVMS components and software products are known to be affected by the delta time limit. The ECOs correct the problems observed in these products. o OpenVMS SECURITY Server - OpenVMS Alpha V7.0 only o DECwindows Motif for OpenVMS - OpenVMS Alpha V7.0 only o Distributed Computing Environment (DCE) for OpenVMS - OpenVMS Alpha V6.2 only o OpenVMS DECthreads - OpenVMS Alpha and OpenVMS VAX V5.5-2 through V7.0 o (OSU) DECthreads HTTP Server (freeware provided with the OpenVMS VAX V5.5-2 through V7.0 Internet_Product_Suite - OpenVMS Alpha and OpenVMS Other software products running on OpenVMS might also experience errors stemming from this delta time limit. Contact the appropriate software vendor for more information. New Features and Enhancements in Version 5.3 1-27 Chapter__2_______________________________________________________ Corrections Made in Version 5.3 This chapter contains information about the defects fixed for the release of Version 5.3-2 and Version 5.3-3 of TCPware for OpenVMS. The information about the corrections made in this release (5.3-3) is preceded in text by an asterisk (*). 2.1 BGDRIVER o Raw socket handling problems were corrected. A security hole was also filled related to BG devices. 2.2 DNIPDRIVER The following two problems with DNIPDRIVER were fixed: o Corruption of non-paged pool under certain circumstances that typically resulted in a system crash. o Frequent incorrect reports of protocol errors that would cause the TCP connection to be unnecessarily re-established for a DNIP link. Note that these errors were logged in the NETCP.LOG file, so reporting of these errors in the future should be far less frequent. Also, NETCP was modified to include SS$_PATHLOST in the list of restartable errors for DNIP lines. Previously, if this error was reported for a TCP connection, the DNIP line would shut down instead of restarting (PIR 889). 2.3 Domain Name Services o * A memory leak in the DNS nameserver has been fixed. (D/E 392) o A few logicals in DNS were causing problems in the server shutdown process. The deassigning of these logicals has been moved from DNS_CONTROL.COM to SHUTNET.COM to correct the problem. (D/E 249) TCPWARE_RES_OPTIONS TCPWARE_DOMAINLIST TCPWARE_NAMESERVERS Corrections Made in Version 5.3 2-1 o Certain local hostname-to-address resolutions no longer fail in TCPWARE_DNS (PIR 896). o A few memory leak problems in NameD were fixed (PIR 791, PIR 809). o A few NameD syslog messages were changed to be more like those of OpenVMS. 2.4 Dynamic Host Configuration Protocol o * The DHCP server was sometimes exiting due to an access violation while re-reading the configuration file. The access violation no longer occurs. (D/E 802) o * When the DHCP server was required to send a DHCPNAK reply, the server would exit with an access violation. The server now correctly sends the DHCPNAK reply. (D/E 715) o * In the DHCPTAB file, negating string-valued tags (for example, "dn") caused the DHCP server to crash. This has been fixed in this release. (D/E 931) o * The DHCPTAB tag "nl" no longer incorrectly assigns the "nl" tag entry value as an IP address. (D/E 907) o * Using the NETCU SHOW DHCP/VERIFY command would deliver an INVLEASE error incorrectly if there was a statically assigned IP address using the "ip" tag having a lease, and there were no free-pool ranges covering the IP address. This problem has been fixed for this release and no error is given. (D/E 906) o A network class entry of 0.0.0.0 (nc=0.0.0.0) no longer needs to be combined with network list (nl) and address list (al) tags (PIR 833). o An ar tag no longer takes precedence over an ip tag if the ip tag is more specific (PIR 895). o All characters after the line continuation backslash (\) in the DHCPTAB configuration file are now ignored (PIR 822, PIR 833). 2.5 FINGER Service o * FINGERD used to report the day of the week and the hours and minutes of the login time for the process. This has been changed so that FINGERD now reports this information only if the user has been logged on for less than seven days. If the user has been logged on for more than seven days, the date in the format dd-mm-yy is reported instead. 2-2 Corrections Made in Version 5.3 Note Although a two-digit year is reported, it is compliant with the year-two-thousand reporting. Example: Old format: SMITH ZEUS Mary Smith 0 Fri 14:36 FTA419: New format: JONES ZEUS John Jones 14 10-DEC-97 FTA372: 2.6 FTP-OpenVMS Client and Server o * FTP can be invoked with a logical name set to point to an initialization file to be run at startup. If, in this startup file, you set a value for ERROR_EXIT, the value was ignored on subsequent exits from FTP. This has been fixed so now the value is kept and displayed on exit from FTP. (D/E 800) o * The FTP library documentation states that the parameter OUTPUT, a descriptor containing the name of the output file, is read only; however, FTP was writing to this variable. The handling of this parameter has been changed to isolate the user's descriptor from being written to. (D/E 460) o When using PUT/FDL (or COPY/FDL /LOCAL) to transfer an FDL file to the remote system, a transfer error now issues an error message on the client. Also, an FDL file transfer error on a multiple transfer (MPUT or COPY/MULTIPLE) aborts the connection. NOTE: If you use PUT/FDL TEMP.TXT, the error message refers to the actual FDL file (TEMP.TXTFDL). o When using a DECNET-style "GET" command from a non-UCX system, writing to a file on the FTP server no longer causes an access violation. o Remote client commands such as COPY/FTP and others that automatically send "anonymous" as user and "e-mail" as password work properly to systems with case-insensitive logins. o Using the FTP Graphical User Interface (DECW_FTP) to transfer binary files no longer produces files with an invalid format (PIR 879). Corrections Made in Version 5.3 2-3 2.7 * GateD o * In GateD, the OSPF protocol could not handle received OSPF packets larger than the MTU of the interface on which the packet is received. This could occur in an environment with bridged datalinks of different MTUs, such as Ethernet/FDDI or if the OSPF neighbor chose to send OSPF datagrams larger than the link MTU. This has now been fixed and is no longer a problem. (D/E 961) 2.8 * IMAP Server The IMAP server has been updated with the following: o * Users with expired accounts are disallowed. o * Connections that are idle for 30 minutes will be disconnected. o * International character sets are now supported. o * Several new directives are available by users for their .IMAPRC file. These are in addition to the ones listed on page 16-11 in the Management Guide. Table 2-1: New IMAP Configuration Directives in User's ____________.IMAPRC___________________________________________ set inbox [foldername] Instructs the server to map the INBOX to the specified foldername. The default is NEWMAIL. set case-insensitive- See the Management Guide. False by folders [true|false] default. set do-purge-reclaim See the Management Guide. True by [true|false] default. set allow-child-folders See the Management Guide, page 16- [true|false] 11, allow-subfolders tag. False by default. set autofile-messages-to- Instructs the server to move read folder [foldername] messages to the specified folder upon closing INBOX. By default, read messages remain in INBOX until moved by the user. set newmail-timer [delta- See the Management Guide. time]_________________________________________________________ The following directives are available in the system-wide TCPWARE:.IMAPRC file: 2-4 Corrections Made in Version 5.3 Table_2-2:__System-wide_TCPWARE:.IMAPRC_Directives____________ set max-ping-count Disables new mail checks on folders [number of messages] containing more than the specified number of messages. set x400-gateway-mapping Specifies a Mail-11 <-> RFC822 Mail [gateway] gateway. set trailing-header- Specifies a line of text which marker [text] indicates the start of the RFC822 header in a message, if it does not appear at the beginning. set enable-full-cache Determines whether the server [true|false] should cache message bodies. By default, only the current message is cached. set smtp-transport-prefix Specifies the prefix used to [prefix] denote Internet addresses (ex: smtp%"user@foo.com"). By default, the value is smtp. set decnet-address [node Creates a mapping between a DECnet namespace domain] node and/or namespace and an internet-style domain name. All parameters must be specified, and quote marks ("") may be used to skip a value. Example: set decnet-address alcor "" eng.process.com set decnet-address elnath "" doc.process.com The DECnet mail header: To: ALCOR::BAZYL From: ELNATH::ANDERSON Becomes the RFC822 header: To: bazyl@eng.process.com From:_anderson@doc.process.com________________________________ o * The IMAP server was terminating with ACCVIO as soon as a user connected to the server, when the user's home directory was specified by a logical and the MAIL> SHOW ALL command displayed a different device specification between the mail folder directory and file as follows: Your mail file directory is DISK$USER:[USER.MAIL] Your current mail file is SYS$SYSDEVICE:[USER.MAIL]MAIL.MAI;1 Corrections Made in Version 5.3 2-5 This problem has been fixed in this release (D/E 869). o * A problem with the IMAP server exiting with ACCVIO status, after deleting messages and then referencing a later message has been fixed in this release. (D/E 1102) 2.9 INETDRIVER o Raw socket handling problems were corrected. A security hole was also filled related to INET devices. 2.10 Installation and Removal o * STARTNET was changed so that now when it invokes SHOW LICENSE/BRIEF, you receive a warning if your TCPware license will expire within 30 days (on recent versions of VMS). If you need more frequent checks, you can create a batch job to do a daily SHOW/BRIEF for all your licenses. (D/E 274) o * The TCPWARE_NW_FILES logical now gets deassigned when TCPware or FSS are shut down. (D/E 431) o * Upon startup, TCPware checks for the logicals TCP, UDP, IP, INET, RMT, RCD, BG, and QX. If any of these logicals have been previously defined on your system, then a warning "%TCPWARE-W-BADLOGICAL" would be generated. A conflict with logicals of similar names, such as TCP0, UDP0, BG0 could also occur. TCPware now checks for these logicals also and will issue a similar warning. If this does occur on your system, you need to redefine the conflicting logical. (D/E 1088) o * The installation process was copying some NetWare files regardless of the NetWare services selections. Now these files are copied only if one or more NetWare Services (FSS, NPS, OR TES) are installed. (NetWare is no longer a supported part of TCPware.) (D/E 880) o * During installation, if TCPWARE_COMMON pointed to SYS$COMMON, and TCPWARE_SPECIFIC pointed to SYS$SPECIFIC, then the TCPWARE_ROOT logical was set to SYS$SYSROOT. In all other cases, TCPWARE_ROOT is set as a search list, pointing to TCPWARE_SPECIFIC:, TCPWARE_COMMON: (D/E 560). o The VMSINSTAL procedure properly checks free block requirements for non-system-disk installations (PIR 883). o All logicals are deassigned after an aborted installation. 2-6 Corrections Made in Version 5.3 o TCPWARE_REMOVE.COM works properly with non-system disk- installations. Previously two passes were required. 2.11 IPDRIVER o * When certain illegal IP packets were received, it caused the system to crash. A fix was made to the IPDRIVER that deals with the illegal packets and keeps the system running (D/E 522). o * The IPDRIVER was looping back on the kernel stack under error conditions with some interfaces; for example, FDDI, causing system crash problems. This problem has now been corrected so the looping back will not occur (D/E 580). o An IPDRIVER LAN VCI ports problem was fixed in which LAN ports would not automatically restart (PIR 866). o ICMP handling returns as much of the original datagram as will fit into the ICMP datagram without it exceeding 576 bytes (as recommended in RFC 1812). The previous action returned only the original IP header plus 8 bytes (64 bits) of the "data." 2.12 Kerberos o * To be consistent with other component configuration procedures, the Kerberos configuration procedure no longer includes the prompt "Do you want to configure Kerberos Services?" (D/E 446). o The NETCU SHOW TICKETS TGT command now works properly. o Kerberos files are now properly cleaned out of the TCPware directory during a TCPWARE_REMOVE. 2.13 Line Printer Services o * The LPS VMS printer symbiont was keeping files marked for deletion in the TCPWARE_LPD_SPOOL directory, which affected the amount of free disk space. This was caused by a network connection going down during printing. The LPS VMS printer symbiont is now fixed so it does not occur anymore (D/E 339). o The TCPWARE_VMSLPRSMB symbiont no longer causes a print failure with a corrupted control file if the domain name of the local system is longer than 25 characters (PIR 907). Corrections Made in Version 5.3 2-7 o The TCPWARE_VMSLPRSMB symbiont no longer goes into a stalled state if the file consists of form feed characters and the file length is two bytes or less (PIR 909). o The TCPWARE_VMSLPRSMB symbiont no longer leaves temporary files in the TCPWARE_LPD_SPOOL directory. This condition occurred when a network connection went down during printing (PIR 927). 2.14 LPD Server o * When the LPD server submited batch jobs to a batch queue, it discarded or retained on error with "-RMS-F- SYN, file specification syntax error" if the queue was set /RETAIN=ERROR. The LPD server has been modified to submit batch jobs to a batch queue with the job name to be a legal VMS file name. With this change, the batch queue can properly generate log files with a legal VMS file specification (D/E 1080). 2.15 NetWare Services o Access is no longer denied to users trying to read or write files on the FSS server even though they have access privileges but do not have Supervisor privileges (PIR 851). o Windows 3.x users connecting to an FSS drive using the File Manager and pressing ALT-Enter to see the properties of a directory with an eight-character name no longer get the message "File manager cannot find the specified path." (PIR 835) o Fixed length files are now copied correctly to a drive mapped to a fixed length record format volume (mount the volume and use the "/record=(format=fixed:xxx)" option in the command line). In older versions of FSS, the fixed length record file being copied would become a stream format file (PIR 900). o FSS-OpenVMS no longer generates two log files under a single name. It uses the names SAP_SVR.LOG and SAP_SVR_ DETACH.LOG for the two log files. o Break-in detection works properly with FSS-OpenVMS on an AXP system. A message in the FSS.LOG file indicated that the $AUDIT_EVENT "system service or exec routine is not loaded" when it actually was. 2-8 Corrections Made in Version 5.3 o FSSadmin was fixed as follows: - FSSadmin better handles the loss of a server. FSSadmin would at times hang if a connected server went away. FSSadmin now detects the loss of the server during its regular update and cleans up its connection. - Extra drive mappings are no longer left around after an ADD USER or DELETE USER operation on some platforms (NT with the Microsoft Client). - FSSadmin no longer has problems with keyboard access to check boxes. - The Time Restrictions grid of the Modify Menu no longer allows random text entry. - When adding or deleting Console Operators on the Server Defaults screen, you no longer get an "Invalid Property Value" error and terminate FSSadmin. - The items in a deleted user's SYSMAIL directory are properly cleaned up. Caution On NT 4.0 systems running FSSadmin at the same time as PC-Xware, some of the DECwindows applications might experience problems. In particular, the pull-down menus and selecting text do not work properly. When you shut down FSSadmin again, the applications work normally again. o A year 2000 correction was made in NPS-OpenVMS. It no longer writes a wrong time stamp in the QSG.LOG file if the time passes the year 2000. o The NPS process now starts up properly (PIR 846). o The QXDRIVER no longer decreases the user account's Buffered I/O quota (visible through SHOW PROCESS/QUOTA) whenever the NPSCP utility id used (PIR 862). o QXCP no longer has a potential problem on a non-system-disk installation. Corrections Made in Version 5.3 2-9 2.16 NETCU o * The NETCU SHOW CONNECTIONS command now properly reports the offending argument when there are syntax errors in the /LOCAL and /REMOTE qualifier values (D/E 556). o * A change in NETCU SHOW SM and SHOW SM_BAK truncates host names at the 120th character. Because the remaining characters (the ones after the 120th character) are required for the REMOVE_SM or REMOVE SM_BK commands, the displayed name cannot be used. While it is unlikely that host names of this length are used, it is a good practice to limit names to less than 120 characters when adding hosts to the table (D/E 957). o * The NETCU TCPDUMP command now properly parses the command expression without causing a parsing error or unexpected results (D/E 963). o * Various problems with the use of BG0: as a logical name have been solved; however, it is still recommended not to use BG0: as a logical (D/E 879). o * The NETCU command SHOW VERISON/ALL, no longer goes into an infinite loop if there are no NetWare components installed (D/E 571). o * Using SPAWN from NETCU without proper privileges no longer causes NETCU to exit after displaying the insufficient privileges status message. It now displays NETCU-E-REQFAIL and returns you to the NETCU prompt (D/E 457). o The SET FILTER command was fixed (see Section 2.21). o A problem was fixed where NETCP was unable to read the privilege mask of suspended processes making NETCU requests. The symptom was that NETCU would show a "failed to perform requested operation" error intermittently (PIR 613, PIR 847). o NETCU NAMED signaling commands no longer exit NETCU if you lack the privileges to use the commands. 2.17 * Network Control Process o The Network Control Process (NETCP) was starting one more process than the limit for which a service had been set; for example, NETCP was starting two servers when the DHCP service had been set for one. This has been fixed so that NETCP no longer creates one more process than the limit set on the service (D/E 747). 2-10 Corrections Made in Version 5.3 2.18 Network Time Protocol o NTP no longer gets hung up or goes to sleep when you perform a SET TIME command to adust for daylight savings time. o NTP recognizes hostnames (instead of just internet addresses) in NTP.CONF file entries (PIR 904). o NTP supports the broadcastclient configuration file command. o You can no longer specify random local-master or master- clock stratum. A message warns that the stratum must be between 0 and 13. o NTP better handles external time changes. 2.19 NFS-OpenVMS Client and Server o * There was a problem with files being reported as locked when they were not locked and all access was denied. A problem with the TCPware Network Lock Manager (NLM) was found and corrected (D/E 753). o * The NFS server was issuing bugcheck messages to the NFS server log file incorrectly and the following messages were being displayed: %NFS-E-BUGCHECK, unexpected close status fid(nnnnn,nn,n) -SYSTEM-F-IVCHAN, invalid I/O channel %NFS-E-BUGCHECK, deassign failed -SYSTEM-F-IVCHAN, invalid I/O channel The problem has been fixed in the server and these messages should no longer appear (D/E 821). o During CNFNET configuration, changing "Do you want PCNFSD enabled?" (the NFS_PCNFSD_ENABLE logical) from PRINTING- ONLY to YES works properly. o During CNFNET configuration, entering an invalid access identifier (NFS_ACCESS_IDENTIFIER) issues an error and a repeated prompting instead of continuing with the configuration. o When editing a file using EDT, ACLs are correctly propa- gated to the next version of the file. o When creating files with the RMS create-if-nonexistent option, the proper status is returned to indicate that a new file was created. For RMS indexed files, this allows RMS to write the proper prologue information to the new file. Corrections Made in Version 5.3 2-11 o The Network Lock Manager no longer starts if neither the Client nor Server is configured (PIR 823). o The NFS Client no longer issues GETATTR requests with filehandle 0 when building directories (PIR 920). o A large file copied from an NFS export now returns uncorrupted data (PIR 837). o A memory corruption problem involving zero-block variable length files was fixed. o NETCU lets users remove export, group, and proxy entries for hostnames that are no longer defined. It previously gave an error that the hostname could not be translated to an IP address (PIR 921). o Changes in version limits now creates a new ADF file. o The mount count on a background mount now increments correctly. o The mount count on an overmount of a shared mount now decrements correctly and the logical definition is correct. o The Network Status Monitor now validates hostnames with monitor requests. 2.20 NSLOOKUP Utility o NSLOOKUP now allows using Ctrl/C to abort non-interactive NSLOOKUP queries (PIR 834). o NSLOOKUP now returns a "No nameserver addresses known" message instead of an access violation if the TCPWARE_ NAMESERVERS logical is incorrectly defined and an LS command or multiple parameter query is performed. 2.21 Packet Filtering o The packet filtering file now accepts a tab character between the first two fields (action and protocol) and no longer returns a syntax error with the NETCU SET FILTER command. 2-12 Corrections Made in Version 5.3 2.22 Post Office Protocol o * The intrusion record of the POP3 server has changed so that a different user with the same IP address is not blocked by the intrusion record of another user (D/E 248). Change from: ::POP3 Change to: .pop3:: o The POP3 server properly delivers SMTP mail that was stripped of the SMTP% address prefix (see Section 1.20) (PIR 906). o POP3 no longer causes an access violation when it retrieves a mail message containing multiple lines greater than 8192 characters. o An incomplete network send of a buffer requiring another send no longer causes an access violation (PIR 881). o POP3 no longer returns garbage when retrieving a mail file with VFC records. o POP3 now supports year 2000 dates. 2.23 PWIPDRIVER o * A change was made in PWIPDRIVER to support the new DIGITAL NTDS product. 2.24 * RMT Server o When RMTSETUP tried making a connection to an RMT server, and the server did not execute (due to noprivs, no image file, and so on), an error message to close the connection was received; however, the error was not being processed by the RMTSETUP command. This has been fixed so now all data received from the server is processed as an error message, displays the error message, and exits with the TCPWARE Connection Error. 2.25 * RSH o RSH now displays the hostname in a NOSUCHHOST error instead of displaying a NOSUCHNODE error without hostname (D/E 482). Corrections Made in Version 5.3 2-13 2.26 Remote Copy Program o * Previously, when using RCP, errors exited normally instead of with an error status (except for fatal errors). This has been changed so that an error message appears for all types of errors and the DCL $STATUS symbol is set (D/E 823). 2.27 RSH Server o * When a remote program prompts you for input, the RSH client now correctly echoes the input. Also, line editing of the input works correctly and pressing the Enter key terminates a line instead of using Ctrl/J (D/E 919). o The RSH server default device assigned to SYS$ERROR is no longer deleted if explicitly closed while executing. TCPware now permanently deletes it upon process termination (PIR 838). 2.28 SMTP-OpenVMS o * When SMTP received mail with commas in the comment string in the From: or Reply-To: fields, an access violation would occur; for example: From: user@domain (username, (617), 222-2222) SMTP now recognizes commas within these comment strings (D/E 198 and D/E 381). o * @SMTP_QONLY no longer results in an invalid IF-THEN-ELSE structure (D/E 881). o The SMTP Server no longer loops if the address in the RCPT TO: field omits the local part. It now returns the message "501 Address specification error: missing local part." (PIR 855) o When mail is returned to an ALL-IN-1 mail user, the local part of the address is no longer missing the leading quote (PIR 902). o SMTP can send mail messages containing more than 1000 characters per line as multiple lines. It can also handle zero record lengths (as in the case of NL:) (PIR 919). o The SMTP Client no longer access violates when trying to bounce mail back to an address with an invalid domain part and the TCPWARE_SMTP_RELAY logical (the "Enter the mail relay option" prompt in CNFNET) is set to "ALL" or "UNKNOWN." (PIR 928). 2-14 Corrections Made in Version 5.3 o The SMTP Server no longer access violates or terminates because of a BADBLOADR error when processing a mail message with long TO: addresses (PIR 888). o A mail message file containing more than 1024 bytes no longer causes SMTP_MAILSHR to access violate. 2.29 SNMP Services o * With SNMP, there may be multiple subtrees registered by multiple subagents. When using getnext, SNMP would walk only the subtrees registered to the subagent having the lowest numbered objectID requested and not query other subagents. This has been fixed so that the agent now looks at all registered subtrees in numerical order by objectID until the requested value is found or the list of subtrees has been exhausted (D/E 967). 2.30 * Socket Library Services o * Non-octal numbers are no longer wrapped by inet_aton() into the octal number space (D/E 850). 2.31 TALK Utility o TALK no longer creates extra, empty log files. 2.32 TCPDRIVER Services o * In this version of TCPware, a change has been made to TCPDRIVER's receive data processing such that receive buffers are merged under certain conditions to reduce system memory requirements (D/E 891). o * If TCP NoListen port was being used on an AXP system, there had been a problem with system crashes. The cause of this has now been fixed (D/E 1083). o A TCPDRIVER crash problem was fixed (PIR 897, PIR 903). 2.33 TCPDUMP Utility o * TCPDUMP previously did not recognize the FWA FDDI device (FPA interface) and returned a "device unknown" error. This device is not properly recognized by TCPDUMP. Corrections Made in Version 5.3 2-15 Also, TCPDUMP previously attempted to erroneously listen to device xxA1: when interface xxx-1 was specified, and resulted in a "device unknown error". This is corrected to properly listen on xxB0 instead (D/E 526). Note The xx or xxx is device specific. Also, this fix makes xxx-2 listen to xxC0; x-3 listen to xxD0, and so on. o * TCPDUMP supports a new option/qualifier that enables more detailed decoding of RPC based services. The new option/qualifier is (D/E 660): R_RPC -"R" all|udp|tcp /RPC [=ALL|UDP|TCP] Note that for a UNIX-style option, the "R" must be uppercase and quoted. The option/qualifier values are: - ALL (default) - decode both UDP and TCP - UDP - decode only UDP - TCP - decode only TCP For option, you must specify one of these three values. The following RPC protocols are decoded: - NFS - Portmapper - Network lock manager version 1 - Network lock manager version 3 - Net status - Mount - PCNFS version 1 - PCNFS version 2 o * TCPDUMP now binds to IPA0: device if no device is specified. Also, it no longer searches for the first network interface if the specified device is not found (D/E 1000). o * When TCPDUMP was run on a VAX, terminating TCPCUMP and exiting did not free memory and it kept on consuming bytecount limit. This has been fixed in this release of TCPware (D/E 1085). 2-16 Corrections Made in Version 5.3 o TCPDUMP recognizes the EOA Ethernet device on a TADPOLE laptop. o When running a TCPDUMP listing on an IP device with verbose mode turned on (-v), TCPDUMP no longer reports "bad checksum!=0" for all outgoing packets. o IPX filtering now works with Raw Ethernet, 802.3, and 802.3/SNAP (PIR 844). o The TCPDUMP command issued from NETCU now handles quoted strings correctly. 2.34 TELNET-OpenVMS o * There was a problem in doing an OPEN or WRITE operation to a permanent NTA device, which was disconnected. This has now been fixed in the NTdriver. The new action is: If a connection to the remote port is broken, then: o The client attempts to reconnect to the remote port if RETRIES >0. o New write $QIOs stall (buffering the write data) and attempt to reconnect for the number of retries specified. (If RETRIES=0, then one reconnect is done.) If a reconnection succeeds, then the buffered data is sent. If all attempts to reconnect fail, then the $QIO ends with SS$_HANGUP signaled (D/E 547). o * There had been a problem with incoming TELNET failing with a SS$_IVBUFLEN status when the length of the host name string was exactly 20 characters. This has been corrected in this release (D/E 662). o * TELNET now correctly goes into TN3270 mode when connect- ing to IBM TCP/IP stack version 3.1 through the DIGITAL AltaVista firewall (D/E 865). o Opening a remote TELNET session in a DECterm no longer connects to the local host when the SHOW DISPLAY command shows Transport: LOCAL and you specify the hostname instead of IP address (PIR 854). o Using the TELNET/CREATE command in batch mode no longer causes "invalid device name" errors (PIR 886). o A TELNET/CREATE/LOGICAL command defining a supervisor-mode logical no longer needs to be run from a privileged process (PIR 813). Corrections Made in Version 5.3 2-17 o Several TELNET client NTA device problems were fixed: - Improper access to QIO parameters (PIR 829) - A problem when sending output to a server that discon- nects while a reconnection is in progress (PIR 861) o TELNET no longer loses the connection with a "requires LOG_ IO" message for users without LOG_IO privilege on OpenVMS Version 6.x machines (PIR 871, PIR 901) o Using TELNET /TN3270 to open a TN3270 session after escaping and then closing the previous session no longer fails to enter TN3270 mode. o When connecting to a remote IBM host through DIGITAL's Al- taVista Firewall (DIGITAL UNIX version) using a transparent TELNET proxy server, TELNET options are properly negotiated for TN3270 mode (PIR 845) o The SET HOST /TELNET and SET HOST /TN3270 command no longer fail with "PORT_NUMBER" errors. 2.35 TIMED o The TIMEDC TRACE command checks arguments better. 2.36 TRACEROUTE Utility o TRACEROUTE no longer loops when encountering a node that returns ICMP unreachable status with certain codes, notably 13 for "communication administratively prohibited by filtering." TRACEROUTE properly terminates with a new annotation, !X, to indicate the fact; for example: traceroute to skat.process.com (198.115.142.57), 30 hops max, 38 byte packets 1 skat.process.com (198.115.142.57) 3 ms !X 2 ms !X 1 ms !X Also, other previously unrecognized codes are annotated with !n, n being the integer value of the ICMP unreachable code. o TRACEROUTE no longer causes an access violation if a switch parameter is omitted (PIR 912). 2.37 VMS Communications Interface Support o LAN VCI ports are automatically restarted after wire disconnects (PIR 866). 2-18 Corrections Made in Version 5.3 2.38 WebCNF o "Return to" links were fixed on the "Basic DNS Nameserver Configuration" screen. o Modifying a secondary zone no longer deletes the old one without modifying it, and no longer adds unrecognizable addresses. o TCPWARE_CONFIGURE.COM is no longer left in cache if changes are submitted. o A name server configured as a primary server is no longer considered a caching server. o Disabling a nameserver now works properly. o The Process Software corporate logo is now included on the main WebCNF page. Corrections Made in Version 5.3 2-19 Chapter__3_______________________________________________________ Changes to the TCPware Documentation Set This chapter describes the changes made to the TCPware printed and online documentation, online help, and information available after press time. For the release of TCPware 5.3- 2, the documents were reformatted and the Installation & Configuration Guide and Management Guide were reorganized. Information that pertains to this release (Version 5.3-3) is preceded in text by an asterisk (*). Note Certain chapters that were of a conceptual nature in the User's Guide and Management Guide were removed to make room for more functional material. Much of the conceptual material is now found in Process Software's TCP/IP Reference Library: A Collection of Practical Guides to TCP/IP Networking. The library includes the TCP/IP Defined, DNS Defined, and Network Security Defined booklets. Also, descriptions of error messages were removed from the documentation. They are available as part of TCPware Help by entering: HELP TCPWARE MESSAGES 3.1 Chapter-by-Chapter Descriptions User's Guide o * The following information was omitted from the documenta- tion for the OPEN and USER commands (D/E 912): When the Client-FTP is invoked from within a command procedure or batch job, it does some complex processing with regard to the username, password, and account parameters. Following the basic conventions listed next can help avoid problems with these parameters: - It is best to explicitly specify the username, password, and account parameters with the OPEN or USER command. Changes to the TCPware Documentation Set 3-1 If they are not provided with the command, they are read from the command procedure as the next data lines. This can cause problems as the behavior is slightly different depending on whether the command procedure is being run interactively or in batch mode. In interactive mode, the user is prompted for the password (in batch mode it is read from the command procedure). Thus, to avoid problems, explicitly specify the username and password with the OPEN command. - If you want only to use a command procedure interactively (not as a batch job), you can have FTP prompt the user for the password instead of obtaining it from the command procedure. To do this do not specify the password with the OPEN or USER command. o * The description of the PUT qualifier, /MULTIPLE, incorrectly states that the remote host's server must support the FTP NLST command for remote wildcard operation to work is incorrect. FTP MPUT does not use the NLST command (D/E 827). o Introducing TCPware for OpenVMS and Functional Overview include descriptions of the new IMAP and SMUX features. o The concepts chapters, Overview of TCP/IP Networking and Overview of X.25 Networking, were removed (see the previous Note). o FTP: Transferring Files mentions use of the asterisk (*) wildcard after a semicolon (;) in remote filespecs to preserve file versions during a PUT or COPY/REMOTE . Under command descriptions, equivalent commands that are described elsewhere are listed as "Equivalents"; command synonyms that are not described elsewhere are listed as "Synonyms." The Troubleshooting section was also removed (see the previous Note). o RCD and RMT: Remote CD-ROMs and Tapes was moved before the Remote Copy Program (RCP) chapter. o SMTP: Transferring Files mentions the option to suppress the SMTP% prefix for incoming mail was added to page 10-3 (see Section 1.20). o TELNET: Connecting to Remote Terminals includes a new sub- section added to the Creating a Permanent NTA Device sec- tion to describe use of the CLOSE_DASSGN and NOTCONNECTED_ OK keywords to the TELNET/CREATE=PERMANENT command. The OPEN command description also includes keyword descriptions (see Section 1.24). Some of the permanent NTA descriptions were also improved. 3-2 Changes to the TCPware Documentation Set o References lists the newly supported RFCs. Installation & Configuration Guide The Installation & Configuration Guide was completely reorganized. It is no longer divided into sections. The transition is now smoother from product installation, core environment configuration, TCP/IP services configuration, NetWare Services configuration, to startup and testing. o Before You Begin is an introduction to and preparation for TCPware installation. o Installing TCPware takes you through the product installa- tion. The new prompt requesting where to install the TCP- ware node-specific files was documented (see Section 1.11). A new "Installing TCPware on Mixed Platform Clusters" sec- tion was added. An "Installing Other Products" section describes the VAX P.S.I., INGRES/Net, and Oracle installa- tions previously located in a later chapter. o Configuring the TCP/IP Core Environment describes how to configure the TCP-OpenVMS core component. A description on entering your Maintenance Agreement Number (MAS) was added (see Section 1.3). o Configuring the TCP/IP Services describes how to configure the TCP/IP services. New sections were added or reorga- nized: - A section on configuring the IMAP Server was added (see Section 1.9). - The full NFS-OpenVMS Client and NFS-OpenVMS Server configuration steps are presented in one chapter rather than in separate chapters. - The SNMP Services configuration section describes configuring the SNMP SMUX Service (see Section 1.21). The SNMP subagent configuration prompts were also made more descriptive. o Configuring the NetWare Services is now a separate chapter. o Starting and Testing TCPware combines two former chapters and adds testing information. o Sample Installation and Sample Configuration reflect changes and additions to the installation and configura- tion. Installed Files includes the new files added. WebCNF User's Guide Changes and improvements were made to this guide. Changes to the TCPware Documentation Set 3-3 Management Guide * Chapter 1, Domain Name Services (D/E 401, D/E 897, and D/E 861) o Example 1-5 on page 1-7 incorrectly refers to tulip.flower.com and lilac.flower.com from Figure 1-2 on page 1-6. These should not be included because they are part of a different subnet. In Figure 1-2, the address for aster.flower.com is incorrect. It should read 172.16.0.1. A trailing dot is missing at the end of the domain name for the examples of resource records on the following pages: ____________________________________________________________ Page Resource Number______Record______Correct_Domain_Name_________________ 1-17 AFSDB daisy.flower.com. 1-23 MINFO err.tulip.flower.com. 1-28 RP daisy.flower.com. iris.flower.com.0 1-29 RT marigold.flower.com. pansy.flower.com. 1-34 X25 lily.flower.com (instead of ________________________Relay.Prime.COM)____________________ 3.1.0.1 Reorganization The Management Guide was completely reorganized. It is divided more functionally into the following parts: o Managing Hosts - Includes chapters on the Domain Name Services and the DHCP/BOOTP Server. Changes include: - Domain Name Services has much of its concept material removed. It includes a section "Caching Data in Memory" that describes use of the TCPWARE_NAMED_MAX_CACHE_TTL logical (see Section 1.4). The chapter also includes the "Dynamic TCP/IP Load Balancing" section that used to be a separate chapter. o Managing Networks - Includes chapters on network inter- faces, Cluster Alias Failover, managing SNMP, and X.25 networks. Changes include: - Common Interfaces, combines five previously separate chapters. It now describes the Ethernet, FDDI, Token Ring, ATM, HYPERchannel, IP-over-DECnet, proNET, and WAN Device Drivers interfaces. 3-4 Changes to the TCPware Documentation Set - Serial Link Interfaces: PPP and SLIP, combines two previously separate chapters. - Managing SNMP Services includes material on SMUX (see Section 1.21) and a section on the template configuration file. o Managing Routing - Includes chapters on the routing protocols (primarily GateD). o Managing Time Services - Includes chapters on the NTP and TIMED protocols. Changes include: - Network Time Protocol (NTP) includes the slewalways configuration file command and no longer includes the multicastclient command (see Section 1.16). o Managing Applications - Includes chapters on managing the FTP-OpenVMS Client and Server, NFS-OpenVMS Client and Server, print services, Berkeley R Commands, mail services (SMTP-OpenVMS, IMAP, and POP3), and the TELNET-OpenVMS Server. Changes include: - Managing NFS-OpenVMS Client includes a "File Version Mapping" section and a "Limiting File Versions" section to show use of the /NOVERSION qualifier. The qualifier description was also added to the NFSMOUNT command (see Section 1.14). - Managing Print Services, the "Terminal Server Print Services" section includes a description of the EXPNTAB option to the INIT/QUEUE/PROC=TCPWARE/ON= qualifier for the Terminal Server Print symbiont (see Section 1.27). - Managing R Commands combines three previously separate chapters and includes the RSH and RMT servers. - Managing Mail Services includes an "IMAP Server" section (see Section 1.9), and describes the SMTP_NOPREFIX server parameter (see Section 1.20). - Managing TELNET-OpenVMS Server describes the new bit 9 (mask 512) setting for the TCPWARE_TELNETD_FLAGS logical that can be set in the TELNET_CONTROL.COM file (see Section 1.25). o Managing Security - Includes chapters on general TCPware security, Access Restrictions, Token Authentication, the Kerberos Server and applications, and IPSO. Changes include: - Access Restrictions combines the Incoming and Outgoing Access Restrictions chapters into one. Changes to the TCPware Documentation Set 3-5 - Managing Kerberos combines the Kerberos Server, Kerberos for R Services, and Kerberos for TELNET chapters into one. o Managing Additional Support - Includes chapters on PATHWORKS support, tunneling DECnet over IP, the X Display Manager (XDM), and DECwindows support. Changes include: o Network Testing Tools - Includes a chapter on testing tools such as DISCARD, FINGER, NETCU DEBUG, NSLOOKUP, PING, QUOTED, TCPDUMP, and TRACEROUTE. Changes include: - Network Testing Tools includes the testing tools previously scattered in separate chapters into one. The testing tools are organized alphabetically as sections on CHARGEND, DAYTIMED, DISCARD, ECHO, FINGER, IDENT, NETCU DEBUG, NSLOOKUP, PING, QUOTED, TCPDUMP, TIME, and TRACEROUTE. The "TCPDUMP" includes descriptions for the -g (/NETWORK and -z (/ASCII) options and qualifiers (see Section 1.23). NETCU Command Reference o Chapter 2, NETCU Commands In the parameters description of the ADD ROUTE command, the parameter line is incorrectly identified as the default. o The NETCU Command Reference includes the additions and changes to commands described in Section 1.13. NetWare Services Administrator's Guide This guide was not reissued for TCPware Version 5.3. Note the following changes: o Introducing FSS-OpenVMS: For a description of feature changes that would affect descriptions in this chapter, see Section 1.15. o Configuration and Printer Sharing: For a change in the default location of the FSS directory that would affect page 2-1 of this chapter, see Section 1.15. Note that certain references to the FSS directory (such as on page 3-1 of the System Security chapter) still refer to the old default location. Also, references to using FSSCON or FSSUTIL in NetWare Version 4.x should also include reference to FSSadmin. o FSS_CONSOLE Reference: For a description of the new ENABLE FORGE_DOSTIME and DISABLE FORGE_DOSTIME commands, see Section 1.15. Also, the ENABLE FSS95 command should include the statement that you should use the command if you use 3-6 Changes to the TCPware Documentation Set Microsoft Client for NetWare. If you use Novell Client for NetWare, you might not need this command. o FSSadmin Utility: This chapter should also include mention of Windows NT Version 3.51 and Version 4.0 workstation support (see Section 1.15). Programmer's Guide * Chapter 7, FTP Library o FTP_GET_CCB library routine The format description for FTP_GET_CCB implies that length is optional; rather, length is required. The format should read: FTP_GET_CCB ccb, field-code, value, length (D/E 824) * Chapter 15, ONC RPC RTL Management Routines o In the section Routine Name Conventions, the differentia- tion between the Digital C Socket Library and the TCPware Socket Library needs additions and updates. Replace the information on page 15-2 with the information as described next (D/E 859). Note In the current documentation, information designated as OLD pertains to the ONC RPC services used with VAX C and the TCPware Socket Library; information designated as NEW pertains to the RPC XDR services used with DEC C the Digital C Socket Library. Routine Name Conventions In this chapter all routines are documented according to their standard UNIX names. Routines that are unique to TCPware have UNIX-style names. OLD: If you are writing code in the C language, you may use the routine names used in this chapter. If you are writing code in a different language, you must use the TCPware names defined in the TCPWARE_ COMMON:[TCPWARE.INCLUDE.RPCOLD]RPC.H file. These names all begin with the letters ONCRPC. Header Files All RPC application programs include the RPC.H header file. Locations for this file are: Changes to the TCPware Documentation Set 3-7 OLD: SYS$COMMON:[TCPWARE.INCLUDE.RPCOLD]RPC.H NEW: UCX$RPC:RPC.H The RPC.H file includes the files listed in Table 15.1. ____________________________________________________________ File_Name________Purpose____________________________________ Pertains to DEC C and VAX C AUTH.H Used for authentication AUTH_UNIX.H Contains XDR definitions for UNIX-style authentication CLNT.H Contains various RPC client definitions IN.H Defines structures for the internet and socket addresses RCP_MSG.H Defines the RPC message format SVC.H Contains various RPC server definitions SVC_AUTH.H Used for server authentication TYPES.H Defines UNIX C data types XDR.H Contains various XDR definitions Pertains to DEC C Only NETDB.H Defines structures and routines to parse /etc/rpc Pertains to VAX C Only ONCRPC_CONST.H Defines RPC characteristics and other constants ONCRPC_FUNC.H Maps ONC RPC routine names with their UNIX counterparts ONCRPC_STRUCT.H Defines structures for the RPC client and _________________server_counters____________________________ There is an additional header file not included by RPC.H that is used by the xdr_pmap and xdr_pmaplist routines. The file name is pmap_prot.h, and the location is: OLD: TCPWARE_COMMON:[TCPWARE.INCLUDE.RPCOLD]PMAP_PROT.H NEW: UCX$RPC:PMAP_PROT.H * Chapter 3, TCPDRIVER Services 3-8 Changes to the TCPware Documentation Set The following information pertains to the section TCPDRIVER Services Program Examples: o The file for the FINGER protocol that contains sample source code, using TCPDRIVER servers, is also TCPWARE_ COMMON:[TCPWARE.EXAMPLES]FINGER.C (D/E 433). Link the files to the TCPware Socket Library as follows for both Alpha and VAX systems for DEC C: $ FINGER :==$FINGER $ LINK FINGER SYS$INPUT/OPTIONS SYS$SHARE:TCPWARE_SOCKLIB_SHR/SHARE $ Ctrl/Z For VAX systems with VAX C: $ CC FINGER.C $ LINK FINGER,SYS$INPUT/OPTIONS TCPWARE:UCX$IPC.OLB/LIBRARY SYS$SHARE:VAXCRTL/SHARE $ Ctrl/Z Chapter 10, SNMP Extendible Agent API Routines In this chapter, you are advised that you need to copy the shareable image you build for your SNMP subagent to the SHS$SHARE: directory. You also need to install the image because of some global declarations in the code. Install the image using this command: $ INSTALL ADD SYS$SHARE:IMAGE-NAME.EXE/OPEN/HEAD/WRITE/SHARE New sample programs were added to this guide: o UCX Compatibility Services includes the BGDRIVER_UDP_ CLIENT.C and BGDRIVER_UDP_SERVER.C sample programs and their build instructions. o TCPDRIVER Services includes the TCPDRIVER_CLIENT.C, TCPDRIVER_SERVER.C, FINGER.C, and FINGERD.C sample programs and their build instructions. o UDPDRIVER Services includes the UDPDRIVER_CLIENT.C and UDPDRIVER_SERVER.C sample programs and their build instructions. o INETDRIVER Services includes the INETDRIVER_CLIENT.C and INETDRIVER_SERVER.C sample programs and their build instructions (PIR 649). o FTP Library includes new build instructions for the FTPSAMPLE.C program. o TELNET Library includes new build instructions for the TELNET_SAMPLE.C program. Changes to the TCPware Documentation Set 3-9 o The ONC RPC Programming section includes new routines, as described in Section 1.18. Some of the routines were relabeled NEW, or OLD, or NEW and OLD. The descriptions for the XDR routines xdr_double and xdr_float were also changed. 3.2 HELP Files The major change to the HELP files was the addition of the MESSAGES help (see the Note at the beginning of Chapter 3). Other HELP file changes mirror enhancements to the documen- tation and reflect product modifications covered in these Release Notes. 3.3 Documentation PostScript Files on CD-ROM The TCPware manual set is available online as PostScript (.PS) files on the CD-ROM media. The files are located in the [TCPWARE53.POST_DOCS] directory, with a subdirectory for each manual, and are arranged sequentially by section and chapter in each subdirectory. The explanatory index for the files is included in the README.TXT file in the top level directory. 3-10 Changes to the TCPware Documentation Set