Archive-Date: Thu, 09 May 1996 16:47:36 GMT Subject: inexpensive tcp for vms 5.43 Message-ID: <4mt7t8$kls@news-central.tiac.net> From: murrayb@tiac.net (Murray Bob) Date: Thu, 09 May 1996 16:47:36 GMT Reply-To: murrayb@tiac.net Is there any freeware or inexpensive software that will allow users to telnet into vms 5.43 and an ftp server. This will be connected to IBM pcs under windows. If you have any ideas please e-mail me Thanks Murray Bob ================================================================================ Archive-Date: XXX, 20 May 1996 12:16:08 -0400 Subject: TCPware V5.1 Message-ID: <1996May20.121609.1976@delta.process.com> From: ostrom@process.com (Andy Ostrom) Date: 20 May 96 12:16:08 -0400 MIME-Version: 1.0 Content-Type: Text/Plain; charset=ISO-8859-1 I am pleased to report that we are now shipping TCPware V5.1 to new customers. The shipment of updates to customers with support contracts will take place about a week from now, after CDROMs have been received from the vendor. The major new features of TCPware V5.1 include: Point-to-Point Protocol (PPP) Classless InterDomain Routing (CIDR) in compliance with RFCs 1517, 1518, 1519 SNMP Agent Extensions (Extensible MIBs) TCPware's SNMP agent now supports subagents serving private Management Information Bases (MIBs) NFS Client Perfomance Enhancements DNS Server V4.9.3 (resolves CERT advisory 96-02) POP3 Server The Post Office Protocol (POP) Version 3 server provides PC users with access to incoming OpenVMS mail Path MTU Discovery NFS-OpenVMS Server XQP+ Multithreading Support Provides a performance improvement for NFS file lookup and access You can now drive TCPware configuration, startup, and shutdown using an up front menu interface RCD Client Local users can access remote CD-ROM devices Much More! Customers with support contracts that want to download the kit from our FTP Server are invited to send mail to "support@process.com" for download instructions. The size of these kits are as follows: tcpware051-alpha.zip 35270 blocks (18MB) tcpware051-vax.zip 15701 blocks ( 8MB) tcpware051-doc.zip 10108 blocks ( 5MB) I will post the release notes for V5.1 as a followup to this article. Andy Ostrom Product Line Manager, OpenVMS Products Process Software Corporation ostrom@process.com ================================================================================ Archive-Date: XXX, 20 May 1996 12:20:30 -0400 Subject: Re: TCPware V5.1 - [1/3] Message-ID: <1996May20.122030.1977@delta.process.com> From: ostrom@process.com (Andy Ostrom) Date: 20 May 96 12:20:30 -0400 References: <1996May20.121609.1976@delta.process.com> MIME-Version: 1.0 Content-Type: message/partial; id="832609372@Andy Ostrom"; number=1; total=3 Content-Type: Text/Plain; charset=ISO-8859-1 TCPware for OpenVMS Version 5.1 Release Notes May 1996 These Release Notes cover enhancements and changes made to TCPware for OpenVMS Version 5.1 since Version 5.0. Process Software Corporation Framingham, Massachusetts ________________________ May 1996 __________ Copyright ©1996 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 can be found on the copyright page of the TCPware for OpenVMS User's Guide. Contents_________________________________________________________ Preface_________________________________________________________v Chapter_1__Highlights_of_Major_New_Features______________________ Chapter_2__New_and_Changed_Features______________________________ 2.1 OpenVMS Version 7.0 Support............................2-1 2.2 CIDR and Variable Length Subnets.......................2-2 2.3 Configuration..........................................2-2 2.4 Configuration: Menu-Driven.............................2-3 2.5 Configuring Database Products..........................2-3 2.6 Domain Name Services (DNS).............................2-3 2.7 Dynamic Host Configuration Protocol (DHCP).............2-7 2.8 FTP-OpenVMS............................................2-8 2.9 GateD..................................................2-8 2.10 Installation...........................................2-8 2.11 Line Printer Services (LPS)............................2-9 2.12 Network Control Utility (NETCU)........................2-9 2.13 Network Time Protocol (NTP)...........................2-10 2.14 NFS-OpenVMS Client....................................2-11 2.15 NFS-OpenVMS Server....................................2-12 2.16 NSLOOKUP..............................................2-12 2.17 NTDRIVER..............................................2-12 2.18 Path MTU Discovery Support............................2-12 2.19 POP3 Server...........................................2-13 2.20 PPP Interface.........................................2-14 2.21 RCD Client............................................2-14 2.22 RCP Command...........................................2-14 2.23 RLOGIN................................................2-14 2.24 RSH Command...........................................2-15 2.25 Serial Line IP (SLIP).................................2-15 2.26 SMTP-OpenVMS..........................................2-15 2.27 SNMP Services.........................................2-16 2.28 SNMP Agent Extensions Using API.......................2-16 2.29 Socket Library........................................2-17 2.30 TELNET-OpenVMS........................................2-17 2.31 TFTP Utility..........................................2-17 iii 2.32 UCX Compatibility Services............................2-18 2.33 VMS Communications Interface (VCI) Support............2-18 Chapter_3__Changes_to_5.0_Made_in_5.1____________________________ 3.1 Alpha System Startup...................................3-1 3.2 BGDRIVER...............................................3-1 3.3 Configuration..........................................3-1 3.4 Domain Name Services (DNS).............................3-2 3.5 Dynamic Host Configuration Protocol (DHCP).............3-3 3.6 FTP-OpenVMS Client.....................................3-4 3.7 FTP-OpenVMS Server.....................................3-5 3.8 GateD..................................................3-5 3.9 Intrusion Detection and Evasion........................3-5 3.10 IPDRIVER Services......................................3-6 3.11 Line Printer Services (LPS)............................3-6 3.12 Network Control Utility (NETCU)........................3-7 3.13 Network Time Protocol (NTP)............................3-7 3.14 NFS-OpenVMS Client.....................................3-8 3.15 NFS-OpenVMS Server.....................................3-8 3.16 PATHWORKS Support......................................3-8 3.17 PING Utility...........................................3-8 3.18 R Commands.............................................3-8 3.19 RCP Command............................................3-9 3.20 RSH Command............................................3-9 3.21 Security-Plus: Kerberos Server Management.............3-10 3.22 Security-Plus: Outgoing Access Restrictions...........3-10 3.23 Security-Plus: Packet Filtering.......................3-10 3.24 SMTP-OpenVMS..........................................3-10 3.25 SNMP Services.........................................3-11 3.26 TELNET-OpenVMS........................................3-12 3.27 Terminal Server Print Services........................3-12 3.28 UCX Compatibility Services and BGDRIVER...............3-12 3.29 VMS Communications Interface (VCI) Support............3-12 3.30 WHOIS Client..........................................3-13 iv Chapter_4__Changes_to_NetWare_Services_in_5.1____________________ 4.1 Major New Changes......................................4-1 4.2 Important Information..................................4-1 4.3 Enhancements...........................................4-3 4.4 FSS-OpenVMS Issues.....................................4-6 4.5 NPS-OpenVMS Issues.....................................4-7 4.6 Fixes in 5.1...........................................4-7 4.7 Other Issues...........................................4-8 Chapter_5__Documentation_Notes___________________________________ 5.1 General Documentation Enhancements.....................5-1 5.2 HELP Files.............................................5-5 Chapter_6__Locating_Software_on_the_Internet_____________________ Tables___________________________________________________________ 1 Document Conventions ............................vi 4-1 Supported NetWare Frame Types ..................4-1 6-1 Software on the Internet .......................6-2 v Preface__________________________________________________________ Intended Audience These Release Notes are for all TCPware for OpenVMS users. Please read these Release Notes before you install, upgrade, or use TCPware for OpenVMS Version 5.1. Organization These Release Notes contain the following chapters: o Chapter 1, Highlights of Major New Features, a list of the major new features in TCPware for OpenVMS Version 5.1 o Chapter 2, New and Changed Features, the enhancements to 5.1 o Chapter 3, Changes to 5.0 Made in 5.1, bugs in Version 5.0 resolved in 5.1 o Chapter 4, Changes to NetWare Services, enhancements to and issues involving the NetWare Services component of TCPware 5.1 o Chapter 5, Documentation Notes, enhancements, late- breaking changes, and errata in the TCPware for OpenVMS documentation set for 5.1 The sections of each chapter are organized alphabetically by TCPware for OpenVMS module. Related Documents The following documents and on-line services contain more information about the use and maintenance of TCPware for OpenVMS and about the topics discussed in these Release Notes: o User's Guide o Installation & Configuration Guide o Management Guide o Programmer's Guide o NetWare Services Administrator's Guide o Software Product Description v o Installation Quick Reference Card o NETCU Quick Reference Card o Network Print Services Quick Reference Card o Terminal Emulation Services Quick Reference Card o On-line TCPWARE Help Conventions In these Release Notes, every use of TCPware means the TCPware for OpenVMS product from Process Software Corporation. Use of OpenVMS generally means the OpenVMS operating system for both Digital Equipment Corporation VAX and Alpha platforms, unless otherwise indicated. The Release Notes also use the conventions listed in Table 1. Table_1:__Document_Conventions________________________________ UPPERCASE OpenVMS commands, files, or processes italics (not Input or message variables, input entered visible in .TXT as lowercase, or documentation titles or output) sections boldface (not User input, often at the $ or other prompt visible in .TXT output) [] In command syntax, optional elements { | } In command syntax, a mandatory choice of elements Note The text that follows contains important _________________information_for_the_user_____________________ vi Chapter__1_______________________________________________________ Highlights of Major New Features The following list identifies the major new features in TCPware for OpenVMS Version 5.1. Chapter 2 includes the full explanation of these new features. o CIDR-Support was added for the Classless Inter-Domain Routing (CIDR) protocol and variable length subnets (see Section 2.2) o Domain Name Services (DNS)-TCPware's DNS was upgraded to the Berkeley Internet Name Domain (BIND) 4.9.3 implementa- tion (see Section 2.6) o Menu-driven Configuration-You can now drive TCPware configuration, startup, and shutdown using an up front menu interface (see Section 2.4) o NFS-OpenVMS Server XQP+ Multithreading Support-Provides a performance improvement for NFS file lookup and access (see Section 2.15) o Path MTU Discovery Support-Provides a performance improve- ment when large packets of data are sent over TCP (see Section 2.18) o POP3 Server-The Post Office Protocol (POP) Version 3 server provides PC users with access to incoming OpenVMS mail (see Section 2.19) o PPP Interface-The Point-to-Point Protocol (PPP) interface allows you to send IP datagrams over serial links in more extensive ways than the Serial Line IP (SLIP) interface (see Section 2.20) o RCD Client-Local users can access remote CD-ROM devices. Configuration is through the RMTSETUP command (see Section 2.21) o SNMP Agent Extensions-TCPware's Simple Network Management Protocol (SNMP) agent now supports subagents serving private Management Information Bases (MIBs) using an application programming interface (API) (see Section 2.28) o Socket Library-TCPware now suggests transitioning to Digital's C Socket Library routines and header files for newer OpenVMS systems (see Section 2.29) Highlights of Major New Features 1-1 Chapter__2_______________________________________________________ New and Changed Features This chapter briefly describes features that are new or changed significantly in TCPware Version 5.1. See Chapter 3 for bug fixes and Chapter 5 for documentation notes. Note TCPware for OpenVMS V5.1 now supports the following versions of OpenVMS: o OpenVMS VAX V5.5-2 and later o OpenVMS Alpha V6.1 and later o OpenVMS VAX and Alpha V7.0 (see Section 2.1) VMS (VAX) V4.x and OpenVMS Alpha V1.5 are no longer supported. 2.1 OpenVMS Version 7.0 Support TCPware now supports OpenVMS V7.0. Digital Equipment Corporation added the following parameters to its SHOW NETWORK command in OpenVMS V7.0 to support TCPware networking: SHOW NETWORK TCPWARE -- brief TCPware networking information SHOW NETWORK TCPWARE/FULL -- full TCPware networking information Digital also added the following parameters to its START/NETWORK and STOP/NETWORK commands in OpenVMS V7.0 to support TCPware networking: START/NETWORK TCPWARE -- works the same as @TCPWARE:STARTNET STOP/NETWORK TCPWARE -- works the same as @TCPWARE:SHUTNET Enable this feature by adding the following line to your SYSTARTUP_VMS.COM system startup procedure: $ @SYS$STARTUP:SYS$NET_SERVICES See the SYS$MANAGER:SYSTARTUP_VMS.TEMPLATE file for more information about the SYSTARTUP_VMS procedure. New and Changed Features 2-1 2.2 CIDR and Variable Length Subnets CIDR is Classless Inter-domain Routing introduced with RFC 1517 as required by the exhaustion and inefficient use of Class B IP addresses. CIDR eliminates address class distinctions and relies instead on address masks that fall on bit instead of byte boundaries. CIDR also aggregates routing information to reduce the exponential growth in routing tables. TCPware's CIDR implementation includes addition of the /MASK qualifier to the ADD ROUTE and REMOVE ROUTE commands in NETCU. The NETCU SHOW ROUTES command also includes a /FULL qualifier that displays the CIDR masking information. TCPware supports complex networks with subnets of variable length subnet masks. 2.3 Configuration o Configuration questions for the Post Office Protocol (POP3) server are now included (see Section 2.19). o Configuration questions for the PWIPDRIVER are now included. o SMTP-OpenVMS configuration now includes the following new prompts: Do you want to use the SMTP Mail Transfer Agent? Do you want to configure the SMTP Mail Transfer Agent? Enter the disk quota option (IGNORE,DEFER,REJECT): Enter the Organization Header equivalence: Enter the System Header equivalence: The disk quota option is based on whether you want to deliver mail to users despite their disk quota limitation. You can IGNORE the limitation, DEFER mail delivery until later, or REJECT the mail immediately based on the limitation. (Also see Section 2.26.) o SNMP Agent configuration now includes an option to configure subagents and the shareable images to use for them. (See Section 2.28 for details.) o The Line Printer Services (LPS) configuration now allows you to set the spool directory specification. A new dialogue and prompt in CNFNET were added. In the case of a directory specification other than the default (TCPWARE_ SPECIFIC:[TCPWARE.LPS_SPOOL]), CNFNET validates it and creates the directory if it does not exist. 2-2 New and Changed Features 2.4 Configuration: Menu-Driven TCPware now provides a menu option to drive the regular configuration. When you execute the CNFNET procedure with the MENU parameter as follows: $ TCPWARE:CNFNET MENU a main Configuration Menu appears. The subsequent menus provide an up front interface to the regular TCPware configuration, startup, and shutdown. (Note that if you enter the CNFNET command without the MENU parameter, or use the FULL or a component code parameter, the Configuration Menu does not appear.) 2.5 Configuring Database Products Changes were made to configuring the Ingres Corporation INGRES/Net and Oracle SQL*Net products to be able to use them with TCPware: o For INGRES/Net for the OpenVMS Operating System Version 6.4 and later, use TCPware's UCX Compatibility mode. For Versions 6.2 and 6.3, use the procedure indicated in the Installation & Configuration Guide, the Customizing Your Configuration chapter. o For Oracle's SQL*Net Version 7.1.5 and later (with Protocol Adapter 2.1.5), simply install the product. You do not need to follow the steps in the Installation & Configuration Guide, the Customizing Your Configuration chapter. 2.6 Domain Name Services (DNS) o TCPware's DNS was upgraded to incorporate the Berkeley Internet Name Domain (BIND) V4.9.3 implementation of NameD, the BIND name server daemon. TCPware 5.1 addresses the February 1996 advisory from the Computer Emergency Response Team (CERT). TCPware V5.1 includes the V4.9.3 BIND server which fixes the security risk outlined in the CERT advisory CA96-02. If you have TCPware V5.0-3 or V5.0-4, you can upgrade your BIND server to V4.9.3 with upgrade software also included with this release. You can read the full text of the CERT advisory at the following Web site: ftp://info.cert.org/pub/cert_ advisories. Although we do not believe that the security risk posed by earlier versions of BIND is very serious, we urge you to review the advisory and upgrade your TCPware BIND server (NameD) as soon as possible. New and Changed Features 2-3 In addition to addressing the CERT advisory, we have learned that the version of NameD obtained from the BIND working group contained several significant bugs. The new V4.9.3 NameD included with this release is expected to resolve the problems associated with version 4.9.2 included in earlier versions of TCPware. o The TCPWARE_NAMED_LOGFILE_SEVERITY logical was added that works exactly like the TCPWARE_NAMED_OPCOM_SEVERITY logical but controls the messages going to the log file. If you set the log file severity to a level that does not go up to LOG_WARNING, you will get a warning before it is set: Messages up to Severity Level 3 will be logged %%TCPWARE_NAMED-W-LOGSVR, Logfile severity setting may suppress important messages Note Messages also appear when starting up the name server. These can be Fatal Errors, Errors, Warnings, or Info messages and are stored in the TCPWARE:NAMESERVER.LOG file. For a review of some of the more critical errors that could appear and what to do about them, see the DNS Name Server Errors section. These messages do not appear in the Domain Names Services chapter of the Management Guide. o The file TEMPLATE_NAMED.CA was replaced with the latest version (Nov 8, 1995) of the domain.root file from InterNIC. (The latest version of NAMED.CA is available from the InterNIC registration services using ANONYMOUS FTP at ftp.rs.internic.net in the file /domain/named.ca.) DNS Name Server Errors The following messages may appear in the TCPWARE:NAMESERVER.LOG file: Critical Errors o The following are critical malloc errors that shut down due to insufficent memory. The message is the message relating to the errno value. These will all shut down with SS$_ INSFMEM, which the NAME_SERVER.COM file will catch and will restart your name server, sending the OPCOM message nameserver process has restarted after an error: 292: 2-4 New and Changed Features TCPWARE_NAMED-F-PANIC, malloc(servent): message - ABORT TCPWARE_NAMED-F-PANIC, malloc(protoent): message - ABORT TCPWARE_NAMED-F-PANIC, malloc(savestr): message - ABORT TCPWARE_NAMED-F-PANIC, malloc(saveinv): message - ABORT TCPWARE_NAMED-F-PANIC, malloc(netinfo): message - ABORT TCPWARE_NAMED-F-PANIC, malloc(netinfo): message - ABORT TCPWARE_NAMED-F-PANIC, malloc(netinfo): message - ABORT TCPWARE_NAMED-F-PANIC, malloc(qdatagram): message - ABORT TCPWARE_NAMED-F-PANIC, malloc(netinfo): message - ABORT TCPWARE_NAMED-F-PANIC, malloc(ddtfile): message - ABORT TCPWARE_NAMED-F-PANIC, malloc(ddtfile): message - ABORT TCPWARE_NAMED-F-PANIC, malloc(fwdinfo): message - ABORT o The following are critical errors that shut down with- out performing any cleanup. These should always result in calls to Process Software Technical Support (sup- port@process.com). TCPWARE_NAMED-F-PANIC, rm_name - ABORT This one will have a TCPWARE_NAMED-E-rm_name Error message before it (see the Errors section): TCPWARE_NAMED-F-PANIC, ns_req: bad action variable - ABORT TCPWARE_NAMED-F-PANIC, stale: impossible condition - ABORT A default section of code was reached. It should never be reached but, just in case, a critical error message is reported. This should never be seen. TCPWARE_NAMED-F-PANIC, make_rr: impossible d_rcode value - ABORT The code tried to reply to a query with a positive answer that was a negatively cached answer. (The record was found in cache, but what was cached was that the record does not exist.) This should never happen and never be seen. Errors The following are errors that can appear in NAME- SERVER.LOG: TCPWARE_NAMED-E-INSFMEM, insufficient dynamic memory Same as the Critical insufficient memory errors described in the Critical Errors section, but have not been modified to be critical ones yet. As before, exits with SS$_INSFMEM. TCPWARE_NAMED-E-Not enough memory to allocate initial zones array TCPWARE_NAMED-E-NOMEM, no memory for more zones New and Changed Features 2-5 If you get either of these two errors, you are seriously low on virtual memory and NameD will never be able to run correctly. TCPWARE_NAMED-E-rm_name(hex(dname)): non-nil data pointer TCPWARE_NAMED-E-rm_name(hex(dname)): non-nil hash pointer Tried to remove a name structure from the cache that still had resource records data or a hash table for children. Should never happen since these are both conditions that are checked before calling the code. TCPWARE_NAMED-E-NOTZTOP, filename: line int: SOA for "domain" not at zone top "origin" There is a Start of Authority (SOA) record in filename at line int. SOA records must be at the top of the files. TCPWARE_NAMED-E-CRESOCK, unable to create a TCP socket, errno = errno TCPWARE_NAMED-E-CRESOCK, unable to create a UDP socket, errno = errno The socket call failed. The errno is the error number that explains why. (This will be changed to be more explicit in the future.) TCPWARE_NAMED-E-listen(vs, 5): error A socket listen failed because of the error indicated. TCPWARE_NAMED-E-SELECT, socket_select error, errno = errno, VMS Status=VMS-errno A socket select call failed. The errnos will help answer why. TCPWARE_NAMED-E-TOOBIG, UDP receive from 'addr,port' failed - datagram too big The UDP datagram was too big; the query was ignored (NameD stays running). TCPWARE_NAMED-E-BADRECV, UDP receive failed, errno = errno A receive failed, and the errno is why. If errno = ENETDOWN, NameD shuts down with a vaxc$errno status. TCPWARE_NAMED-E-get interface flags: message A socket_ioctl call requesting SIOCGIFFLAGS failed (see the Programmer's Guide). The reason is printed as message. If a failure, this interface is ignored. TCPWARE_NAMED-E-CRESOCK, unable to create a socket, errno = errno Could not create the UDP socket; the errno gives a clue as to why. TCPWARE_NAMED-E-FOPEN, filename: error Could not open file filename because of error. TCPWARE_NAMED-E-BADDATA, database error 2-6 New and Changed Features The database file loaded with errors; the log file should have reports of the specific errors. TCPWARE_NAMED-E-LVLIMIT, unrecognized limit in bootfile: "limit" The bootfile limit is not recognized. TCPWARE_NAMED-E-IVOPTION, unrecognized option in bootfile: "option" The bootfile option is not recognized. TCPWARE_NAMED-E-PROCERR, unable to create process to transfer zone domain The LIB$SPAWN command failed. Generally accompanied by other messages. TCPWARE_NAMED-E-fwritemsg: message A socket_send failed for some reason, denoted with message. TCPWARE_NAMED-E-IVTIM, unable to set maintenance timer A system service call to set the timer failed. This will be more informative in the future. TCPWARE_NAMED-E-BADARG, ZXFR argument error A bad argument was passed to the zone transfer process. This should never come up unless someone tries to use the TCPWARE_ ZXFR.EXE file from the command line. TCPWARE_NAMED-E-BIND, unable to bind the socket, errno = errno A bind() call failed because of the errno. TCPWARE_NAMED-E-filename, message Reports that an output error occurred on the file stream (out of disk space). 2.7 Dynamic Host Configuration Protocol (DHCP) DHCP now supports the "network class" for specifying a class of clients. Using the new nc option, you can specify a DHCP entry assigned to a group of clients that belong to other networks. Their DHCP requests are routed through a relay agent on a router. You can provide different configurations to clients on different networks without listing each client with MAC addresses in the DHCP configuration file. New and Changed Features 2-7 2.8 FTP-OpenVMS Client-FTP o The FTP graphical user interface (GUI) (the DECW_FTP procedure) now recognizes UNIX-style filenames. o The FTP GUI now uses a lowercase filename default. You can change the default using a toggle button in the "Settings" dialog box. o On the GUI "File Transfers" screen, the VMS mode selection is now moved out of the radio box in the center of the screen into a separate toggle button. You can enable or disable this button if you want to use the MODE_M_VMS modifier along with the regular file transfer mode when dealing with a VMS FTP server that implements this mode. This toggle button is disabled if the server is not VMS. o In command line FTP, the commands ENABLE VMS_PLUS and DISABLE VMS_PLUS were added to switch VMS_PLUS transfer mode on and off. VMS_PLUS mode is used with TCPware and UCX servers and is automatically negotiated when the connection is set up. Server-FTP The TCPWARE_FTP_ANONYMOUS_ROOT logical no longer sets the default directory for the ANONYMOUS account. To do so, follow the instructions in the FTP-OpenVMS Server Management chapter of the User's Guide. 2.9 GateD GateD now fully supports masks for routes and protocols (including OSPF) that support variable subnet masks can now use the variable subnets supported with CIDR changes. (See Section 2.2 for details on CIDR.) 2.10 Installation o Customer changes to the TCPWARE:SERVICES. file are now added to the new file. The file is also no longer purged during installation. o The following additional files are no longer purged during installation: *_CONTROL.COM and TCPWARE_COMMANDS.COM. Customer modifications made to the .COM files should be incorporated into TCPWARE:TCPWARE_STARTUP.COM. After doing this, these files may be purged. (See the Installation & Configuration Guide Customizing Your Configuration chapter for details.) 2-8 New and Changed Features o Support for an alternate work device (AWD) installation was added. 2.11 Line Printer Services (LPS) You can now start LPS using a batch job, which can greatly reduce the time of TCPware startup when there are many LPS queues defined. You can choose batch startup after ending the LPS queue configuration during TCPware configuration. 2.12 Network Control Utility (NETCU) The following modifications were made to the NETCU commands: o ADD ROUTE includes the /MASK qualifier to support CIDR. (For information on CIDR, see Section 2.2.) o ADD SERVICE and MODIFY SERVICE include the /INACTIVITY_ TIMER and /NOLISTEN qualifiers for the NOLISTEN service. o ANALYZE MAIL was added for SMTP-OpenVMS. o ENABLE REDIRECTS and DISABLE REDIRECTS were added. You can disable transmitting ICMP redirects when a TCPware system acts as a gateway (forwards datagrams) using the command DISABLE REDIRECTS. ENABLE REDIRECTS is the default if IP forwarding is enabled (using ENABLE FORWARDING). The current state of redirection appears in SHOW ROUTES output. o MODIFY KDB /LIFETIME was corrected to /MAX_LIFE. o REMOVE MAIL was added for SMTP-OpenVMS. o REMOVE ROUTE includes the /MASK qualifier to support CIDR. (For information on CIDR, see Section 2.2.) o REMOVE SERVICE includes the /ADDRESS qualifier. o SEND MAIL was added for SMTP-OpenVMS. o SET CONFIGURATION SMTP was added for SMTP-OpenVMS. o SHOW CONFIGURATION SMTP was added for SMTP-OpenVMS. o SHOW MAIL was added for SMTP-OpenVMS. o SHOW ROUTES includes the /FULL qualifier to display CIDR and Path MTU discovery information (see also Section 2.2 and Section 2.18. o The SHOW SERVICES /FULL qualifier now displays output for the /INACTIVITY_TIMER, and /NOLISTEN values. o START/SMTP was added for SMTP-OpenVMS. New and Changed Features 2-9 o START/TCP includes the /PATH_MTU_DISCOVERY and /NOPATH_ MTU_DISCOVERY qualifiers to support Path MTU discovery (see also Section 2.18. o STOP/SMTP was added for SMTP-OpenVMS. o The STOP command was renamed STOP/NETCP. 2.13 Network Time Protocol (NTP) o The following modifications were made to the NTPD server to support master-clock mode and local-master mode. These modes use NTPD as an NTP server in the non-Internet connected network so that the local host can act as a reference server to synchronize the reference clock: - The local time offset is calculated from the local VMS time and TCPware timezone setting. - The reference time field is now filled in. - The dispersion value is set to 0.01 seconds. - NTPD implements server mode to respond to client requests immediately without queuing and storing peer information. With these changes, you can configure NTPD with the local- master option to run with a strata over 10 without a reference clock. You can also use the master-clock option when there is a reference clock synchronizing the VMS host clock and specifying a strata below 10. o NTPD can now interoperate with NTP client commands such as ntp or ntpdate. o Added a second keyword version to the peer command. For example: peer 198.115.142.47 version 1 When the server polls the specified peer, it specifies NTP version 1 in the packet. This is necessary to communicate with a peer that only supports NTP version 1, and when the TCPware NTP server is not listed as a peer on a V1 server. If the V1 server polls the TCPware server first, the version number in the packet is noted and used later in packets sent to the V1 server. In case of version 2 and 3, the NTP server will alternate versions in case the peer does not respond. 2-10 New and Changed Features o Added the server command. When another NTP server is specified with this command, the local server will operate in client mode and the other server in server mode. In this mode, client adjusts time according to the server, but the server will never synchronize to the client. As with the peer command, you can specify a server version. For example: server 192.42.95.1 o Added the master-clock command. Configure NTP as a master server at strata lower than 10. This is used for a host that has special hardware to synchronize its clock, such as a WWVB radio clock. For example: master-clock 1 o NTP now polls peers at an interval of a minimum 64 (a change from 32) seconds, and a maximum 1024 (a change from 2048) seconds, to be compliant with the NTP RFC. o NTP now posts synchronization messages as OPCOM messages as well as in the NTPSERVER.LOG file. 2.14 NFS-OpenVMS Client The NFS Client now performs file handle lookups for specific files when accessed only, or when the file's attributes are requested, by default. The NFSMOUNT command includes the default /NOLOOKUPS qualifier for this purpose. (Using NFSMOUNT /LOOKUPS implements the previous method of looking up file handles for each and every file in a directory for any file accessed.) The /NOLOOKUPS default can improve performance for customers with large directories who require access to a small number of known files in them. Accessing a specific file activates a lookup for that file only. Performing a DCL DIRECTORY command with /NOLOOKUPS still activates lookups for the entire directory contents. Note that an NFSMOUNT /FILEIDS=NONUNIQUE does an implicit /LOOKUPS. This means that combining FILEIDS=NONUNIQUE with an explicit /NOLOOKUPS returns an error message. New and Changed Features 2-11 2.15 NFS-OpenVMS Server The NFS Server now attempts to use XQP+ multithreading support. This support allows multiple XQP requests to be active from a single process. This improves performance when the NFS Server issues XQP requests (such as to look up, create, and access files). XQP+ support was developed by Digital for use by the Pathworks Server. It is available in recent versions of OpenVMS. XQP+ multithreading must be enabled using the SYSGEN XQPCTLD1 parameter. By default, this parameter is 0, which disables the support. For the NFS Server to use this feature, the SYSGEN parameter must be set to 2 or higher (up to 8). (See SYSGEN HELP on the XQPCTLD1 parameter). Note that this parameter is dynamic so that no reboot is needed to change it. If a site is using Pathworks and the NFS Server but does not want the NFS Server to use the XQP multithreading support, the system logical TCPWARE_NFS_XQP_THREADS can be defined to specify the number of threads (this logical can also limit the number of threads used). If the logical equivalence value is 0 or 1, XQP+ multithreading support is not used. If the logical does not exist or specifies a value higher than the XQPCTLD1 parameter, the XQPCTLD1 parameter limit is used. 2.16 NSLOOKUP Help is now available for NSLOOKUP. Enter HELP or ? at the > prompt. 2.17 NTDRIVER The NTDRIVER was enhanced to set the size of the transmit buffer based on SYSGEN's LRPSIZE when running on VMS 5.x systems. This improves performance on these systems. 2.18 Path MTU Discovery Support Path MTU discovery provides a performance improvement when large packets of data are sent over TCP. It causes TCP to segment data (when segmentation is necessary) into the largest possible datagrams that can be transmitted to the remote host without fragmentation along the path. Path MTU discovery is specified in RFC 1191. You can disable Path MTU discovery using the /NOPATH_MTU_DISCOVERY qualifier with the NETCU START/TCP command. 2-12 New and Changed Features 2.19 POP3 Server The Post Office Protocol Version 3 (POP3) Server provides a way for hosts (such as PCs) who do not want to maintain their own message transport systems (MTSs) to retrieve mail from an OpenVMS mail server's incoming mailboxes. The client cannot retrieve mail moved to or located in other mailbox folders. POP3 is a multithreaded server that can handle up to 31 simultaneous client connections. It does not perform any mail delivery functions. Initially the TCPware server host starts the POP3 service by listening on TCP port 110. A client (PC) wishing to use the mail service makes a connection with the server, which sends a greeting. The client and TCPware host exchange commands and responses until the connection is closed or aborted. In the process, the client can retrieve new mail in the server inboxes. The basic TCPware configuration was modified to ask if you want to use the POP3 server. The full configuration was modified to ask the following questions: o What is the maximum number of new mail messages to return per connection? The default is 32. o What is the desired logging level? The options are: - ERROR-Logs errors only (the default) - INFO-Logs errors and informational messages - THREAD-Logs errors, informational messages, and detailed thread logging - DEBUG-Complete debug logging TCPware creates the TCPWARE_SPECIFIC:[TCPWARE]POP3SERVER.LOG file when the server is started. o Do you want to do a MAIL PURGE/RECLAIM operation for each mailbox after its use? If TRUE, this not only purges (deletes all messages in) the wastebasket folder, but releases deleted message space back to RMS for reuse. The default is TRUE. TCPware's POP3 server supports all the "minimal" commands described in RFC 1725 (USER, PASS, QUIT, STAT, LIST, RETR, DELE, NOOP, RSET, and QUIT) as well as the optional TOP command. The APOP and UIDL optional commands are not supported. The POP3 server is documented as part of the SMTP-OpenVMS Management chapter of the Management Guide. New and Changed Features 2-13 2.20 PPP Interface The Point-to-Point Protocol (PPP) interface allows you to send IP datagrams over serial links, including LAT or modem connections. PPP enhances the nonstandard Serial Line IP (SLIP) interface by providing self-contained error detection and automatically negotiated header compression. PPP also provides authentication through the Password Authentication Protocol (PAP) and Challenge Handshake Authentication Protocol (CHAP). You configure PPP on the TCPware host using the pppd command and its options at the DCL level or aggregated in an options file. (See the PPP Interface chapter of the Management Guide for details.) 2.21 RCD Client The RCD Client allows local users to access remote CD-ROM drives as if they were local drives. You can configure an RCD pseudodevice using the RMTSETUP command with the /CD qualifier so that you can perform the usual file access functions on the write-locked CD-ROM device. 2.22 RCP Command o RCP now returns status values to reflect the reason RCP exited or completed. There is also more extensive messaging associated with the new status codes. o RCP now includes the /NOVMS qualifier. /NOVMS cannot be propagated through a third-party copy and RCP does not check for /VMS if UNIX syntax is used. Also, VMS file attributes are not preserved in a third-party copy to a UCX host. To preserve VMS file attributes in this case, instead of using RCP tcpware-host:file ucx-host:file, use RSH to send over the command (RSH tcpware-host RCP /NOVMS file ucx-host:file). 2.23 RLOGIN The following new qualifiers were added to the RLOGIN command: o /EIGHTBIT-for eight-bit data transmission o /ESCAPE_CHARACTER-redefines the escape character o /LOG=file-logs an RLOGIN session o /LOWERCASE and /NOLOWERCASE-enables or disables lowercasing of the local username sent to the remote host 2-14 New and Changed Features 2.24 RSH Command The RSH command now includes the /LOG and /SYSERROR quali- fiers. 2.25 Serial Line IP (SLIP) A check is now made as to whether the SLIP packet is a TCP packet for compression. Non-TCP packets should not be compressed. 2.26 SMTP-OpenVMS o The POP3 Server was introduced as a part of SMTP-OpenVMS. For details on POP3, see Section 2.19. o You can now define RFC 822 headers for outgoing mail using the TCPWARE:CONF_SMTP_HEADERS.COM procedure. This provides a menu and prompt driven interface that replaces the previous logicals definition approach. (See the SMTP: Transferring Mail chapter of the User's Guide for details.) o SMTP now includes all the addresses in the RFC Reply-To: header in the VMS From: header so that reply mail will go to all the addresses in the RFC 822 Reply-to: header. o SMTP mail over ALL-IN-1 now includes an outgoing alias in the FROM: header. To add an ALL-IN-1 alias, perform the following steps (NOTE: These are not included in the SMTP: Transferring Mail chapter of the User's Guide): 1. Find the equivalent to the logical TCPWARE_DOMAINNAME by doing a SHOW LOGICAL TCPWARE_DOMAINNAME. 2. Do an ADD ALIAS/OUTGOING command in NETCU. Define the alias name and supply the following for the equivalence parameter: """ALL-IN-1-user%.allin1""@logical-equivalent" ALL-IN-1-user must be in uppercase, %.allin1 must be in lowercase, and the TCPWARE_DOMAINNAME logical equivalent must be exactly as determined in step 1. For example: $ SHOW LOGICAL TCPWARE_DOMAINNAME (LNM$SYSTEM_TABLE) "TCPWARE_DOMAINNAME" = "nodea.domain.com" New and Changed Features 2-15 NETCU> ADD ALIAS/OUTGOING Joe.User """USER%.allin1""@nodea.domain.com" This creates an outgoing and incoming alias called Joe.User for ALL-IN-1 user USER. The FROM header will contain Joe.User@domain_part and mail can be sent to SMTP%"Joe.User@domain.com" and will be forwarded to ALL- IN-1 for user USER. o SMTP has been ignoring disk quota limitations enforced on user accounts. Now the behavior of mail delivery to user account is controlled by the system executive logical TCPWARE_SMTP_DISKQUOTA. This logical can take the following values: "IGNORE" - Ignore quota and delivery mail (default). "DEFER" - Keep retrying delivery within message life. "REJECT" - Immediately bounce. o The SMTP server now uses the contents of the Apparently-to: header as the To: header content if there is no To: header in the RFC header portion of the mail message. Since there can be multiple Apparently-to: headers, the To: header can be a list of these addresses. 2.27 SNMP Services SNMPD now reads and writes routes using IPDRIVER us- ing variable subnet masks. This means that SNMPD uses ip.ipRoutingTable.ipRouteEntry.ipRouteMask instead of the Class A, B, or C or other subnet mask the driver used to give this variable. You can now read and write routes using a CIDR mask. (See Section 2.2 for details on CIDR.) 2.28 SNMP Agent Extensions Using API TCPware's SNMP Agent now supports subagents serving private MIBs using an Application Programming Interface (API). Under this scheme anyone willing to have their private MIBs served by TCPware's Agent should develop a shareable image that exports the APIs in them in addition to the routines they may need to access the MIB variables. Note to Application Developers Since the shareable image is loaded into the same process address space as that of the SNMPD server, an access violation by the subagent shareable image crashes the server application. Ensure the integrity of your shareable image by testing it thoroughly. Shareable image errors can also corrupt 2-16 New and Changed Features the server's memory space or may result in memory or resource leaks. For more information on the SNMP Agent extensions, see the SNMP Extendible Agent API Routines chapter in the Programmer's Guide. 2.29 Socket Library Note For OpenVMS V5.3 and later, whether the compiler is VAX C, DEC C, or DEC C++, network programmers should use Digital Equipment Corporation's Socket Library routines and header (include) files. In the case of the compiler being DEC C or C++, programmers MUST use Digital's library and header files. This applies to VAX and Alpha system alike. 2.30 TELNET-OpenVMS o TELNET-OpenVMS now uses the STREAM service by default in- stead of TCP for better performance. The /OPTION=KEEPALIVE qualifier was added to the NETCU ADD SERVICE command in the TELNET_CONTROL.COM file so that it is enabled when the TELNET STREAM service is added. o Using the OPEN/CREATE command in a startup file now exits TELNET after completing the command and continues processing the file. 2.31 TFTP Utility o The TFTPD server now releases UDP ports after connecting to the first host requesting the TFTP transfer. This enables the master server to create new TFTPD processes to serve other clients while the first server is processing the first client. o The TFTPD server was enhanced to convert UNIX pathnames into VMS subdirectory filespecs under the TFTP directory. Thus: dir/filename. is converted to: [.dir]filename. /dir/filename. is converted to: [.dir]filename. New and Changed Features 2-17 2.32 UCX Compatibility Services SOCK_RAW support was added for UCX compatibility. You can access this using the DEC C Run-Time Library and BGDRIVER. Consult the UCX documentation for details. 2.33 VMS Communications Interface (VCI) Support VCI support is now available for VAX V5.5 (and later) systems. 2-18 New and Changed Features Chapter__3_______________________________________________________ Changes to 5.0 Made in 5.1 3.1 Alpha System Startup Process limits were increased so that TCPware will start up on ================================================================================ Archive-Date: XXX, 20 May 1996 12:20:39 -0400 Subject: Re: TCPware V5.1 - [2/3] Message-ID: <1996May20.122039.1978@delta.process.com> From: ostrom@process.com (Andy Ostrom) Date: 20 May 96 12:20:39 -0400 References: <1996May20.121609.1976@delta.process.com> MIME-Version: 1.0 Content-Type: message/partial; id="832609372@Andy Ostrom"; number=2; total=3 certain Alpha systems. 3.2 BGDRIVER BGDRIVER is no longer as restrictive about what it wants for certain operations (which could affect DECwindows). 3.3 Configuration o CNFNET no longer fails if it cannot find the HOSTS. file. o The LPS configuration now includes the warning Default printer undefined if you delete the default printer. o TFTP configuration now redisplays the Enter the root working directory prompt after a bogus entry. o The DNS configuration was modified to better explain the use of forwarding-only name servers. Instead of a separate choice for a "slave" server, there is an additional question in the configuration of primary, secondary and caching servers. It asks if you want this server to be a forwarding-only server (defaulting to no if it was not a forwarding-only before, and yes if it was a forwarding- only server). If you answer yes, it asks for the internet address of one or more forwarders. Also, the question about configuring the estimated number of local definitions was removed from the DNS configuration. o CNFNET no longer skips to the NetWare configuration if you do not wish to configure all of TCPware at this time. o Domain Name Services configuration no longer returns errors. o An "undefined symbol" message for the MISC_CONTROL.COM file no longer appears during configuration. Changes to 5.0 Made in 5.1 3-1 o A "no such file" message because of an error in the KERBEROS_CONTROL.COM file during configuration no longer appears. 3.4 Domain Name Services (DNS) o DNS client and server were modified to automatically restart if an unexpected error occurs. One of the following messages may appear in OPCOM: TCPware_DNS, TCPware DNS client process has restarted after an error: %X0000000C TCPware_NAMED, TCPware nameserver process has restarted after an error: 12 If the above message appears, please contact Process Software Technical Support. o Modifications were made to the NameD and DNS startup procedures to optimize the startup parameters: DNS: WORKING_SET - changed from 256 to 1024 MAXIMUM_WORKING_SET - changed from default 2048 to WSMAX sysgen parameter PAGE_FILE - changed from 65536 to VIRTUALPAGECNT sysgen parameter NAMED: AST_LIMIT - changed from 15 to 256 IO_BUFFERED - changed from 30 to 128 IO_DIRECT - changed from 30 to 128 QUEUE_LIMIT - changed from 50 to 256 MAXIMUM_WORKING_SET - changed from 65536 to WSMAX sysgen parameter PAGE_FILE - changed from 65536 to VIRTUALPAGECNT sysgen parameter. The question about configuring the estimated number of local definitions was also removed from the DNS configuration. o NAMED was modified to change the way it binds to UDP ports, for a performance enhancement. Previously it was binding to all the available interfaces (as seen below from NETCU SHOW CONNECTION output) to multiply the number of UDP packets to be buffered. UDP1639 0 0 192.42.95.1.domain *.* UDP1640 0 0 127.0.0.1.domain *.* UDP1641 0 0 *.domain *.* 3-2 Changes to 5.0 Made in 5.1 It now binds multiple times to the same wildcard interface to increase the buffer size without adding the overhead of binding to multiple interfaces. When you use NETCU SHOW CONNECTION, you now see the binding as follows: UDP222 0 0 *.domain *.* UDP223 0 0 *.domain *.* UDP224 0 0 *.domain *.* o A change to the NAME_SERVER.COM file was made so that if the exit status of NAMED.EXE indicated insufficient memory, NAMED automatically restarts. In some situations, NAMED may run out of memory if it is caching a lot of information. o CNFNET DNS or CNFNET FULL now properly writes records to the TCPWARE_CONFIGURE.COM file. o NAMED no longer hangs if a zone transfer is requested and the client does not close the TCP connection after the transfer. 3.5 Dynamic Host Configuration Protocol (DHCP) o In the BOOTP/DHCP configuration, if the static route was defined in the BOOTP/DHCP configuration using the st tag and the entry containing that tag was referenced from another entry with the tc tag, the contents of the st tag was not propagated to the referencing entry. This was fixed. o If the DHCP or BOOTP request contained a non-DHCP option such as a hostname option (option 12), the DHCP/BOOTP server failed with an option format error and did not respond to BOOTP/DHCP requests. This could result in BOOTP failures when upgrading from a previous version. This was fixed. o Being able to specify an infinite lease time using lt=0 now works properly. o The MTU value was sent out as four-byte data. It is now being correctly sent out as two-byte data. o When specifying bs=auto (boot file size calculated), TCPware was sending out the boot file size as 1 when there was no boot file specified. The boot file size is no longer sent out unless the boot file is specified. o An erroneous "invalid lease for address" error no longer occurs. o The DHCP process was changed from DHCPD to TCPWARE_DHCPD. Changes to 5.0 Made in 5.1 3-3 3.6 FTP-OpenVMS Client o An AlphaStation 4000 4/233 no longer has a problem using the FTP GUI. o The FTP GUI installation was corrected not to link DECW_ FTP.EXE at sites with the earlier XUI version of DECwindows instead of the Motif version. o The VERBOSE command now toggles correctly. o The COPY command without a /LOCAL or /REMOTE qualifier now properly defaults to /REMOTE if a node name is part of the specification. o The FTP GUI no longer ACCVIOs when you double-click on the empty brackets ([ ]) displayed after changing to a nonexistent directory. o The FTP GUI no longer ACCVIOs with a VMS server that reported filespecs without a version number. o A popup message is displayed when an error occurs during an FTP operation. Some messages direct you to look in the detailed message logged in the message window. o Exiting FTP with a Control-Z no longer returns an "end of file detected" message. o The allowable length of the command after SITE SPAWN was increased to 252 characters. o The Client now properly signals that a virtual circuit was broken. o The MGET and MDELETE commands now work properly. o The DEBUG command now toggles correctly. It previously toggled the REPLIES instead of COMMANDS class. o Changing default to a subdirectory no longer fails with a 501 %RMS-E-PRV, insufficient privilege or file protection violation error when: - the user directory access is restricted by the TCPWARE_ FTP_ANONYMOUS_ROOT or TCPWARE_FTP_user_ROOT logicals. - the root directory is on a different device from the user's (or anonymous account's) login device. o You can now switch from a VMS server to a server that does not implement the SYST command. The remote host type detection mechanism was enhanced to prevent the remote host type detection from failing and still remaining as VMS type, causing an ACCVIO. 3-4 Changes to 5.0 Made in 5.1 o FTP was corrected not to output hash characters when outputting to the terminal screen instead of a file. 3.7 FTP-OpenVMS Server o The Server interprets UNIX-style syntax with the client CD command as proper OpenVMS directory syntax. (See the Client section above.) o Server-FTP was enhanced to handle the RMD (Remove Direc- tory) command. o The status was changed for a DIR operation on an EMPTY directory (with no filename specified or with a filename consisting of just the wildcard characters *, ., or ;). In verbose mode, the Server now reports 226: Transfer complete instead of the previous File not found message. o The Server was enhanced to allow the DIR command for a captive account in OpenVMS V6.0. 3.8 GateD GateD's kernel routing table routines now assign GateD log priority levels based on the severity of the error the system returns. Errors were previously logged with priority LOG_ CRIT. Under the new scheme, WARNINGS are logged as LOG_ WARNING, errors as LOG_ERR, informationals as LOG_INFO, and the remainder as LOG_CRIT. 3.9 Intrusion Detection and Evasion TCPware 5.1 changes intrusion (break-in) detection and evasion for PCNFSD and REXECD as follows: 1. The format of the intrusion records has changed to be more consistent with the standard format, (node::user). It is now: IP-address::PCNFSD (for PCNFSD) IP-address::REXECD (for REXECD) 2. For OpenVMS V7.0 and later, the new SYS$SCAN_INTRUSION system service is used. This system service manages the intrusion database and creates appropriate security audit records. No security audit records are created for earlier VMS or OpenVMS versions. Changes to 5.0 Made in 5.1 3-5 3.10 IPDRIVER Services o Net-directed broadcasts are now forwarded on a multihomed host. o If forwarding is enabled and IPDRIVER receives a datagram destined for another host but does not have a route to that host, IPDRIVER now generates an ICMP destination unreachable message with a code of "network unreachable" instead of "host unreachable." This is in compliance with RFC 1812. o A system crash could occur if ICMP Destination/Port unreachable packets were received that did not contain the IP header of the original transmitted packet. This was fixed. 3.11 Line Printer Services (LPS) o The LPR symbiont now correctly handles file conversion to STREAM-LF. o Previously, an problem occurred with the VMSLPR symbiont. Now it behaves consistently in cases where setup modules are used and where a special escape sequence suppressed the VMS symbiont to insert . o LPS startup no longer fails with a DCL error if there were many LPS queues configured (the number depended on the queue name length, but it was somewhere over 100). o When configuring LPS queues through CNFNET, if a quote was included in the "Additional Qualifiers," subsequent queue startup failures occurred with "undefined symbol" errors. This problem is fixed. o An access violation could occur on an Alpha system upon cleaning up after a print job was queued. This was fixed. o Starting a local queue for a VMS LPR printer no longer fails with a "no logical name match" error. o With the LPR, LPRM, and LPQ commands, if an unknown host were specified with the -P option, the commands did not report an error and used the default printer. The error is now reported properly. 3-6 Changes to 5.0 Made in 5.1 3.12 Network Control Utility (NETCU) o NETCU now treats a command line beginning with a !, #, or ; character as a comment. This was done so that command files used as input to NETCU, such as SERVICES.COM, can have comment lines in them. o ADD ACCESS_LIST now does not overwrite a user-defined "access denied" message with a blank message if the /MESSAGE qualifier is omitted when adding a new entry to a list. The previous message is kept and only overwritten if a subsequent /MESSAGE qualifier is used. o SHOW ACCESS_LIST can now handle access lists with more than 72 entries. This previously caused the command to hang. o SHOW CONNECTION/HOST now displays proper hostnames. o SHOW CONNECTION/NOALL/CONTINUOUS no longer exits with an "exceeded byte count quota" error. o A warning is now given if doing a NETCU REMOVE ACCESS_LIST for a nonexistent entry. o NETCU SHOW ACCESS_LISTS no longer continuously repeats the listing entries when a list using access list number 65535 was added. 3.13 Network Time Protocol (NTP) o The NTPD process no longer exits with an SS$_INSFMEM status after a couple of days. o When NTPD is used in server mode, it no longer causes a memory leak. o The NTP server now no longer limits itself to setting time only within +/-20 minutes. o An error in the time offset calculation that could result in a time synchronization in another timezone being off by 7 minutes 9.5 seconds was fixed. o NTP showing a time seven minutes late in certain timezones was fixed. o NTP no longer starts at stratum 33 and loses sync peers. o When NTP was configured as a local-master, "leap" flags in the response packet are now properly set to "0" (synchronized). o NTP now polls at a minimum interval of 64 seconds instead of 32. Changes to 5.0 Made in 5.1 3-7 o The NTPSERVER.LOG file is no longer locked on Alpha systems, when a shutdown was necessary. 3.14 NFS-OpenVMS Client o The Client now properly finds the host-specific PROXY entry during a mount operation. o The RELOAD PROXY command for a specific username now works properly. o The Client no longer tries to delete ADF files when using a TCPware Server. o Rename operations now work correctly when using a TCPware Server. o The maximum record size on fixed-length files is now set correctly. 3.15 NFS-OpenVMS Server o The Server now works properly on a relative volume set disk. o The record size is now set properly when an export entry is set to create fixed-length files. 3.16 PATHWORKS Support A change was made to PWIPDRIVER to fix a PATHWORKS performance problem. Whenever possible, multiple transmit requests are now consolidated in a single TCP segment to prevent 200 ms delays in the transmit stream that are otherwise generated. 3.17 PING Utility PING now returns the proper number of seconds for a connec- tion. 3.18 R Commands The R Commands properly generate an audit record for a failed command if set up to do so. 3-8 Changes to 5.0 Made in 5.1 3.19 RCP Command o The RCP command is now parsed properly. o An "ambiguous target" error was fixed. o The number of blocks copied from a remote system no longer shows as zero (0) during a /LOG display. o An RCP /LOG no longer indicates that files were copied when they were indeed not. o The RCP server was not copying a file properly if the server only had the FTP license, and not the Security-Plus license. This was fixed. o RCP now works on an Alpha system without having to specify the /USERNAME qualifier. 3.20 RSH Command o Recent versions of TCPware (V4.1 and later most likely, including V5.0-3) may have had a problem on larger systems where there were many incoming RSH/REXEC sessions that stay around (such as with eXcursion). When someone tried to RSH/REXEC into the system, they could get an exceeded byte count quota error. Or, attempts to start an eXcursion session could fail (since eXcursion does not return an error in this case). This is typically seen after about 80+ RSH/REXEC sessions are active (the exact number depends on certain factors). This problem was fixed by increasing the buffer limit in STARTNET.COM to 4194304 bytes. This value should allow about 500+ sessions. You can set this value to whatever you like. Edit the TCPWARE:STARTNET.COM file, locate the /BUFFER_LIMIT = 4194304 - line, and modify the 4194304 value to a higher one. Figure about 6000 bytes per RSH/REXEC session. You also need to allow about 32768 bytes per network interface and around 512 bytes per service definition. (These are rough numbers!) o Control now returns properly to the DCL level after an RSH command is executed. o The /PASSWORD qualifier can now be used without requiring the /USER qualifier. Changes to 5.0 Made in 5.1 3-9 3.21 Security-Plus: Kerberos Server Management o Kerberos no longer returns an "unknown internal routine name" error at startup. o The NETCU ADD KDB command instance parameter now preserves case if the value is enclosed in quotes. o The NETCU MODIFY KDB command /PASSWORD qualifier now specifies the user's new Kerberos password, if a password change is desired. (It was previously documented to take the value of the Kerberos master password.) The Kerberos administrator can enter the user's current password as a command parameter and change this password using the /PASSWORD qualifier. 3.22 Security-Plus: Outgoing Access Restrictions o NETCU SET OUTGOING no longer allows creation of an invalid UIC/GID combination for the UserID. o Previously, the destination address in the restrictions file was not "cleaned up" based on the destination mask. If you did not specify a clean value, the restrictions may have been incorrect from what you intended. If you entered 192.42.95.56 255.255.255.0, the code should have treated this as if you entered 192.42.95.0 255.255.255.0. This was fixed. 3.23 Security-Plus: Packet Filtering See Section 3.22. The same bug fix applies. 3.24 SMTP-OpenVMS o SMTP now forwards mail correctly if the original sender has an alias name in the source path and From: header that contains a comma and spaces; for example, "User, Name"@domain.com. o SMTP now fully translates an incoming alias to its equivalent if the incoming alias is defined multiple levels and at any lower level an alias contains a lowercase character. This was causing mail not to be delivered to the correct recipient. o SMTP now fully translates an incoming alias name to its equivalent if the address contains an IP address as its domain part, such as alias@[192.42.95.26]. 3-10 Changes to 5.0 Made in 5.1 o If you send mail with the quoted DECnet-style mail address in the local part to Server-SMTP, it no longer rejects the mail with a syntax error in the local part. o Some address resolution bugs were fixed as far as use of single quotes, and source routing and DECnet node syntax. o SMTP no longer experiences a Bad Block Address error when closing a local message file. This error occurred when the second recipient in the To: header exceeded 45 characters and memory allocated to determine whether the To: address was a mailing list was not being deallocated. o The Server no longer ACCVIOs because of a message contain- ing an empty To: header. o SMTP_MAILSHR no longer ACCVIOs when adding the user-defined headers to the mail message. o If a blank TCPWARE_SMTP_INCOMING_ALIAS_FILE.DAT file exists, then all incoming names are no longer converted to uppercase. o Bounced mail is now properly returned to the sender. Previously the sender's name was truncated so that returned mail failed. o Nondelivery notification bugs were fixed. o SMTP-OpenVMS can now handle multiple addresses in the Reply-to: header. Also, if a user has forwarding set, the source path is kept intact and is not replaced with the Reply-to: header body. o The Server can now handle multiple-line From: addresses properly, as well as continuation header lines that are preceded by a space or a tab. o Errors in writing to a client mailbox are now written to an SMTP_S* file so that the file can be processed when the check/retry time kicks in. o Sender Unknown no longer appears in the VMS From: mail header even if the sender is valid. 3.25 SNMP Services The SNMPSERVER.LOG file is no longer locked on Alpha systems, where a shutdown was necessary. Changes to 5.0 Made in 5.1 3-11 3.26 TELNET-OpenVMS o TN3270 mode had a problem with a certain kind of TELNET server on IBM hosts that prompts the user in NVT mode first, then goes into the TN3270 session, and comes back into NVT mode when the TN3270 session was completed. TN3270 recognized the change of mode from NVT to TN3270, but did not recognize the other way, ending up trying to recognize the NVT data stream as a TN3270 data stream and resulting in a corrupted state. This was fixed. o The obsolete CHARSET.DAT file was removed. 3.27 Terminal Server Print Services o Previously, when binary data was sent out to a terminal server that did not support RAW mode, the terminal server removed the byte after the character, resulting in an erroneous print result. The extra character is now properly inserted after the character if the character that follows is not . o If a print job was deleted before a TCP/IP connection could be established with the remote terminal server and a previously stopped queue was started, then print jobs submitted to the first queue were directed to the IP address assigned to the second queue. This was fixed. o The TCPWARE_TSSYM now operates properly in RAW mode. 3.28 UCX Compatibility Services and BGDRIVER o Previously, if an active connection existed for a partic- ular local-address and port number, you could not bind to that same combination even if you specified SO_REUSEADDR. One result was that VAX NOTES V2.5 (and later) would not work. This was fixed. o NETCP was fixed to correct a problem with services using the BG_TCP and BG_UDP protocol. Previously, these services were not accessible if the username specified with the service had an odd character length. 3.29 VMS Communications Interface (VCI) Support NETCU no longer occasionally hangs on a NETCU START/IP when starting a VCI LAN interface. 3-12 Changes to 5.0 Made in 5.1 3.30 WHOIS Client The default server the WHOIS client references was changed from the now defunct whois.internic.net to ds.internic.net. Changes to 5.0 Made in 5.1 3-13 Chapter__4_______________________________________________________ Changes to NetWare Services in 5.1 4.1 Major New Changes o Addition of the 802.2 and 802.2/SNAP frame types o Addition of RPR to FSS-OpenVMS to better support network printing in NetWare 3 and 4 environments o Addition of the Service Advertising Protocol (SAP) Server for RPR and FSS-OpenVMS o Addition of the new FSS-OpenVMS client utilities (FSSCON and FSSUTL) to support networking administration in a pure NetWare V4 environment o Addition of the new NPS-OpenVMS client utility (NPSUTL) 4.2 Important Information 802.2 and 802.2/SNAP Frame Types You can configure the 802.2 and 802.2/SNAP (SubNetwork Access Protocol) frame types, along with the 802.3 and Ethernet II types, for the NetWare Services. You can specify the frame types as in Table 4-1. Warning The NetWare 802.3 frame type is incompatible with and conflicts with the DECnet/OSI 802.3 frame type. Therefore, do not use the 802.3 frame when using NetWare together with DECnet/OSI. Table_4-1:__Supported_NetWare_Frame_Types_____________________ For_Frame_Type..._____Enter_During_Configuration...___________ IEEE 802.3 with ETHERNET_802.2 or 802.2 802.2 IEEE 802.3 with ETHERNET_SNAP or SNAP 802.2 SNAP ETHERNET II ETHERNET_II or ETHER IEEE_802.3_"raw"______ETHERNET_802.3_or_802.3_________________ Changes to NetWare Services in 5.1 4-1 SET SERVER MEMORY Command Some customers experienced FSS crashing and found the following error messages in their FSS.LOG file: %ITNS-F-NOMEMORY, out of dynamic memory %LIB-F-PAGLIMEXC, page limit exceeded for zone The problem usually occurred on a site with large numbers of connections to the FSS server. There is an undocumented command you can use to solve this problem, whose syntax is: SET SERVER MEMORY /ZONE=2 /PAGES=nnnn The nnnn parameter is the decimal number of the pages. The default shipped setting is 1250. Use the /ZONE qualifier to increase the zone size to solve the crashing problem. You can only specify this command in the FSS.CMD file. You have to restart FSS-OpenVMS for the change to take effect. Configuring RPR TCPware includes an enhanced remote printer (RPR), which appears on the network as RPRINTER (for NetWare V3) or NPRINTER (for NetWare V4). RPR is an OpenVMS process that receives jobs from NetWare PSERVERs and sends them to OpenVMS print queues. Although RPR is part of FSS-OpenVMS, it runs independently: you can use RPR and NetWare 2 print queue emulation with FSS at the same time. You can share up to 250 OpenVMS printers with your Novell network through RPR and the NetWare PSERVERs. TCPware improved RPR performance and efficiency due to a newly added Server Advertising Protocol (SAP) server, and RPR now works with NetWare 4. (See the "Enhancements" subsection below.) You can migrate your FSS-OpenVMS printing configuration slowly. Start by configuring 10 to 20 queues in RPR, then test the configuration. Once you have RPRinter configured properly, add more queues. Keep adding queues until you add your entire FSS-OpenVMS printing configuration to RPR. When RPR is configured and running, you can disable NetWare V2.x printing in FSS-OpenVMS. If you are configuring print queues and print servers on a NetWare 4 server, you must use either NWADMIN or the NetWare 4 version of PCONSOLE. Use the NetWare 3 version of PCONSOLE when configuring queues and the print server on a NetWare 3 or NetWare 2 server. To configure a NetWare 4 file server, you must have an NDS workstation. To run NWADMIN, the workstation must be running Windows. If you need additional information, 4-2 Changes to NetWare Services in 5.1 contact Process Software Corporation's Technical Support group. o Creating more than 16 connections-If you are having trouble maintaining multiple connections with RPR, you may have to modify your communication parameters on the NetWare file server, the OpenVMS host, or the dedicated print server. Contact Process Software Technical Support for addition information if you have trouble establishing a large number of RPR connections. o Configuring the NetWare file server-Communication between the NetWare file server and OpenVMS host is controlled by various configuration parameters. Setting the following SPX values on the NetWare file server may improve perfor- mance and reliability when configuring more than 16 RPR connections: SPX watchdog abort timeout 1080 (default 540) SPX watchdog verify timeout 108 (default 54) SPX ack wait timeout 216 (default 108) SPX default retry count 20 (default 10) Set these parameters using the SPXCONFG utility from the NetWare file server console. See your NetWare documentation for additional information. RPR runs best with a minimum of 16 Mb of extended memory on the file server where you are running the PSERVER.NLM file. LE>Configuring a dedicated print server-If you are using a dedicated NetWare print server, you should increase the number of SPX connections for the print server. The number of SPX connections is defined in the Protocol section of the NET.CFG file on the workstation: Protocol IPXODI SPX CONNECTIONS=60 (default 15) 4.3 Enhancements File Ownership Switch Added The FILE OWNERSHIP command was added to define OpenVMS file ownership when new files are created. The syntax for the new command is as follows: FILE OWNERSHIP=DIRECTORY FILE OWNERSHIP=USER DIRECTORY is the default setting, and it works the way previous versions of FSS worked. File ownership is defined by the owner of the directory in which the file is created. Changes to NetWare Services in 5.1 4-3 If you specify USER, the OpenVMS account associated with the FSS user owns the OpenVMS file. The hybrid user's OpenVMS account owns a file a hybrid user creates, and the FSS guest account (IGUEST by default) owns a file a NetWare-only user creates. You can specify this command in the OPTIONS.DAT file or from the FSS_CONSOLE. FSSCON and FSSUTL Utilities You can configure NetWare users for NetWare 4 systems using a special FSSCON windows-based utility or an FSSUTL DOS command line utility available for FSS-OpenVMS client systems. Contact Process Software about the availability of these utilities. (Further information on the FSSCON and FSSUTL utilities is included in a README.TXT file on the FSS Utilities diskette.) Passwords entered for the FSSCON utility are converted to uppercase. Passwords entered for the FSSUTL utility are not case-converted. Note When displaying server information using FSSCON, the error Application Error, call to undefined Dynalink means that you have an outdated version of the NWCALLS.DLL file. Obtain the latest Windows NetWare Client kit, which includes the latest Windows data link library files. ENABLE/DISABLE FSS95 Commands TCPware provides two new commands in FSS_CONSOLE to support Windows 95 functionality on the FSS server, ENABLE FSS95 and DISABLE FSS95. The default is to disable Windows 95 functionality. If you want to enable Windows 95, you need to disable FSS_PRINTER through SET SERVER DISABLE 2X_PRINTING in the FSS.CMD initialization file. ENABLE/DISABLE VMSBROADCAST Commands TCPware provides two new commands in FSS_CONSOLE to enable or disable VMS broadcast messages to go to your workstation through the FSS server, ENABLE VMSBROADCAST and DISABLE VMSBROADCAST. The default is ENABLE VMSBROADCAST. SET READ PAD and SET WRITE PAD Commands TCPware provides two new commands in FSS_CONSOLE to support record padding, SET READ PAD and SET WRITE PAD. Record padding alleviates occasional file length problems in transferring files between OpenVMS and PC systems. 4-4 Changes to NetWare Services in 5.1 OpenVMS reads and writes in words (one word equals two bytes). If a record contains an odd number of bytes, OpenVMS pads the record to create a word. This switch allows you to specify the character to use to pad records during OpenVMS reads from variable length files. NPSUTL Utility NPSUTL.EXE is an NPS-OpenVMS client configuration utility using the DOS command line interface. NPSUTL provides a simple way for customers to create queue objects on or remove queue objects from the NetWare server's bindery in a NetWare 4.x coexistence environment. See the README1.NPS file on your floppy disk for details on NPSUTL.EXE. Improved WAN Support WAN support was improved. This release includes modifications to the implementation of watchdogs to improve compatibility with NetWare 3 and NetWare 4 networks. Audit Trail for User Login Failures FSS-OpenVMS now creates an OpenVMS Audit Event for user login failure. SAP Server Added This release includes a Server Advertising Protocol (SAP) server. The SAP server maintains a database of NetWare services available to FSS and RPR. In this release, RPR relies entirely on the SAP server, while FSS checks the SAP server when it is started. If the SAP server is running, FSS uses it. If the SAP server is not running, FSS handles SAPs itself. When you install and start FSS, the SAP server and RPR is installed and started. The process name of the SAP Server is TCPware_SAP. Diagnostic Memory Probe You can use a new command in FSS.CMD to set the diagnostic memory probe. The usage of the command is: SET SERVER DIAGNOSTIC MEMORY PROBE Support for FLAG Command The NetWare FLAG command is fully supported for NetWare 2 and 3 systems. Changes to NetWare Services in 5.1 4-5 IPT.LOG File NetWare Services writes the status of startup commands and any error or other status messages the IPT_PROCESS generates to the file TCPWARE_SPECIFIC:[TCPWARE]IPT.LOG. PEER Option The documented PEER option defaults to YES. You cannot change it in the current release. The documented PORT option defaults to 213. You cannot change it in the current release (which complies with RFC 1234, Tunneling IPX Traffic through IP Networks). 4.4 FSS-OpenVMS Issues Using RPR with FSS Printing NPS-OpenVMS now includes NPSUTL.EXE, an NPS client configu- ration utility using the DOS command line interface. NPSUTL provides a simple way for customers to create queue objects on or remove queue objects from the NetWare server's bindery in a NetWare 4.x coexistence environment. For details, see the README1.NPS file on your floppy disk. When installing NetWare Services, both RPR and NetWare 2 print queue emulation are loaded. Once RPR is configured and running, you can disable NetWare 2 print queue emulation in FSS by entering the following command in the FSS.CMD file and restarting FSS: SET SERVER DISABLE 2X_PRINTING Using FSS NetWare 2 Print Queue Emulation from Hybrid User Accounts In OpenVMS version 6.0 and later, certain security enhance- ments were made to allow OpenVMS to meet C2/B1 security re- quirements. These enhancements affected the way the FSS server handled file ownership. FSS assigns ownership of files based on either the ownership of the parent directory, or the OpenVMS account creating the file. By default, ownership is assigned by directory. This causes problems with printing from hybrid user accounts because the directories where the FSS server creates the temporary files for printing are owned by the FSS guest account (IGUEST). 4-6 Changes to NetWare Services in 5.1 When using OpenVMS version 6.0 and later, the OpenVMS user account for a FSS hybrid user must have read access to these files. To print from hybrid user accounts, you must changes the file ownership assignment to the account creating the file. You can change the file ownership setting using the FILE OWNERSHIP command. To set the ownership to account creating the file, enter the following command in your FSS_OPTIONS.DAT file: FILE OWNERSHIP=USER You must also enter this command from the FSS_CONSOLE or restart FSS for the change to take effect. Note that this change applies to all files created by all user on the FSS volume. Release Number for Support Calls You will see a release number in FSS.LOG when you start or exit from FSS-OpenVMS. You need this number when you call Process Software Technical Support for the product support. 4.5 NPS-OpenVMS Issues User Account Quotas-To use NPSCP, OpenVMS users must have a BYTLM setting of 10000. You set the BYTLM parameter for each account using the AUTHORIZE utility. To run AUTHORIZE, set your process default device and directory to SYS$SYSTEM, and run AUTHORIZE as follows: $SET DEF SYS$SYSTEM $RUN AUTHORIZE Then modify the BYTLM parameter by entering the following command: UAF>modify /BYTLM=10000 username Replace USERNAME with the name of the account you want to modify, You must modify each account that needs access to NPSCP. 4.6 Fixes in 5.1 o The FSS process now goes away after a full SHUTNET. o An "image records ignored" error on startup was fixed. o Part of an older message no longer appears at the end of the current message in FSS.LOG. o The Guest account no longer needs a password. Changes to NetWare Services in 5.1 4-7 o Parsing the Access Control List (ACL) no longer causes an ACCVIO. o A process no longer loses buffered I/O quota when using NPSCP. This was fixed in QXDRIVER. o In the previous release of FSS-OpenVMS, writes to disk were slow. This version of FSS-OpenVMS has optimized writes, resulting in better performance. o FSS-OpenVMS now properly gets the trustee directory list so that all client utilities can use the function. o FSSCON and FSSUTL now allows viewing Trustee Directory Assignments done using FSSCON and FSSUTL on volumes other than the /SYS: volume. o FSSCON now includes the User Group function. You can add, delete, or configure the User Group in the bindery database. o FSSCON now allows a virtually unlimited number of server names in the "Known Server" box. o The system no longer crashes in FSS with a SSRVEXCEPT, Unexpected system service exception message. o The buffered I/O byte count quota no longer gets consumed on entering the NPSCP utility without being released on exiting. 4.7 Other Issues Conflicts with the symbols FSS_CONSOLE, TESCP, NPSCP, and QXCP (that run the corresponding utilities) can occur on systems having a mixture of TCPware's NetWare Services products and Interconnection's LFN products in combination with TCPware's TCP/IP Services products. Because of these potential conflicts, the symbol definitions in the TCPWARE_ COMMON:[TCPWARE]TCPWARE_COMMANDS.COM file are now commented out. WORKAROUND: To define the FSS_CONSOLE, TESCP, NPSCP, or QXCP symbol for your system, "uncomment" the appropriate line(s) in the TCPWARE_COMMANDS.COM file. 4-8 Changes to NetWare Services in 5.1 Chapter__5_______________________________________________________ Documentation Notes This chapter discusses the enhancements made to the TCPware for OpenVMS hardcopy and on-line documentation (including DCL HELP), as well as errata found after the publication or production dates (look for the entry "ERRATA"). 5.1 General Documentation Enhancements o The Introduction, User's Guide, & Master Index is now simply titled the User's Guide and was enhanced as follows: - Overview of TCP/IP Networking: A section describing the Classless Inter-Domain Routing (CIDR) protocol was added. (See Section 2.2.) - FTP: Transferring Files: The ENABLE VMS_PLUS and DISABLE VMS_PLUS commands were added, as was the DISPLAY command. (See Section 2.8.) Clarification about wildcarded (* and &) directory deletions (using DELETE/DIRECTORY or RMDIR) was added. Wildcards work only with VMS-to-VMS directory deletions. Also note that when you do a /CONFIRM, the directory names are not expanded at the confirmation prompt. The description for DELETE/LOG was rewritten to say that, if using wildcards, the qualifier displays file specifications "for each deletion request executed" instead of each file deleted. Added clarification to the /CONFIRM qualifier for all commands that accept it that /CONFIRM is positional and applies to all files if positioned immediately after the verb or only to the specific file if positioned after the filename. - Network Printing: Clarification about using quotes around options that may have lowercase and uppercase versions was added. A statement was also added with the LPR -m option that, if used, the LPD server sets the /NOTIFY qualifier in the PRINT command, so that if you are logged in as a user Documentation Notes 5-1 under which the job was printed, OpenVMS notifies you that the job completed. - RCP: Copying Files: The /NOVMS qualifier was added to cover possible command execution errors. However, third- party copies to a UCX system do not preserve the VMS file attributes. Information on avoiding using the /USERNAME and /PASSWORD qualifiers and multiple passwords (for third-party copies) when using DECnet syntax was added. Clarification on the use of multiple quotes to preserve case in sending third-party commands was added. - RSH: Issuing Commands on the Remote Host: Clarification on the use of multiple quotes to preserve case in sending third-party commands was added. An explanation was also added that the /LOG qualifier does not apply to "third-party" transactions. - SMTP: Transferring Mail: Included instructions on use of the CONFIG_FMTP_HEADERS.COM procedure for user-defined RFC 822 headers. - TFTP: Initiating Trivial File Transfers: An explanation was added about an adjustment to the specified TFTP retransmission period (Rexmt-interval) as it appears in STATUS output. The adjustment to Rexmt-interval occurs when the necessary integer value of Tries is used when the formula "Tries = Rexmt-interval / Max-timeout" yields a non-integer result. o The Installation & Configuration Guide was enhanced as follows: - Customizing Your Configuration includes changes to the Oracle SQL*Net Version 7.1.5 (and later) installation and adds details on TCPware's support for Digital's TEAMLINKS and AIDA software. o The Management Guide was enhanced as follows: - Routing: Includes statement warning about mixing routerdiscovery client and routerdiscovery server statements in the GATED.CONF file. - PPP Interface: This is a new chapter. (See Section 2.20 for details.) 5-2 Documentation Notes - NFS-OpenVMS Client Management: The description of ADF files and the /ADF qualifier to the NFSMOUNT command was enhanced to say that "Attributes data files (ADFs) are special "companion" files the Client maintains on a non- VMS server to preserve attribute information the server would not normally recognize." ERRATA: The NFSMOUNT /LOOKUPS command has an incorrect description. See Section 2.14 for a correct description. - NFS-OpenVMS Server Management: The default value for the NFS_DIRREAD_LIMIT advanced parameter was changed from 51200 to -1, which is to turn off file size estimation. - DHCP/BOOTP Server: Added the "network class" (nc) DHCP configuration file tag. (See Section 2.7 for details.) - Domain Name Services: The description for forwarding servers (formally "slave" servers) and forwarders was enhanced. Also, the trailing dots at the end of zone names in the NAMED.BOOT file were removed. ERRATA: The chapter failed to include the NAMESERVER.LOG file error messages described in the DNS Name Server Errors section of Section 2.6. See this section for details. - NSLOOKUP Utility: The NSLOOKUP command description now indicates that commands should be entered in lowercase only. - Network Time Protocol: The NTP chapter now includes a "Troubleshooting" section. - SNMP Services Management: A section on supporting ex- tendible MIBs was added to the chapter. (See Section 2.28 for details.) - Kerberos Server Management: The Kerberos Configuration Checklist was improved to more fully reflect the Kerberos configuration process. ERRATA: Page 38-10 should not include the line ADD KACL ADD * ADMIN *. Using wildcards in an ADD KACL command causes a mapping error. - Security-Plus: Incoming Access Restrictions: Added a section, "Using Subnet Masks for Selective Access," that goes over the order items appear in the file, including such occasions when a particular mask may change the normal DENY/PERMIT order. Documentation Notes 5-3 - Security-Plus: Kerberos Server: The description of the CREATE SRVTAB command in NETCU was modified to indicate that the service table must be created after the services have been added for that host. - NETCU Reference: Modifications include addition of the SMTP management commands (ANALYZE MAIL, REMOVE MAIL, SEND MAIL, SET CONFIGURATION SMTP, SHOW CONFIGURATION SMTP, SHOW MAIL, START/SMTP, and STOP/SMTP), the STOP/DNS command, and corrections to existing commands. ERRATA: Page 43-87 should include more extensive syntax for the SET CONFIGURATION SMTP command /SYSTEM_HEADER_ORG and /SYSTEM_HEADER_SYS qualifiers. The syntax should be: /SYSTEM_HEADER_ORG="string" /SYSTEM_HEADER_SYS="string" o The Programmer's Guide was enhanced as follows: - Socket Library: The chapter now contains an explanation that the VAX C and DEC C socket library routines are preferred over the TCPware Socket Library for VMS 5.3 and later. The chapter now includes a section on transitioning to the C Socket Library: how to use the header files and link applications. The TCPware Socket Library chapter was changed to Appendix A at the end of the guide. A modification to the TCPware Socket Library appendix is the addition of the FIOASYNC request code for the SOCKET_ ================================================================================ Archive-Date: XXX, 20 May 1996 12:20:43 -0400 Subject: Re: TCPware V5.1 - [3/3] Message-ID: <1996May20.122043.1979@delta.process.com> From: ostrom@process.com (Andy Ostrom) Date: 20 May 96 12:20:43 -0400 References: <1996May20.121609.1976@delta.process.com> MIME-Version: 1.0 Content-Type: message/partial; id="832609372@Andy Ostrom"; number=3; total=3 IOCTL routine. - TELNET Library: The TEL_CREATE_TERMINAL library routine is now documented. This routine opens and allocates a connection to an NTA device so that you can use a terminal device with TELNET. - SNMP Extendible Agent API Routines: This is a new chapter. (See Section 2.28 for details.) ERRATA: A warning to application developers about possible access violations was not included. (See the "Warning to Application Developers" note in Section 2.28.) o The NetWare Services Administrator's Guide was enhanced as follows: - FSS_CONSOLE Reference: FSS_CONSOLE now includes two new commands to support packet padding (SET READ PAD and SET WRITE PAD), two new commands to enable or disable Windows 95 functionality with the FSS server (ENABLE FSS95 and DISABLE FSS95), and two new commands to enable 5-4 Documentation Notes or disable VMS broadcast messages from appearing (ENABLE VMSBROADCAST and DISABLE VMSBROADCAST). (See Chapter 4 for more information.) The syntax of the QUEUE JOBS command was corrected to QUEUE qname JOBS. It was previously given as QUEUE JOBS qname. - FSS-OpenVMS Section: A number of places in the chapters of this section now include an explanation that FSS does not recognize files with the .DIR extension as OpenVMS directories and lists them without the extension. Always use the [dir] syntax with FSS-OpenVMS. 5.2 HELP Files HELP file changes mirror enhancements to the documentation and reflect product modifications covered in these Release Notes. Many help file corrections were made, including a restructur- ing of topics at the top level of the TCPWARE help file, and an explanation of how to navigate through help. Documentation Notes 5-5 Chapter__6_______________________________________________________ Locating Software on the Internet Educational institutions, commercial organization, and others have made numerous software packages freely available to you over the Internet. Note Process Software Corporation neither supports nor provides warranties for these software packages. Some of these software packages have been ported to VMS. Some of the packages ported to VMS may work directly with TCPware, or require the use of UCX emulation, or require you to make code changes. ARCHIE is a tool that helps you locate available software on the Internet. You can TELNET to the nearest ARCHIE server if you do not know where to locate a software package. See the following list for some of the ARCHIE servers (log in as archie): ARCHIE.ANS.NET (USA[NY]) ARCHIE.RUTGERS.EDU (USA[NJ]) ARCHIE.SURA.NET (USA[MD]) ARCHIE.MCGILL.CA (Canada) ARCHIE.FUNET.FI (Finland/Mainland Europe) ARCHIE.AU (Australia) ARCHIE.DOC.IC.AC.UK (Great Britain/Ireland) The following books provide information about using the Internet, ARCHIE, and other software packages: o Krol, Ed. The Whole Internet User's Guide and Catalog. 1992: O'Reilly & Associates, Inc., Sebastopol, California o Marine, April et al. Internet: Getting Started. 1993: PTR Prentice Hall, Englewood Cliffs, New Jersey Organizations place available software packages at anonymous FTP sites. Some software packages may be available from more than one site. Table 6-1 lists some available software packages and a site at which it is available. TELNET to the nearest ARCHIE server if you do not know where a software package is located. Note that some are provided on the TCPware for OpenVMS CD-ROM distribution media. Locating Software on the Internet 6-1 Table_6-1:__Software_on_the_Internet__________________________ Software Package_____Site______________________Note____________________ ANU-NEWS KUHUB.CC.UKANS.EDU Provided on TCPware CD-ROM ARCHIE SODA.BERKELEY.EDU GOPHER BOOMBOX.MICRO.UMN.EDU LYNX FTP2.CC.UKANS.EDU Provided on TCPware (/pub/lynx) CD-ROM WAIS________SUNSITE.UNC.EDU___________________________________ 6-2 Locating Software on the Internet