NETLIB015.AA ð NETLIB015.AaBACKUP KITINSTAL.COM,NETLIB015.RELEASE_NOTES NETLIB015.A/SAVE/INTERCHANGE/BLOCK=4096/NOCRC/GROU=0 MADISON  @È)œ‘¶–T6.0 _CIA::  _$1$STA0: V6.0 äð*[NETLIB]KITINSTAL.COM;118+,œ. / @ 4M N-œ0ª123KÿPWO 56’‡ÒªØ…–7R™|oÙ…–8&ibh—9G @HˆªJÿ $! [NETLIB]KITINSTAL.COM$!.$! KITINSTAL procedure for installing NETLIB.$!0$! 31-JAN-1991 V1.0 Madison Initial coding.M$! 05-FEB-1991 V1.0-1 Madison Two parts for integration into other kits.$!)$ ON CONTROL_Y THEN GOTO NETLIB_CONTROL_Y"$ ON WARNING THEN GOTO NETLIB_FAIL$!5$ IF P1 .EQS. "VMI$_INSTALL" THEN GOTO NETLIB_INSTALL$ EXIT VMI$_UNSUPPORTED$!$NETLIB_CONTROL_Y:$ VMI$CALLBACK CONTROL_Y$! $NETLIB_FAIL:$ NETLIB_STATUS == $STATUS=$ IF F$TRNLNM ("NETLIB_STUP") .NES. "" THEN CLOSE NETLIB_STUP$ EXIT 'NETLIB_STATUS$!$NETLIB_INSTALL:$!$ IF P2 THEN SET VERIFY$! $ NETLIB_SAY := WRITE SYS$OUTPUT$!#$ IF F$GETSYI("HW_MODEL") .LT. 1024$ THEN$ NETLIB_VAX = 1$ NETLIB_AXP = 0$ NETLIB_REQD_VMSVER = "V5.0""$ NETLIB_REQD_VMSVER_OLD = "050"K$ VMI$CALLBACK CHECK_VMS_VERSION NETLIB_VMSVEROK 'NETLIB_REQD_VMSVER_OLD'$ IF .NOT. NETLIB_VMSVEROK$ THEN$$ VMI$CALLBACK MESSAGE E VMSVER -F "This product requires VMS version ''NETLIB_REQD_VMSVER' to run.'$ EXIT VMI$_FAILURE $ ENDIF$ ELSE$ NETLIB_VAX = 0$ NETLIB_AXP = 1$ ENDIF$!$!C$ VMI$CALLBACK CHECK_NET_UTILIZATION NETLIB_ENOUGHDISK 3000 30 30003$ IF .NOT. NETLIB_ENOUGHDISK THEN EXIT VMI$_FAILURE$!*$ VMI$CALLBACK SET SAFETY CONDITIONAL 5000$!$!$ TYPE SYS$INPUT:5 NETLIB Installation ProcedureG Copyright © 1992, 1993 Matthew D. Madison. All Rights Reserved.@ Redistribution for no commercial gain is permitted.$!$!$ VMI$CALLBACK SET PURGE ASK $ VMI$CALLBACK RESTORE_SAVESET B9$ @VMI$KWD:NETLIB_INSTALL 'P1 'P2 'P3 'P4 'P5 'P6 'P7 'P8$ NETLIB_STATUS == $STATUS+$ IF NETLIB_STATUS .EQ. VMI$_SUCCESS THEN - TYPE SYS$INPUTE All NETLIB images have been linked. Remember to edit your system< startup command procedure to add the following commmand:% $ @SYS$STARTUP:NETLIB_STARTUPB The file SYS$STARTUP:NETLIB_STARTUP.COM can be edited to alterE the selection of the default NETLIB transport library, as needed.$!$ EXIT 'NETLIB_STATUSÿÿà NETLIB015.A£ú œ![NETLIB]NETLIB015.RELEASE_NOTES;7Tÿ?í%ð!*[NETLIB]NETLIB015.RELEASE_NOTES;7+,£ú ./ @ 4TÎÿ?-œ0ª123KÿPWO56èM(š‘¶–7h¸ñš‘¶–89G @HˆªJÿ   NETLIB Release Notes April, 1993= This file contains the release notes for the NETLIB@ TCP/IP interface library. It describes any last-minute? features, restrictions, changes, or additions made to NETLIB.A Revision/Update Information: This is a revised manual.> Operating System and Version: VAX/VMS V5.0 or later;A OpenVMS AXP V1.0 or later4 Software Version: NETLIB V1.5D Matthew D. Madison TGV, Inc. Santa Cruz, California  " ________________________ 22 April 19936 DISCLAIMER: The author and TGV, Inc. make no; representations or warranties with respect to the? contents hereof and specifically disclaim any implied: warranties of merchantability or fitness for any particular purpose. __________, Copyright ©1993 Matthew D. Madison; The following are trademarks of Digital Equipment Corporation:9 DEC ULTRIX VAX9 VAXcluster VAXstation VMS6 MultiNet is a registered trademark TGV, Inc.4 TCPware is a trademark of Process Software Corporation.  A _______________________________________________________ ContentsA _______________________________________________________A CHAPTER 1 INSTALLING NETLIB 1-1A _______________________________________________________A CHAPTER 2 NETLIB REQUIREMENTS 2-1A _______________________________________________________A CHAPTER 3 NEW FEATURES 3-1A _________________________________________________A 3.1 DOMAIN SERVER LIST INITIALIZATION 3-2A _________________________________________________A 3.2 NETLIB_DOMAIN LOGICAL NAME 3-3A _________________________________________________A 3.3 DEBUGGING CODE 3-3A _______________________________________________________A CHAPTER 4 BUG FIXES 4-1A iii  A _______________________________________________________ 1 Installing NETLIB; NETLIB is installed with the VMSINSTAL procedure:5 $@SYS$UPDATE:VMSINSTAL NETLIB015 ddcu:? You will be asked which TCP/IP packages for which you= wish to install NETLIB support and where the NETLIB& librà NETLIB015.A£ú œ![NETLIB]NETLIB015.RELEASE_NOTES;7Tÿ?p¼aries should be located.A 1-1  A _______________________________________________________ 2 NETLIB Requirements< NETLIB libraries are INSTALLed as shared shareable< libraries. The NETLIB_SHRXFR transport-independent@ library requires 3 global pages and 2 global sections.? Each selected transport-dependent library requires 13- global pages and 2 global sections.< The amount of disk space required for each library$ varies based on transport:* CMU V6.4 270 blocks) CMU V6.5 and later 30 blocks) UCX V1.2 15 blocks< UCX V1.3 and later 260 blocks (VAX), 350 blocks% (AXP)< MultiNet V2.2 and 260 blocks (VAX), 360 blocks% later (AXP)< PSC TCPware 260 blocks (VAX), 360 blocks% (AXP)> The SHRXFR transport-independent library takes up 10 blocks.> The libraries can be placed in SYS$LIBRARY or in any desired directory.A 2-1  A _______________________________________________________ 3 New Features? NETLIB V1.5D is a maintenance release and contains no> new features over V1.5, except for adding TCPware to> the list of TCP/IP packages supported on OpenVMS AXP systems.< NETLIB V1.5 added the following feature over V1.4:6 o Support for TCPware from Process Software2 Corporation, courtesy of Bernie Volz.; NETLIB V1.4 added the following new features over V1.3:: o the ability to specify a timeout value on UDP= receives. A parameter has been added to the UDP_> RECEIVE routine to accommodate this change. (This< was not correctly implemented in V1.4, but does work in V1.5D).= o the ability to redirect NETLIB debugging output.; A new routine, NET_SET_TRACE_ROUTINE, has been9 added. By passing the address of your output= routine (which should mimic LIB$PUT_OUTPUT), you> can redirect debug output (currently only used in> the DNS_MXLOOK routine for TCP/IP implementations3 other than CMU-Tek V6.5 and UCX V1.2).3 o some minor improvements in DNS_MXLOOK.: NETLIB V1.3 added one new feature over V1.2: the= ability to create an active TCP/IP connection while> at the same time fixing the port number on the local: host. This is done with the addition of the NOT_/ PASSIVE flag on the NET_BIND routine.A 3-1   New Features> NETLIB V1.2 added one new feature over V1.1: the TCP: receive routines now allow the caller to specify: a timeout value for the receive. Previously, all- receives timed out after 5 minutes.; NETLIB V1.1 added the following new features over> V1.0, all of which have to do with the NETLIB_MXLOOK> routine. These features affect NETLIB operatÐ NETLIB015.A£ú œ![NETLIB]NETLIB015.RELEASE_NOTES;7Tÿ?¦°ion with< UCX (V1.3 or later), MultiNet (V2.2 or later), and@ CMU-Tek V6.4. Operation with CMU-Tek V6.5 and later is not affected.L __________________________________________________________________+ 3.1 Domain Server List Initialization? The NETLIB_MXLOOK routine, for UCX V1.3, TCPware, and? MultiNet, will use the transport-specific name server: list logical names for initializing its internal? name server list. For UCX, the logical names used are? UCX$BIND_SERVERnnn, where "nnn" is a 3-digit sequence= number. For Multinet, the logical name is MULTINET_> NAMESERVERS. For TCPware, the logical name is TCPIP_ NAMESERVERS.= For CMU-Tek V6.4, the NETLIB installation procedure@ automatically includes a definition for NETLIB_CMU064_> NAMESERVERS, since the name server list used by CMU-> Tek is not readily available. You should modify that< logical name definition as needed for your system.: You can override the default name server list by; defining the logical name NETLIB_NAMESERVERS as a@ search list containing the names of the domain servers1 you would like NETLIB initially to use. 3-2  A New FeaturesL __________________________________________________________________$ 3.2 NETLIB_DOMAIN Logical Name< For CMU V6.4, UCX V1.3, TCPware, and MultiNet, you? can define a logical name NETLIB_DOMAIN (which may be> a search list) to specify the domains to be used for@ partial name completion in the MXLOOK routine. This is? not needed for CMU V6.5 (which uses the built-in name< resolver) or UCX V1.2 (which does not support name resolvers).> If undefined, the MXLOOK routine uses full host name@ as the domain name, trimming one segment from the left> part (and doing so repeatedly until there is no more domain name to trim).+ For example, if your host name is9 VAX.DEPT.COMPANY.COM, the default behaviour for9 doing name completeion would be to first append= DEPT.COMPANY.COM, then COMPANY.COM, then COM to any+ address. By defining the logical:T $DEFINE/SYSTEM NETLIB_DOMAIN "dept.company.com","dept2.company.com",-. _$ "company.com"@ you will cause the MXLOOK routine to append just those; domains you specify for name completion purposes.L __________________________________________________________________ 3.3 Debugging Code@ The MXLOOK routine contains debugging code that prints= out a trace of its activity. To activate this code,; define the logical name NETLIB_DEBUG system-wide:/ $DEFINE/SYSTEM NETLIB_DEBUG TRUE> Debugging code may be added to other NETLIB routines in a future release.A 3-3  A _______________________________________________________ 4 Bug Fixes< NETLIB V1.5D includes the following bug fixes over V1.4A:= o NET_GET_ADDRESS would return success status with> a zero-length address list when uà NETLIB015.A£ú œ![NETLIB]NETLIB015.RELEASE_NOTES;7Tÿ?;)sed with CMU-Tek< TCP/IP. It now correctly returns SS$_ENDOFFILE.? o The CMU-Tek error status NET$_CREF was not getting< translated. It now correctly translates to SS$_ REJECT.> o Some arguments were not passed correctly in QIO's( for the MultiNet interface.= o The DNS_MXLOOK routine was not properly checking= the success or failure of the translation of the< NETLIB_DOMAIN logical name, causing unnecessary= additional lookups to occur if that logical were: defined. (Does not apply to the CMU-Tek V6.5+ implementation.)< o The DNS_MXLOOK routine now checks to see if the< name to be looked up contains a dot, and if so,> first checks the name by itself before attempting9 to do name completion. This should generally= reduce the number of lookups made, since in most; cases, names with dots in them are full domain8 names. (Does not apply to the CMU-Tek V6.5+ implementation.)A 4-1ÿÿà