                                     '                     DEC TCP/IP Services H                     for_OpenVMS_________________________________________!                     Release Notes                          April 1995  I                     These Release Notes are for installers, managers, and !                     end-users of:   F                     o  DEC TCP/IP Services for OpenVMS VAX Version 3.3  F                     o  DEC TCP/IP Services for OpenVMS AXP Version 3.3  =                     This document updates the UCX Version 3.2 &                     documentation set.            E                     Operating System:             VMS VAX Version 5.5 F                                                   OpenVMS VAX Versions?                                                   6.0, 6.1, 6.2 F                                                   OpenVMS AXP Versions=                                                   6.1 and 6.2   I                     Software Version:             DEC TCP/IP Services for I                                                   OpenVMS VAX Version 3.3 I                                                   DEC TCP/IP Services for I                                                   OpenVMS AXP Version 3.3   1                     Digital Equipment Corporation *                     Maynard, Massachusetts                   ?           The information in this document is subject to change D           without notice and should not be construed as a commitment=           by Digital Equipment Corporation. Digital Equipment C           Corporation assumes no responsibility for any errors that &           may appear in this document.  B           Possession, use, or copying of the software described inA           this publication is authorized only pursuant to a valid D           written license from Digital or an authorized sublicensor.  @           Digital Equipment Corporation makes no representationsA           that the use of its products in the manner described in B           this publication will not infringe on existing or futureB           patent rights, nor do the descriptions contained in thisB           publication imply the granting of licenses to make, use,>           or sell equipment or software in accordance with the           description.  :                        Digital Equipment Corporation 19951                               All Rights Reserved 0                                Printed in U.S.A.    ;           The following are trademarks of Digital Equipment B           Corporation:  ADVANTAGE-NETWORKS, Alpha AXP, AXP, DDCMP,E           DEC, DECnet, DECserver, DECstation, DECUS, DECwindows, LAT, C           MicroVAX, OpenVMS, PATHWORKS, ULTRIX, UNIBUS, VAX, VAXBI, D           VAXcluster, VAXstation, VMS, VMScluster, VT, the Alpha AXP%           logo, and the Digital logo.   3           The following are third-party trademarks:   E           HP and Hewlett-Packard are registered trademarks of Hewlett            Packard Company.  A           IBM is a registered trademark of International Business            Machines Corporation.   D           MS-DOS is a registered trademark of Microsoft Corporation.  :           OSF/1 is a registered trademark of Open Software           Foundation, Inc.  E           PostScript is a registered trademark of Adobe Systems, Inc.   ?           Sun, NFS, and PC-NFS are registered trademarks of Sun            Microsystems, Inc.  A           UNIX is a registered trademark in the United States and >           other countries, licensed exclusively through X/Open           Company Ltd.  C           USRobotics and Sporster are registered trademarks of U.S.            Robotics, Inc.  @           All other trademarks and registered trademarks are the/           property of their respective holders.                                  C   _________________________________________________________________   C                                                            Contents       C   Preface...................................................    vii   "   1  New Features and Enhancements  C         1.1   Management Control Program ...................    1-1 C         1.2   NFS Client ...................................    1-2 C         1.2.1     OpenVMS-to-UNIX Mode .....................    1-2 C         1.2.2     OpenVMS-to-OpenVMS Mode ..................    1-2 9         1.2.2.1     File Organizations and Record Formats C                     ........................................    1-2 C         1.2.2.2     File Name Conversion ...................    1-2 C         1.2.2.3     Export Options .........................    1-2 C         1.3   NTP ..........................................    1-4 C         1.3.1     Strata Numbers ...........................    1-4 C         1.3.2     Logging ..................................    1-4 C         1.3.3     Setting Up NTP ...........................    1-6 C         1.3.3.1     NTP Configuration File .................    1-6 C         1.4   RLOGIN and RSH ...............................    1-9 C         1.4.1     Default Case .............................    1-9 C         1.4.2     Incoming RLOGIN Proxy ....................    1-9 C         1.5   SLIP and CSLIP ...............................    1-9 C         1.5.1     Features of SLIP .........................   1-10 C         1.5.2     Features of CSLIP ........................   1-10 C         1.5.3     Protocol Description .....................   1-10 C         1.5.4     Uses for SLIP ............................   1-11 C         1.5.5     Setting Up a SLIP Interface: Overview ....   1-12 C         1.5.5.1     Setting Up SLIP: Hard-wired Lines ......   1-15 C         1.5.5.2     Setting Up SLIP: Dial-up Lines .........   1-16 :         1.5.5.3     Setting Up SLIP: UCX As a Dial-up SLIPC                     Provider ...............................   1-18 :         1.5.5.4     Setting Up a Host "Directly Connected"C                     to the LAN .............................   1-20 C         1.5.5.5     UCX As a SLIP Gateway with Proxy ARP ...   1-20   C                                                                 iii                    E           1.5.6     Shutting Down SLIP .......................   1-21 E           1.5.7     Troubleshooting ..........................   1-21 E           1.6   TELNET .......................................   1-22 E           1.6.1     SHOW SESSION Command .....................   1-22 E           1.6.2     Command Qualifiers .......................   1-22 E           1.6.3     Error and Status Messages ................   1-23 E           1.7   UCX$TRACE ....................................   1-25   %     2  Installation and Configuration   E           2.1   Requirements..................................    2-1 E           2.1.1     Operating System .........................    2-1 E           2.1.2     Licenses .................................    2-1 E           2.1.3     Information You Need .....................    2-2 E           2.2   Server Configuration Menu ....................    2-2 E           2.3   New Images ...................................    2-5 E           2.4   Reinstalling .................................    2-5 =           2.4.1     Upgrading from UCX Version 3.0 or Earlier E                     ..........................................    2-5 E           2.4.2     Reverting to a Previous Version ..........    2-6 E           2.4.3     RSH and REXEC ............................    2-6        3  Corrected Problems   E           3.1   Kernel .......................................    3-2 E           3.1.1     Security Driver ..........................    3-3 E           3.1.2     TELNET (TN) Driver .......................    3-3 E           3.1.3     UCX$TRACE Utility ........................    3-3 E           3.2   PWIP Driver ..................................    3-4 E           3.3   Sun RPC Programming Interface ................    3-6 E           3.4   Management Control Program ...................    3-6 E           3.5   BIND Server ..................................    3-8 E           3.6   Remote BOOT Server ...........................    3-8 E           3.7   FTP ..........................................    3-9 E           3.8   LPD ..........................................   3-11 E           3.9   NFS Client ...................................   3-16 E           3.10  NFS Server ...................................   3-16 E           3.11  PC-NFSd ......................................   3-16 E           3.12  Portmapper ...................................   3-17 E           3.13  Remote Shell .................................   3-17 E           3.14  SMTP .........................................   3-18 E           3.15  TELNET .......................................   3-21 E           3.15.1    TELNET Print Symbiont (TELNETSYM) ........   3-21          iv                   I               3.15.2    TELNET Client ............................   3-22            4  Known Problems              5  Restrictions   I               5.1   NFS Client and Server ........................    5-1 I               5.2   NFS Client ...................................    5-3 I               5.3   UCX on VMScluster Systems ....................    5-5 I               5.4   BIND Server ..................................    5-5 I               5.5   Management Commands ..........................    5-5            6  Documentation  I               6.1   Omitted Documentation ........................    6-1 I               6.1.1     TELNET Print Symbiont (TELNETSYM) ........    6-1 I               6.1.1.1     Setting Up a Print Queue ...............    6-2 I               6.1.1.2     Link Establishment .....................    6-2 I               6.1.1.3     Link Shutdown ..........................    6-2 I               6.1.1.4     Output Byte Stream .....................    6-3 I               6.1.1.5     Configuring Print Queues ...............    6-3 >               6.1.1.5.1    Stream of Print Bytes Sent Over theI                            Link ..................................    6-4 I               6.1.1.5.2    Diagnostics Logging ...................    6-4 I               6.1.1.5.3    Characteristics of the TCP/IP Link ....    6-6 B               6.1.1.5.4    Establishment and Release of the TCP/IPI                            Link ..................................    6-7 I               6.1.1.5.5    Other .................................    6-7 I               6.1.1.6     Relay Queues ...........................    6-8 I               6.1.1.7     Common Problems ........................    6-8 I               6.1.2     FTP Logical Names ........................   6-11 I               6.1.3     BIND SERVER Error Message ................   6-11 I               6.1.4     Configuring SMTP .........................   6-12 I               6.2   Known Errors .................................   6-13 8               6.2.1     "DEC TCP/IP Services for OpenVMSI                         Management" Manual .......................   6-13 I               6.2.1.1     Table 6-2...............................   6-13 I               6.2.1.2     Section 6.6.4...........................   6-13 I               6.2.1.3     Section 9.1.1...........................   6-13 I               6.2.1.4     Section 9.3.............................   6-14 I               6.2.1.5     Table 9-2...............................   6-14 I               6.2.1.6     Section 9.5.7...........................   6-14 I               6.2.1.7     Section 9.5.8.2.........................   6-14   I                                                                         v                    4           6.2.2     "DEC TCP/IP Services for OpenVMSE                     Management Command Reference" Manual .....   6-15 5           6.2.2.1     NFS Server: MAP-Related Command E                       Descriptions ...........................   6-15 E           6.2.2.2     CONVERT /ULTRIX HOST Command............   6-15 E           6.2.2.3     SET BOOTP Command.......................   6-15 E           6.2.2.4     SET MX_RECORDS Command..................   6-16 4           6.2.2.5     SET CONFIGURATION NAME_SERVICEE                       Command.................................   6-16 6           6.2.2.6     SET CONFIGURATION NONAME_SERVICEE                       Command.................................   6-16 E           6.2.2.7     SET SERVICE Command.....................   6-16 E           6.2.2.8     MOUNT Command ..........................   6-16        7  Unsupported Components   E           7.1   Support for Outbound TELNET Devices ..........    7-2 E           7.2   Remote File Copy (RCP) .......................    7-2   E           RCP ................................................    7-3 E           7.3   Incoming RLOGIN Proxies ......................    7-8        A  Installed Files  E           A.1   UCX Files ....................................    A-1 E           A.2   Files Installed for PATHWORKS Systems.........    A-5        Examples  >           5-1       Mounting from UNIX and OpenVMS NFS ClientsE                     ..........................................    5-3   =           5-2       Viewing Directories from UNIX and OpenVMS E                     NFS Clients ..............................    5-4   ;           6-1       Typical SHOW CONFIGURATION BIND Display E                     ..........................................   6-12                      vi                            Figures   I               1-1       Example Section from an NTP Log File .....    1-5   I               1-2       Example NTP Configuration File ...........    1-8   9               1-3       Configuration of Distant Networks I                         Connected by SLIP ........................   1-12   @               2-1       Example: SERVER Components ConfigurationI                         Menu .....................................    2-3            Tables  ;               1-1       Configuring SLIP: SET INTERFACE and I                         SET CONFIGURATION INTERFACE Commands .....   1-13   B               1-2       TELNET and TN3270 Commands: New QualifiersI                         ..........................................   1-23   I               1-3       TCPIPTRACE Command Qualifiers ............   1-26   :               3-1       Corrected Problems with ManagementI                         Commands .................................    3-6   ?               7-1       RCP Command: Specifying the Source File I                         ..........................................    7-4                                     I                                                                       vii                              I         _________________________________________________________________   I                                                                   Preface       B               The DEC TCP/IP Services for OpenVMS (UCX) product isG               Digital's implementation of the TCP/IP protocol suite and H               internet services for OpenVMS VAX and OpenVMS AXP systems.  +               These Release Notes apply to:   @               o  DEC TCP/IP Services for OpenVMS VAX Version 3.3  @               o  DEC TCP/IP Services for OpenVMS AXP Version 3.3           Audience  E               This document is for UCX installers, managers, and end-                users.  F               It is assumed that you are familiar with the UCX product4               and the Version 3.2 documentation set.           About This Manual   ?               This document contains the following information:   *               o  Chapter 1, "New Features"  I                  Lists the features new to this release and describes how (                  to use and manage them.  <               o  Chapter 2, "Installation and Configuration"  C                  Updates the Version 3.2 of the DEC TCP/IP Services G                  for OpenVMS Installation and Configuration manual with 9                  information specific to UCX Version 3.3.   0               o  Chapter 3, "Corrected Problems"  G                  Lists the problems in previous releases that have been &                  fixed in Version 3.3.  ,               o  Chapter 4, "Known Problems"  I                                                                       vii                    A              Describes the problems identified in the Version 3.3s              software.  &           o  Chapter 5, "Restrictions"  4              Lists use restrictions of the software.  '           o  Chapter 6, "Documentation"   ?              Updates the text of the Version 3.2 documentation.3  0           o  Chapter 7, "Unsupported Components"  A              Documents the new software that is included with the A              Version 3.3 release but is not, in any way, legal or -              otherwise, supported by Digital.        Documentation Set   A           For information about UCX and how to use it, please use B           the Version 3.2 documentation set, which consists of the           following manuals:  B           o  DEC TCP/IP Services for OpenVMS Concepts and Planning  %              Order Number AA-Q06TC-TE   =           o  DEC TCP/IP Services for OpenVMS Installation ands              Configuration  %              Order Number AA-LU49G-TEP  9           o  DEC TCP/IP Services for OpenVMS User's Guide   %              Order Number AA-PC27F-TE   7           o  DEC TCP/IP Services for OpenVMS Management   %              Order Number AA-LU50G-TE   ?           o  DEC TCP/IP Services for OpenVMS Management Commandg              Reference  %              Order Number AA-PQQGD-TEm  @           o  DEC TCP/IP Services for OpenVMS Sun RPC Programming  %              Order Number AA-Q06VC-TEo  A           o  DEC TCP/IP Services for OpenVMS System Service and C.              Socket Programming   %              Order Number AA-LU51G-TE        viii i  i                    I                                                                         1iI         _________________________________________________________________e  H                                            New Features and Enhancements    ,               The Version 3.3 release of theF               DEC TCP/IP Services for OpenVMS (UCX) product offers the%               following new software:m  D               o  Management control program (enhanced) (Section 1.1)  4               o  NFS Client (enhanced) (Section 1.2)  "               o  NTP (Section 1.3)  H               o  RLOGIN and RSH (enhanced) (Section 1.4 and Section 7.3)  -               o  SLIP and CSLIP (Section 1.5).  0               o  TELNET (enhanced) (Section 1.6)  3               o  UCX$TRACE (enhanced) (Section 1.7)W  -               o  LPD (enhanced) (Section 3.8)e  /               o  SMTP (enhanced) (Section 3.14)   =               o  TELNET Print Symbiont (TELNETSYM) (enhanced)I!                  (Section 3.15.1)n  D               o  Outbound TELNET devices (unsupported) (Section 7.1)  >               o  Remote Copy (RCP) (unsupported) (Section 7.2)  &         1.1 Management Control Program  -               The following features are new:p  6               o  Terminating TCP connections on demand  G                  With the UCX DISCONNECT DEVICE_SOCKET command, you can F                  interactively terminate existing TCP connections, for                  example:   4                  UCX> DISCONNECT DEVICE_SOCKET BG123                 o  Managing SLIP  I                                        New Features and Enhancements  1-1r o  u                            See Section 1.5.5.N       1.2 NFS Client  E           The Network File System (NFS) Client software now functionsl           in two modes:   ,           o  OpenVMS-to-UNIX (Section 1.2.1)  /           o  OpenVMS-to-OpenVMS (Section 1.2.2)        1.2.1 OpenVMS-to-UNIX Mode  %           No change from Version 3.2.r  !     1.2.2 OpenVMS-to-OpenVMS Modei  A           If the NFS server node is running UCX Version 3.3, this_E           mode is used automatically, except if you mount a container B           file system. If it is running any earlier version of theE           UCX server or any server other than UCX, the client runs in            OpenVMS-to-UNIX mode.   B           When you upgrade the NFS Server software to Version 3.3,@           Version 3.3 client nodes must remount the file systems?           served by the upgraded server before they start using."           OpenVMS-to-OpenVMS mode.  4           For more information, see Section 6.2.2.8.  1     1.2.2.1 File Organizations and Record Formats   ?           All OpenVMS file organizations and record formats are 3           supported for both read and write access..        1.2.2.2 File Name Conversion  @           In OpenVMS-to-OpenVMS mode, file names appear in their           unconverted form..       1.2.2.3 Export Options  ?           If you add a file system entry to the Export Database.C           specifying the PURGE_VERSIONS or DATA_CONVERSION options,.A           the NFS Client in OpenVMS-to-OpenVMS mode ignores these            options.  $           For example, if you issue:  J           UCX> ADD EXPORT "/path/name" /HOST=host /OPTIONS=DATA_CONVERSION  %     1-2 New Features and Enhancements. .  .              C               sequential files that are not STREAM_LF record format F               are converted to STREAM_LF for UNIX clients, but not for9               OpenVMS clients in OpenVMS-to-OpenVMS mode.                                                                                     I                                        New Features and Enhancements  1-3.    s                   1.3 NTP.  B           This release of UCX implements the Network Time Protocol9           (NTP), described in Request for Comments (RFC):H  D           o  1059, "Network Time Protocol (Version 1), Specification!              and Implementation."   !           o  RFC 1119 (Version 2)   !           o  RFC 1305 (Version 3)r  A           NTP synchronizes timekeeping and provides accurate timee?           stamps. Hosts running NTP can participate in a TCP/IPL/           network with fully synchronized time.        1.3.1 Strata Numbers  :           Strata numbers identify the participating peers:  4           o  Lower-strata peers act as time servers.  -           o  Higher-strata peers are clients..  >           o  Hosts in both directions - time provider and time,              requester - are known as peers.  E           o  An Internet Time Server, with the lowest number, Stratum D              1, has a radio-clock-generated clock based on UniversalD              Coordinated Time (UTC). NTP times are an offset of UTC,0              formerly Greenwich Mean Time (GMT).  C           o  Any higher stratum host is, by definition, a Stratum 2.D              host or higher. Most participating hosts have a stratumE              higher than Stratum 2. They act as timekeepers for other &              hosts on the NTP network.  A           o  Each host has its identifying stratum number encoded.;              within UDP datagrams that these peers exchangeeB              periodically with each other. The datagrams are time-<              stamped. Each host adjusts its clock as needed.       1.3.2 Logging.  B           NTP maintains a log file and reopens it daily, each timeD           creating a new version of the file. The older versions areD           not automatically purged. Figure 1-1 shows a small portion           of an NTP log file.   %     1-4 New Features and Enhancementso .  .                I         _________________________________________________________________     7         Figure 1-1 Example Section from an NTP Log File.  )         * lost contact with peer 16.1.0.2 (         * sync source lost, free running&         * re-acquired peer 16.20.208.8@         * selected new sync source 16.20.208.8, now at stratum 5O          17:09:56.09    +0.004304 seconds, trip 0.1039, aperture 0.0143, hold 4iO          17:10:06.09    +0.003959 seconds, trip 0.1039, aperture 0.0140, hold 3nO          17:10:38.09    +0.004832 seconds, trip 0.1000, aperture 0.0148, hold 2.O          17:11:10.09    +0.004043 seconds, trip 0.1000, aperture 0.0140, hold 1.O          17:11:42.09    +0.002963 seconds, trip 0.1000, aperture 0.0130, hold 0 I          17:12:14.17    +0.003922 seconds, new tick 100004 for 31 seconds-I          17:12:46.18    +0.002536 seconds, new tick 100004 for 36 seconds I          17:13:50.25    +0.006192 seconds, new tick 100004 for 89 seconds I          17:15:58.18    +0.000944 seconds, new tick 100004 for 13 seconds H          17:20:14.28    +0.000444 seconds, new tick 100004 for 6 secondsI          17:24:30.38    +0.003322 seconds, new tick 100004 for 47 seconds3I          17:33:02.29    +0.001390 seconds, new tick 100004 for 20 secondsMI          17:50:06.40    +0.001011 seconds, new tick 100004 for 14 secondsTI          18:24:14.41    -0.001323 seconds, new tick 100002 for 19 secondsTH          18:58:22.42    -0.000461 seconds, new tick 100002 for 6 seconds#         * re-acquired peer 16.1.0.2C=         * selected new sync source 16.1.0.2, now at stratum 3PO          19:26:00.37    -0.005816 seconds, trip 0.2600, aperture 0.0158, hold 4eO          19:26:10.49    -0.006081 seconds, trip 0.2200, aperture 0.0161, hold 3.O          19:26:42.50    -0.012000 seconds, trip 0.2300, aperture 0.0120, hold 2.O          19:27:14.54    +0.017324 seconds, trip 0.2700, aperture 0.0120, hold 1.O          19:27:46.51    +0.001404 seconds, trip 0.2200, aperture 0.0114, hold 0.I          19:33:38.66    -0.002879 seconds, new tick 100002 for 31 secondseI          19:38:10.76    -0.004792 seconds, new tick 100001 for 31 secondsiE          19:45:06.97    +0.055078 seconds, discarded, trip > 0.132004tI          19:48:02.92    -0.004358 seconds, new tick 100001 for 31 secondsk  I         _________________________________________________________________S              I                                        New Features and Enhancements  1-5. .  .                   1.3.3 Setting Up NTP  C           Like the other services, you can configure NTP during the B           UCX configuration procedure. However, before you run theA           UCX startup procedure, you might first need to edit the C           NTP configuration file. Setting up NTP with this sequence A           of steps makes unnecessary the need to execute manually-?           UCX$NTPD_STARTUP.COM. When NTP is configured, the UCXC5           startup procedure automatically starts NTP..  2           To configure NTP, following these steps:  1           1. Run the UCX configuration procedure, (              SYS$MANAGER:UCX$CONFIG.COM.  =           2. From the Main Menu, select the SERVER Componentsl               Configuration Menu.  B           3. From the SERVER Components Configuration Menu, select7              NTP, which is Option 11 (see Section 2.2).g  E           4. Either finish running the UCX configuration procedure or.               exit at this point.  5           5. Populate the NTP Configuration File (see.              Section 1.3.3.1).  9           6. If you started UCX before properly and fully <              configuring NTP, run the NTP startup procedure,.              SYS$MANAGER:UCX$NTPD_STARTUP.COM.  "     1.3.3.1 NTP Configuration File  <           Each host maintains an NTP configuration file with:           the names of participating peers. During the UCXB           configuration procedure, if you select to configure NTP,B           the procedure creates the example NTP configuration file1           SYS$SPECIFIC:[UCX$NTP]UCX$NTP.TEMPLATE.   :           Use a copy of this template to list the names of2           participating peers. Follow these steps:  :           1. Identify the peers you want to include in the?              configuration file. These are hosts with which you <              regularly exchange data and where accurate time@              coordination is important. Each host can be both a:  C              o  Time server, from which the local host synchronizess                 its time..  %     1-6 New Features and EnhancementsU I  O              D                  o  Higher-stratum host, which synchronizes with the                     local host..  H               2. Edit SYS$SPECIFIC:[UCX$NTP]UCX$NTP.TEMPLATE to add peer                  entries.S  F                  o  Format of each entry - Type the word "peer" (whichI                     is not case-sensitive) followed by the peer host's IP                      address.  E                  o  Comment lines - If you want to add comment lines,.4                     begin each with a semicolon (;).  F               3. You do not need to identify the stratum of each peer.H                  NTP determines this by the information it sends through!                  the NTP packets.y  B               4. To achieve redundancy, list as peers multiple NTP6                  servers (systems at a lower stratum).  E               5. Save the file as SYS$SPECIFIC:[UCX$NTP]UCX$NTP.CONF.a  H                  NTP periodically reads the last version of this file so5                  that your changes to it are dynamic.                                           I                                        New Features and Enhancements  1-7                    '     Figure 1-2 shows the template file.   E     _________________________________________________________________     -     Figure 1-2 Example NTP Configuration File.  =     ;       Copyright (c) Digital Equipment Corporation, 1995i  ;     ;                        Example NTP Configuration File.  8     ; This template needs to be renamed to ucx$ntp.conf.  M     ; The Network Time Protocol (NTP) provides synchronized timekeeping amongeK     ; a set of distributed time servers and clients. The local OpenVMS host.P     ; maintains an NTP configuration file, UCX$NTP.CONF, of participating peers.G     ; UCX$NTP.CONF is maintained in the UCX$NTP sys$specific directory.   N     ; The system manager populating this file determines with which peer hostsR     ; the local hosts should negotiate and synchronize. These are hosts with whichL     ; you regularly exchange data and where accurate time coordination is anM     ; important factor.  Include at least one (but preferably two) peer hosts      ; that you are assured:        ; * provide accurate time H     ; * synchronize to Internet Time Servers (if they are not themselves     ;   Internet Time Servers).i  K     ; Two hosts provide reliability in case one of the two hosts goes down.a  O     ; The NTP peer configuration file is dynamic and does not require a restart      ; after being edited.   M     ; Samples entries follow.  Replace them with your own peers. The order of.N     ; the items is irrelevant. Each line  not commented with a ";" or "!" mustS     ; begin with the word peer and be followed by the peer host's internet address.        peer 18.72.0.3     peer 130.43.2.2_     peer 16.1.0.22  E     _________________________________________________________________       %     1-8 New Features and Enhancements                             1.4 RLOGIN and RSH  @               The RLOGIN and RSH services have the following new               enhancements.n           1.4.1 Default Case  E               As of Version 3.2, the RSH and RLOGIN end-user commands C               have a new default case for the /LOWERCASE qualifier. C               /LOWERCASE now defaults to ON. This new default might 7               affect both the UCX manager and end-user.X  <               In the Proxy Database, if the user name is in:  ?               o  Uppercase - the user must use the /NOLOWERCASE                   qualifier..  B               o  Lowercase - RSH and RLOGIN default to /LOWERCASE.  I               As of Version 3.3, the RLOGIN and RSH case-sensitivity flag1I               defaults to CASE_INSENSITIVE. With this setting, the server F               accepts both the old and new default behaviors, that is,>               both all-uppercase and all-lowercase user names.  6               To set the case-sensitivity flag, issue:  ?               UCX> SET SERVICE RLOGIN /FLAGS=(CASE_INSENSITIVE)u  <               UCX> SET SERVICE RSH /FLAGS=(CASE_INSENSITIVE)  #         1.4.2 Incoming RLOGIN Proxyr                 See Section 7.3.           1.5 SLIP and CSLIP  F               This release of UCX implements the SLIP (Serial Line IP)E               and Compressed SLIP (CSLIP) protocols, described in RFC H               1055, "A Nonstandard for Transmission of IP Datagrams Over"               Serial Lines: SLIP."  A               SLIP is a TCP/IP protocol for point-to-point serialCD               connections. Use SLIP to connect across a serial line,D               rather than an Ethernet, FDDI, or Token Ring LAN. EachF               end of the link requires SLIP software. At least one end               requires UCX.t  B               Configure dedicated SLIP lines either during the UCXG               configuration procedure or interactively. You can use any >               standard OpenVMS terminal device as a SLIP line.  I                                        New Features and Enhancements  1-9                         1.5.1 Features of SLIP  C           SLIP is a packet-framing protocol that defines a sequenceIE           of characters that frame IP packets on a serial line. SLIP:e  D           o  Is a reliable way to use serial lines to connect TCP/IP              hosts and routers.i  D           o  Allows mixes of hosts and routers to communicate. Host-E              to-host, host-to-router, and router-to-router are commonF)              SLIP network configurations.r  E           o  Allows you to run only one protocol (TCP/IP) over a SLIP               connection.  @           o  Provides no addressing, packet type identification,>              error detection, error correction, or compression              mechanisms.       1.5.2 Features of CSLIPm  B           CSLIP provides header compression, especially beneficialA           for small packets, as described in Request for CommentsO?           (RFC) 1144, "Compressing TCP/IP Headers for Low-Speed            Serial Links."  8           Header compression improves packet throughput.       1.5.3 Protocol Description  3           The SLIP Protocol defines two characters:   /           o  END - hexadecimal C0 (decimal 192)   /           o  ESC - hexadecimal DB (decimal 219)   B           To send a packet, a SLIP host starts sending the data in@           the packet. If a data byte is the same code as the ENDB           character, a two-byte sequence of ESC and hexadecimal DCE           (decimal 220) is sent instead. If the data byte is the same A           as an ESC character, a 2-byte sequence of ESC and octaloE           hexadecimal DD (decimal 221) is sent instead. When the last D           byte in the packet has been sent, an END character is then           transmitted.  D           There is no "standard" SLIP specification, nor a "defined"E           maximum packet size for SLIP. It is probably best to accept(@           the maximum packet size used by the Berkeley UNIX SLIPE           drivers: 1006 bytes including the IP and transport protocol 9           headers (not including the framing characters).   &     1-10 New Features and Enhancements                   F               UCX's implementation of SLIP accepts 1006-byte datagramsC               and does not send more than 1006 bytes in a datagram.T           1.5.4 Uses for SLIP   B               SLIP routes traffic over a serial line. SLIP has the               following uses:   7               o  Dedicated, or hard-wired, serial lines                  o  Dialups  A               You can use dial-up SLIP with these configurations:   <               o  UCX host originates the dial-up connection.  @               o  UCX host answers calls and establishes remotely,                  initiated SLIP connections.  D               Figure 1-3 shows an example of a network configurationE               using SLIP. In this configuration, SLIP Network 3.0.0.0oC               connects Networks 1.0.0.0 and 2.0.0.0, which might be @               Ethernet, FDDI, Token Ring, satellite, or wirelessF               networks. The gateways configured to make the connection"               are each multihomed:  +               o  gateway.a's connection to:e  G                  -  Network 1.0.0.0 - is its internet interface with IPo$                     address 1.0.0.25  F                  -  Network 3.0.0.0 (SLIP) - is its internet interface+                     with IP address 3.0.0.8   +               o  gateway.b's connection to:r  G                  -  Network 2.0.0.0 - is its internet interface with IPi#                     address 2.0.7.8.  F                  -  Network 3.0.0.0 (SLIP) - is its internet interface+                     with IP address 3.0.9.9   I               ___________________________________________________________n    I                                       New Features and Enhancements  1-11  o  r              C           Figure 1-3 Configuration of Distant Networks Connected byy                      SLIP   M           Network 1.0.0.0                                     Network 2.0.0.0 M           |                                                                 | M           | *----------*                                       *----------* |TM           |=| 1.0.0.24 |                                       | 2.0.0.16 |=|.M           | *----------*                                       *----------* |rM           |                                                                 | M           |                                                                 | M           |                 ...............................                 | M           |                 .             SLIP            .                 | M           |                 .        Network 3.0.0.0      .                 |cM           |                 .                             .                 |1M           |                 .                             .                 |eM           |                 .=3.0.0.8             3.0.0.9=.                 |iM           |                ggggggggggggggg   ggggggggggggggg                | M           |    1.0.0.25    g             g   g             g     2.0.7.8    |rM           |=-------------= g  gateway.a  g   g  gateway.b  g =-------------=|aM           |                g             g   g             g                |cM           |                ggggggggggggggg   ggggggggggggggg                | M           |                                                                 |-M           |                                                                 |uM           |                                                                 |eM           | *----------*                                       *----------* | M           |=| 1.0.0.26 |                                       | 2.0.0.18 |=| M           | *----------*                                       *----------* |pM           |                                                                 |e  E           ___________________________________________________________   /     1.5.5 Setting Up a SLIP Interface: Overviewe  A           Before you can communicate across a SLIP line, complete #           these prerequisite tasks:.  B           1. Choose an IP address for the interface at each end of              the line.  B              Every network interface requires a unique IP address.D              For example, a host with an Ethernet interface, an FDDID              interface, and three SLIP interfaces has five differentE              IP addresses. For another example, see Figure 1-3, whichaC              shows gateway.a and gateway.b, each with an IP address_  &     1-12 New Features and Enhancements                   I                  for their Ethernet interface and a second IP address for &                  their SLIP interface.  1               2. Establish a physical connection.8  ?               3. On the UCX host, configure the SLIP interface.5  H               After you complete these tasks, set up the SLIP interface.0               Use these UCX management commands:  C               o  SET INTERFACE - takes effect immediately. Stays in34                  effect until the next UCX shutdown.  G               o  SET CONFIGURATION INTERFACE - makes the change part of.H                  the permanent configuration. Takes effect upon the next                  UCX startup.   E               Table 1-1 shows the qualifiers of the SET INTERFACE and8D               SET CONFIGURATION INTERFACE commands for managing SLIP               interfaces.,  ;               Table 1-1 Configuring SLIP: SET INTERFACE and0I               __________SET_CONFIGURATION_INTERFACE_Commands_____________0  I               Qualifier_______________Description________________________   E               /[NO]AUTO_START         Optional. Default: /AUTO_START.9  I                                       Automatically creates the interface 7                                       upon UCX startup.1  I               ___________________________________________________________.  H               /COMPRESS=              Optional. Default: No compression.                 {ON         }eD               {OFF        }           Enables or disables TCP header:               {AUTOMATIC  }           compression (CSLIP).               {           }0  ?                                       With /COMPRESS=AUTOMATIC,6D                                       compression remains off unlessF                                       the remote end begins to use it.  I               ___________________________________________________________1  I                                                  (continued on next page)   I                                       New Features and Enhancements  1-13e d                 ?           Table 1-1 (Cont.) Configuring SLIP: SET INTERFACE and E           __________________SET_CONFIGURATION_INTERFACE_Commands_____   E           Qualifier_______________Description________________________   E           /FLOWCONTROL            Optional. Default: No flow control.a  A                                   Enables the special handling of A                                   XON and XOFF characters to work ?                                   properly with modems that are ?                                   configured to interpret these 5                                   characters locally.   B                                   Specify /FLOWCONTROL only if theC                                   host at the other end of the line 6                                   is another UCX host.  A                                   If you cannot use /FLOWCONTROL, B                                   configure your modem to pass allE                                   the XON and XOFF characters throughV0                                   transparently.  E           ___________________________________________________________   +           /HOST=host              Required..  E                                   Local host name or IP address usinge0                                   the interface.E                                   If your host is multihomed, specify3-                                   an address.e  E           ___________________________________________________________r  E                                              (continued on next page)T                      &     1-14 New Features and Enhancements i  a              C               Table 1-1 (Cont.) Configuring SLIP: SET INTERFACE and I               __________________SET_CONFIGURATION_INTERFACE_Commands_____r  I               Qualifier_______________Description________________________C  /               /SERIAL_DEVICE=device   Required.   H                                       Identifies the interface as a SLIP-                                       device.o  C                                       Specify an arbitrary terminals2                                       device name.  G                                       (Unlike Ethernet, FDDI, and TokenhB                                       Ring interface names, a SLIPF                                       interface name is not related toI               ________________________the_OpenVMS_device_name.)__________t  F               Example: The following command configures SLIP interfaceD               SL5, using the local IP address assigned to host CROW,E               with a subnet mask of 255.255.255.0. The interface usestE               the terminal device TTA3:. /COMPRESS enables TCP headertH               compression (CSLIP). /FLOWCONTROL enables special handling)               of XON and XOFF characters.   M               UCX> SET INTERFACE SL5 /HOST=CROW /NETWORK_MASK=255.255.255.0 - A               _UCX> /SERIAL_DEVICE=TTA3 /COMPRESS=ON /FLOWCONTROL.  1         1.5.5.1 Setting Up SLIP: Hard-wired Linest  !               Follow these steps:   H               1. Establish a physical connection. Plug in a serial cableE                  between the two host systems or ensure that they are ?                  both cabled to opposite ends of a leased line.O  C               2. Decide on the IP address. Follow these guidelines:s  E                  -  When you select IP addresses, it is often helpful F                     to place each physical link in a separate network,C                     or subnet. Just as each Ethernet or FDDI LAN iseB                     typically assigned one subnet number, assign a6                     separate subnet to each SLIP line.  I                     The interfaces at the two ends of the line would bothn1                     be in that particular subnet.   I                                       New Features and Enhancements  1-15o x  p              E              -  If it is advantageous for you to assign to the remotenD                 host an address in the same subnet as your site LAN,@                 use the proxy ARP feature (see Section 1.5.5.4).  B           3. Configure the SLIP interface. Issue the SET INTERFACE>              command, the SET CONFIGURATION INTERFACE command,A              or both. The /HOST and /SERIAL_DEVICE qualifiers areo              required.  <              Example: This command defines interface SL2 and?              identifies it as SLIP device TTA1: with IP addressoA              1.2.3.4. Communications on this line will use CSLIP.   O              UCX> SET INTERFACE SL2 /HOST=1.2.3.4 /NETWORK_MASK=255.255.255.0 -z4              _UCX> /SERIAL_DEVICE=TTA1: /COMPRESS=ON  *     1.5.5.2 Setting Up SLIP: Dial-up Lines  C           Either a terminal server port or an OpenVMS system itself 4           can be configured to answer dial-in calls.             Follow these steps:   E           1. Configure the appropriate settings for the terminal portyA              to which you will connect. Begin a dialog of dialingiB              (or answering) commands with your modem. The specificB              required commands depend on the type of modem you are              using.r  E              Example 1: The following command prevents the modem from_B              hanging up when you exit the SET HOST /DTE session to$              bring up the SLIP line:  <              $ SET TERMINAL TTA2 /PERMANENT /MODEM /NOHANGUP  C              Example 2: This command disables interactive logins on.B              the line. Any SLIP data that arrives before you issue@              the SET INTERFACE command is ignored. Otherwise, itB              would trigger the creation of a new interactive login              process.h  8              $ SET TERMINAL TTA2 /PERMANENT /NOTYPEAHEAD  @              Example 3: To allow interactive logins after a user/              sends a Break, issue this command:e  F              $ SET TERMINAL TTA2 /PERMANENT /NOAUTOBAUD /SECURE_SERVER  C           2. Configure the modem. Issue the appropriate commands to <              dial the telephone and establish communication.  &     1-16 New Features and Enhancements n  t              F               3. Unless you are setting up a SLIP line between two UCXD                  hosts and plan to use the /FLOWCONTROL qualifier atE                  both ends, disable modem recognition of XON and XOFFSD                  characters. (If SLIP packets have CTRL/S and CTRL/QF                  characters embedded in them as data, you must prevent:                  the modem from trying to interpret them.)  I                  Either use hardware flow control or disable flow controliB                  entirely. The following examples disable all flow                  control.0  H                  Example 1: With a DECmodem V32 in AT command mode, set:  ;                     AT%F0 - No speed buffering flow control >                     AT%M0 - Disable speed buffering (optional)  B                  Example 2: With a DECmodem V32 in DCML mode, set:  C                     SET P2/SBU and SET P1/SBU - Then answer promptsI  E                  Example 3: With a U.S.Robotics Sportster modem, set:   H                     AT&B0 - Variable, follows connection rate (optional)1                     AT&H0 - Flow control disabled :                     AT&I0 - Software flow control disabled  C               4. Decide on the IP address. Follow these guidelines:m  E                  -  When you select IP addresses, it is often helpful F                     to place each physical link in a separate network,C                     or subnet. Just as each Ethernet or FDDI LAN is B                     typically assigned one subnet number, assign a6                     separate subnet to each SLIP line.  I                     The interfaces at the two ends of the line would botht1                     be in that particular subnet.S  I                  -  If it is advantageous for you to assign to the remotecH                     host an address in the same subnet as your site LAN,D                     use the proxy ARP feature (see Section 1.5.5.4).  -               5. Dial in. Follow these steps:   4                  a. Issue the SET HOST /DTE command:  1                     $ SET HOST /DTE terminal_namee                    b. Type:a  )                     ATDT telephone_number   I                                       New Features and Enhancements  1-17e l  n              =              c. The connected system displays its interactive ?                 (command mode) prompt. You are "talking" to theh@                 terminal server and can now make the connection.  D           Example: This example shows a user named SLIP-USER, at her@           PC named ROBIN and her 9600-baud modem, using terminal?           device TTA2 and connecting it to the port of terminale"           server. In this example:  D           o  The terminal server is a DECserver 700 terminal server.  4           o  It dials the telephone number 222-2222.  ?           o  The "password" prompt of the terminal server is #.   4           o  Its current log-in password is hootowl.  "           o  Its prompt is Local>.  /           o  The user's user name is SLIP-USER.n             $ SET HOST /DTE TTA2  /           %REM-I-TOQUIT, connection establishedL7           Press Ctrl/\ to quit, Ctrl/@ for command mode              ATDT 2222222             CONNECT 9600              # hootowl (not echoed)  -           Network Access SW V1.5 for DS700-16tQ           (c) Copyright 1994, Digital Equipment Corporation - All Rights Reserved 1           Please type HELP if you need assistancen  #           Enter username> SLIP-USER              Local> CONNECT SLIPe           Ctrl/\  ;     1.5.5.3 Setting Up SLIP: UCX As a Dial-up SLIP Provider   D           You can configure a UCX host to answer calls and establishE           remotely initiated SLIP connections. To set up this kind of            connection:a  "           1. Log in to the system.  <           2. Issue an appropriate UCX SET INTERFACE command.  2              Specify the /SERIAL_DEVICE qualifier.  &     1-18 New Features and Enhancements o  y              E                  Example: This command creates a SLIP interface namedxC                  SL5, using the terminal device associated with theo5                  session where the command is issued.c  L                  UCX> SET INTERFACE SL5 /HOST=192.208.35.5 /SERIAL_DEVICE=TT                 3. Log out  G               As soon as you log out, UCX takes over your terminal portiH               as a SLIP interface. Without causing the modem to hang up,.               start SLIP on the remote system.  D               To facilitate connection setup for end-users, create aE               dedicated user name for each remote host that dials in.iE               These users need have a LOGIN.COM procedure that issues F               appropriate SET TERMINAL and UCX SET INTERFACE commands,B               terminating with a LOGOUT command. Every user shouldC               specify a different SLIP interface name and host nameiE               (or IP address). These users require the OPER privilege ,               in order to create interfaces.  H               Optionally, enable IP forwarding on the SLIP provider host?               and start dynamic routing. As appropriate, issue:n  +               UCX> SET PROTOCOL IP /FORWARD   9               UCX> SET CONFIGURATION PROTOCOL IP /FORWARD   (               UCX> START ROUTING /SUPPLY  :               UCX> SET CONFIGURATION START ROUTING /SUPPLY  C               IP forwarding must be enabled if the host is expected F               to act as a gateway, forwarding packets between the SLIP7               interface and other available interfaces.-  F               Dynamic routing, with the /SUPPLY option, can be used toI               automatically send notifications on all connected LANs when H               new hosts or networks become reachable. For example, everyF               time a SLIP connection is set up to a new remote subnet,E               a corresponding route will be advertised using RIP (the ,               Routing Information Protocol).      I                                       New Features and Enhancements  1-19                    =     1.5.5.4 Setting Up a Host "Directly Connected" to the LAN   A           You can make a SLIP-connected host appear as if it were.A           directly connected to the LAN. This is possible using a D           proxy ARP server - usually the same host that is acting as&           a SLIP gateway into the LAN.  C           To use proxy ARP, assign to the remote host an IP address B           in the same subnet as the LAN. As other hosts on the LAN?           attempt to communicate with the remote host, the SLIP C           gateway answers ARP queries for the remote host by giving @           its own LAN address. The gateway then forwards packets           across the SLIP line.   >           Many of Digital's DECserver terminal server products>           support SLIP connections and implement proxy ARP. If>           you dial in from a UCX host to a terminal server, itA           automatically detects what IP address you are using and A           begins responding to ARP queries, forwarding packets as            necessary.  C           To use proxy ARP with a DECserver terminal server, assign B           an IP address in the same subnet as the terminal server.  C           On the terminal server, issue the SHOW PORT SLIP command.c           Verify that:  D           o  A particular IP address has not already been associated              with your port.  D           o  Header compression is available, if you plan to use it.  0     1.5.5.5 UCX As a SLIP Gateway with Proxy ARP  D           It is also possible to set up a host running UCX as a SLIPC           gateway with proxy ARP. You might prefer this approach ifLA           your dial-in modems are attached directly to an OpenVMSo3           system, rather than to a terminal server.o             Follow these steps:w  @           1. On the host to become a SLIP gateway, create a SLIPA              interface in another network or subnet, for example:   F              UCX> SET INTERFACE SL0 /HOST=10.1.2.3 /SERIAL_DEVICE=TTA2  C           2. On the host to become a SLIP gateway, add a host routeC0              for the remote system, for example:  3              UCX> SET ROUTE FINCH /GATEWAY=10.1.2.3n  &     1-20 New Features and Enhancements e  c              G               3. On the host to become a SLIP gateway, configure an ARP E                  entry for the remote host, listing your own EthernetCD                  address (as shown in UCX SHOW INTERFACE /FULL), for                  example:   =                  UCX> SET ARP 08-00-2B-2C-4F-46 FINCH /PUBLIC   G               4. On the host to become a SLIP gateway, enable IP packet 8                  forwarding, if not already done. Issue:  .                  UCX> SET PROTOCOL IP /FORWARD  H               5. On the remote host at the other end of the serial line,D                  create an interface. Specify an address in the same#                  subnet as the LAN._  E               Although the two ends of the SLIP line are in different:E               subnets, traffic can flow properly due to the interfacer9               route you added with the SET ROUTE command.             1.5.6 Shutting Down SLIP  A               To terminate a SLIP connection, follow these steps:   D               1. Return the associated terminal port to general use.                  Issue:e  /                  UCX> SET NOINTERFACE interfaced  @               2. If you added special route and proxy entries in=                  conjunction with the SLIP line, remove them.   H               3. If you changed any terminal settings in preparation forH                  SLIP, restore them. Issue the DCL SET TERMINAL command.           1.5.7 Troubleshootingi  @               To debug SLIP problems, use the following methods:  G               o  From another window, issue a TCPIPTRACE command to see 8                  packets going in and out of the system.  D               o  Watch the modem's Send and Receive data LEDs as youH                  attempt communication with the TELNET or PING commands.  G               o  Display a count of the packets being sent and received_I                  on the problem interface, in full-screen format, updated %                  every second. Issue:r  6                  UCX> SHOW INTERFACE SLn /CONTINUOUS=1  I                                       New Features and Enhancements  1-21o r                      1.6 TELNET  ?           The TELNET Service offers the following new software:   1           o  SHOW SESSION command (Section 1.6.1)   /           o  Command qualifiers (Section 1.6.2)   6           o  Error and status messages (Section 1.6.3)       1.6.1 SHOW SESSION Command  A           The SHOW SESSION command is now implemented. If you area           running TELNET with:  2           o  No connections, the command displays:  !              TELNET> SHOW SESSIONo3              %TELNET-E-NOSESSION, No active session   C           o  One session, the command displays information such as:   !              TELNET> SHOW SESSION G              Session 01, host ucxaxp, port 23  (default active session)   E           o  Multiple sessions, the command displays information such               as:  !              TELNET> SHOW SESSION -              Session 01, host ucxaxp, port 23 G              Session 02, host tnpubs, port 23  (default active session)        1.6.2 Command Qualifiers  @           The TELNET and TN3270 commands have the new qualifiers           shown in Table 1-2.                   &     1-22 New Features and Enhancements                   I               Table_1-2_TELNET_and_TN3270_Commands:_New_Qualifiers_______C  I               Qualifier_____Description__________________________________E  C               /NOINTERACTIVEOptional. Default: TELNET command mode._  A                             Disables the capability of the escapeAE                             character to leave the session and returndE                             you to the TELNET prompt (useful when the G                             TELNET or TN3270 commands are issued from arD                             command procedure in a captive account).  I               ___________________________________________________________   :               /LOG_         Optional. Default: no logging.               FILE=file B                             Logs the output of all sessions to theI                             specified file while maintaining the sessionseI               ______________on_your_terminal.____________________________l  '         1.6.3 Error and Status Messages   @               The following messages enhance the TELNET Service:  =               o  TELNET-S-NORMAL Normal successful completiona  '                  Successful connection.L  C               o  TELNET-E-CONNFAIL Failed to connect to remote hostc  G                  TELNET's attempt to connect to the remote host failed..  G               o  TELNET-E-CREATELOG Failed to create log file file_nameT  D                  You requested an output log file with the /LOG_FILEC                  qualifier, but TELNET's attempt to create the filen                  failed.  9               o  TELNET-I-ESCAPE Escape character is char   I                  This is the default or user-defined escape character fore                  your session.  -               o  TELNET-S-EXIT EXIT requested   <                  You entered the EXIT command. TELNET exits.  *               o  TELNET-I-INETCALL message  G                  Information about the interface call that triggered antG                  error. This message accompanies the TELNET-E-INETERROR                   message.   I                                       New Features and Enhancements  1-23f s                 8           o  TELNET-E-INETERROR Internet interface error  D              TELNET's attempt to issue an internet call failed. ThisD              message is usually accompanied by the TELNET-E-INETCALLD              message to show both the actual call that was attempted2              and the resulting status of the call.  9           o  TELNET-E-IVHOST Invalid or unknown host host   E              TELNET's attempt to resolve the specified host's address               failed.  3           o  TELNET-E-IVMODE Invalid mode specifiedo  C              You tried to set the mode to something other than CHAR.(              or LINE. This is not valid.  7           o  TELNET-S-LCLCLOSED Local connection closedd  C              You closed the TELNET connection by issuing either theh(              DISCONNECT or EXIT command.  4           o  TELNET-E-NOLICENSE License check failed  @              The DEC TCP/IP Services for OpenVMS license is: not-              present, not valid, or disabled.   1           o  TELNET-E-NOSESSION No active sessiony  C              You issued a command, which is valid during a session, B              but there is no current session or no sessions exist.  A           o  TELNET-E-NRESNOTAVAIL Network resource not availablen  E              TELNET tried to perform a network I/O, but there were not'              network buffers available.r  :           o  TELNET-E-OPENIN Failed to open file for input  >              Attempt to access the TELNET initialization file,@              SYS$LOGIN:TELNETINIT.INI, resulted in an error. The/              next messages indicate the reason.   6           o  TELNET-E-OPENQUOTA Too many sessions open  @              You tried to create more than the maximum number of/              allowed simultaneous sessions, 64.S  8           o  TELNET-S-REMCLOSED Remote connection closed  ;              An active connection was closed by the server.d  2           o  TELNET-S-RESUME Resume TELNET session  @              You issued a RESUME command to resume your session.  &     1-24 New Features and Enhancements w  t              E               o  TELNET-I-SESSION Session session_number, host, port_                   numberT  F                  The session number, host name, and port number of the9                  session whose status is being displayed.h  <               o  TELNET-E-TERMERROR Terminal interface error  8                  TELNET's attempt to issue a QIO failed.  0               o  TELNET-I-TERMFUNC function_name  H                  The function that was being attempted when an error wasF                  returned to a QIO. This message follows the TELNET-E-#                  TERMERROR message.k  0               o  TELNET-I-TRYING Trying ... host  ?                  Host to which a connection is being attempted.e  @               o  TELNET-W-UNSUPPORTED Qualifier qualifier is not$                  currently supported  >                  The qualifier you specified is not supported.  F                 ________________________ Note ________________________  F                 In OpenVMS Version 6.2, the /AUTHENTICATE qualifier ofE                 these DCL commands is not supported: SET HOST /TELNETp%                 and SET HOST /TN3270.   F                 ______________________________________________________           1.7 UCX$TRACE/  C               The UCX$TRACE Utility has the following new features:b  H               o  New DCL TCPIPTRACE command - Use this command to invoke                  the utility.   H               o  New options - Use the qualifiers listed in Table 1-3 to?                  customize tracing for your particular problem.e      I                                       New Features and Enhancements  1-25a e  s              E           Table_1-3_TCPIPTRACE_Command_Qualifiers____________________   E           Qualifier___________Function_______________________________N  5           /BUFFERS=n          Optional. Default: 100.u  >                               Number of buffers that UCX$TRACE>                               allocates for temporary storage.  C                               These buffers must be locked into the @                               working set, so the number can be:  D                               o  Decreased to be accommodated in the,                                  working set  B                               o  Raised to prevent the dropping of.                                  trace packets  E           ___________________________________________________________n  ?           /FULL               Optional. Default: brief display.p  =                               Displays the packet's contents.s  E           ___________________________________________________________c  @           /OUTPUT=file        Optional. Default: Screen display.  A                               Redirects the output from screen tonC                               the specified file. If this file namewD                               already exists, the output is appended$                               to it.  E           ___________________________________________________________r  4           /PACKETS=n          Optional. Default: 10.  A                               Stops the trace after the specifiedh=                               number of packets is displayed.h  E           ___________________________________________________________o  E                                              (continued on next page)s    &     1-26 New Features and Enhancements /                 I               Table_1-3_(Cont.)_TCPIPTRACE_Command_Qualifiers____________   I               Qualifier___________Function_______________________________   H                      [LOCAL   ]   Optional for port number. Default: all7               /PORT= [REMOTE  ]   traffic is displayed.                       [        ]   E               =n                  Required for port type. Filters thes  >                                   trace to the specified port.  I               ___________________________________________________________   B               /PROTOCOL=          Optional. Default: /PROTOCOL=IP.                 {ARP   }D               {ICMP  }            Filters on the specified protocol.               {IP    }               {TCP   }               {      }               {UDP   }  I               ___________________________________________________________                  Examples:   6               $ TCPIPTRACE HOST1 /FULL /PORT=REMOTE=21  @               $ TCPIPTRACE HOST2 /PORT=(LOCAL=23, REMOTE=1056) -;               _$ /FULL /PACKETS=30 /OUTPUT=TELNET_TRACE.TXTe                            I                                       New Features and Enhancements  1-27                          I                                                                         2 I         _________________________________________________________________   H                                           Installation and Configuration    C               This chapter plus the DEC TCP/IP Services for OpenVMS D               Installation and Configuration manual provide complete7               installation information for Version 3.3.r           2.1 Requirements  C               Check that your system meets all the requirements forn               installation.            2.1.1 Operating System  C               The DEC TCP/IP Services for OpenVMS (UCX) Version 3.3rG               software requires one of the following operating systems:   $               o  VMS VAX Version 5.5  /               o  OpenVMS VAX Version 6.1 or 6.2n  /               o  OpenVMS AXP Version 6.1 or 6.2            2.1.2 Licenses  9               To use UCX, you need one of these licenses:O  0               o  DEC TCP/IP Services for OpenVMS  .               o  DEC TCP/IP Client for OpenVMS  C               o  Digital NAS Client 150 Version 7.0 for OpenVMS VAXf                  Workstations   C               o  Digital NAS Client 150 Version 7.0 for OpenVMS APX                   Workstationsa  0               o  Digital NAS 150 to 250 Upgrades  C               DECwindows - You do not need a UCX license to displayd>               DECwindows applications on a remote TCP/IP host.  H               PATHWORKS - You do need a license for loading the software-               supplied for PATHWORKS systems.,  I                                       Installation and Configuration  2-1                         2.1.3 Information You Need  ?           For a smooth and fast installation and configuration, *           before you start the procedures:  &           o  Read these Release Notes.  B           o  Read the DEC TCP/IP Services for OpenVMS Installation&              and Configuration manual.  C           o  Complete the installation and configuration checklistss>              with the required information (see the DEC TCP/IP@              Services for OpenVMS Installation and Configuration              manual).t  !     2.2 Server Configuration Menuo  C           The Server Components Configuration Menu has been updatedtA           to add the Network Time Protocol (NTP) Service (for NTP (           information, see Section 1.3).  ?           Figure 2-1 shows a sample TCP/IP Services for OpenVMS /           SERVER Components Configuration Menu.l  E           ___________________________________________________________A                                        &     2-2 Installation and Configuration u  a              F               Figure 2-1 Example: SERVER Components Configuration Menu  V                       TCP/IP Services for OpenVMS SERVER Components Configuration Menu  ,                       Configuration options:  <                                1  -  BIND           Disabled<                                2  -  BOOTP          Disabled;                                3  -  TFTP           Enabledd;                                4  -  FTP            Enabledp;                                5  -  LPR/LPD        Enabledp;                                6  -  NFS            Enabledy;                                7  -  PC-NFS         Enabledg;                                8  -  PORTMAPPER     Enabledr;                                9  -  TELNET/RLOGIN  Enableda<                               10  -  SNMP           Disabled<                               11  -  NTP            Disabled  =                                A  -  Configure options 1 - 11 .                               [E] -  Exit menu  )               Enter configuration option:F                                              I                                       Installation and Configuration  2-3     f                E           ___________________________________________________________.                                                                                      &     2-4 Installation and Configuration u  a                       2.3 New Images  F               DEC TCP/IP Services for OpenVMS Version 3.3 includes the"               following new files:  /               o  SYS$COMMON:[SYSLIB]UCX$SDA.EXEX  7                  -  System Dump Analyzer (SDA) back end   A                  -  Debugs problems within the PATHWORKS Internet *                     Protocol (PWIP) Driver  /               o  SYS$COMMON:[SYSEXE]UCX$RCP.EXED                    -  RCP commandh  0               o  SYS$COMMON:[SYSEXE]UCX$NTPD.EXE  /                  -  Network Time Protocol (NTP)h  H                  -  Sends and receives network messages with the correct5                     time and adjusts the system clock   F               DEC TCP/IP Services for OpenVMS Version 3.3 also updates'               the following help files:d  &               o  UCX$TOPLEVEL_HELP.HLP  !               o  UCX$UCP_HELP.HLPn  $               o  UCX$TELNET_HELP.HLP  F               For a list of all the files in the distribution kit, see               Appendix A.            2.4 Reinstalling  ?               If your installation is an upgrade, or if you arenH               reinstalling an older version of the UCX product, complete"               the following steps.  7         2.4.1 Upgrading from UCX Version 3.0 or EarlierI  C               If you are upgrading from UCX Version 3.0 or earlier,rH               reconfigure all the currently configured server and client               components.   I                                       Installation and Configuration  2-5c s  i              )     2.4.2 Reverting to a Previous Versione  ?           If you decide to revert to an earlier version of UCX,t           follow these steps:o  C           1. Run the cleanup procedure, SYS$UPDATE:UCX$CLEANUP.COM,nB              which deletes most UCX data. UCX$CLEANUP deletes UCX-E              related executables, directories, accounts, identifiers, @              and save sets. However, it does not delete database              files.   /           2. Delete the Configuration Database, 6              SYS$COMMON:[SYSEXE]UCX$CONFIGURATION.DAT.             3. Shut down UCX.   3           4. Reinstall the version you want to use.n       2.4.3 RSH and REXECm  @           If you are upgrading from a previous release, move theB           Remote Shell and Remote Execute startup command files toC           their own directories on SYS$SYSDEVICE. Use the following            commands:   M           $ COPY SYS$MANAGER:UCX$REXECD_STARTUP.COM SYS$SYSDEVICE:[UCX$REXEC]   I           $ COPY SYS$MANAGER:UCX$RSHD_STARTUP.COM SYS$SYSDEVICE:[UCX$RSH]                                   &     2-6 Installation and Configuration E  S                    I                                                                         3 I         _________________________________________________________________   H                                                       Corrected Problems    I               The following problems in previous releases of the softwaree'               are fixed in Version 3.3:s  %               o  Kernel (Section 3.1)n  *               o  PWIP Driver (Section 3.2)  <               o  Sun RPC programming interface (Section 3.3)  9               o  Management control program (Section 3.4)a  *               o  BIND Server (Section 3.5)  1               o  Remote BOOT Server (Section 3.6)_  "               o  FTP (Section 3.7)  "               o  LPD (Section 3.8)  )               o  NFS Client (Section 3.9)   *               o  NFS Server (Section 3.10)  '               o  PC-NFSd (Section 3.11)t  *               o  Portmapper (Section 3.12)  #               o  RSH (Section 3.13)w  $               o  SMTP (Section 3.14)  &               o  TELNET (Section 3.15)        I                                                   Corrected Problems  3-1     _                   3.1 Kernel  !           These "bugs" are fixed:   "           o  Multiple open sockets  E              UCX now supports the select()  operation on more than 32t+              open sockets at the same time.   C           o  The IO$_SETMODE function of the $QIO[W] system service B              no longer causes access violations or system crashes.  A           o  INET device units are now correctly deleted on finalw              deassignment.  B           o  The parsing table for remote table allows an "ignore"              bit.   E           o  The configuration of communication security lists is nowi              supported.h  E           o  UCX now correctly searches the proxy cache when wildcardaB              proxies were involved. Dynamically loaded proxies nowD              correctly appear to be loaded, and non-wildcard proxiesD              are correctly found when similar wildcard proxies exist&              for different user names.  =           o  The SHOW COMMUNICATION /MEMORY command no longer 4              triggers a problem with corrupted pool.  ?           o  When two processes share a socket, only the actual D              creator could perform IO$_DEACCESS QIOs. UCX now checks              these items:t  (              -  Is the socket shareable?  B              -  Does the issuing process have the SHARE privilege?  @              -  Does the issuer's parent process own the device?  6              Access is denied only if all checks fail.  E           o  A problem with dynamic routing on OpenVMS AXP systems is               fixed.   ?           o  A problem with the execution of the SHOW INTERFACEL              command is fixed.  D           o  UCX correctly aborts FTP from remote multivendor hosts.  2           o  UCX now correctly deallocates a VCRP.       3-2 Corrected Problems d                 I               o  When starting a new server process, the Auxiliary ServeroH                  now uses the LOGINOUT.EXE image rather than the DCL.EXE                  image.   E               o  SELECT on a multiprocessor with null lists now works                   properly.           3.1.1 Security Driverh  4               o  The Security Driver works properly.  8               o  The Security Driver interface is fixed.            3.1.2 TELNET (TN) Driver  E               o  UCX processes correctly if a partner for a TN Driver 0                  connection becomes unreachable.  C               o  A problem due to a corrupted TIMER queue is fixed.t  E               o  When the TELNET Server receives both a DO ECHO and a-G                  WILL ECHO from the remote host, UCX now correctly setsi&                  the remote echo flag.  H               o  UCX now correctly limits the size of the subnegotiation                  buffer.  B               o  The problem with a TN Driver UCB overrun into the(                  following ORB is fixed.           3.1.3 UCX$TRACE Utility   G               o  The utility properly counts only the number of packetst                  displayed.i  H               o  To better distinguish between the end of one packet andH                  the start of the next, each each packet now starts with:                  3 blank lines and one line of dashes (-).  E               o  Processing is successful if the number of buffers isa                  one.   B               o  The formatting of the UDP destination port is now                  correct.   I                                                   Corrected Problems  3-3                         3.2 PWIP Drivert  !           These "bugs" are fixed:w  ;           o  PWIP shutdown and restart processes correctly.   =           o  Link error processing is now handled in a manner C              consistent with the Transport Provider Interface (TPI)n              Specification.   E           o  The PWIP Driver does not attempt to transmit if transmitL              is suspended.  A           o  The PWIP ACP log file name, PWIPACP_host.LOG, is nowe"              UCX$PWIPACP_host.LOG.  B           o  Records are now flushed to disk after every write. OnB              OpenVMS AXP systems, UCX correctly reads the PWIP ACP              log file.  >           o  Attempts to assign channels to BG devices are now              successful.  >           o  Sessions queued to the PWIP Driver work queue areE              properly removed before termination processing proceeds.t  B           o  The PWIP Driver startup and shutdown messages are now              posted to OPCOM.e  >           o  The PWIP Driver now dynamically recalculates MBUF@              resource and session limits when they are exceeded.C              This removes the need to reboot the system in order toe6              pick up UCX large buffer maximum changes.  D           o  The PWIP Driver now writes a message to OPCOM when MBUFE              resource and session limits are depleted or replenished.   1           o  Backlog enforcement works correctly.N  C           o  A problem with untimely disconnect requests because of 9              timing issues has been identified and fixed.a  E           o  For connect reject processing, the appropriate interfaceuA              state is no longer overwritten with an inappropriate @              state in routine d_discon_req in module PWIPDRIVER_              DOWN.C.  D           o  Changes have been made to the MBUF transmit throttle soE              that PWIP has sufficient available buffers, particularly 7              when a large number of sockets are active.        3-4 Corrected Problems T  E              G               o  UCX correctly defers the queuing of connections to the F                  ACP work queue if the connection is already queued to,                  the PWIP Driver work queue.                                                                                    I                                                   Corrected Problems  3-5o e  t              %     3.3 Sun RPC Programming Interfacea  !           These "bugs" are fixed:_  @           o  The definition and usage of the XDR_VECTOR()  addrp%              argument is now correct.s  >           o  CLNT_SPERRNO(),  CLNT_SPCREATE_ERROR(), and CLNT_@              SPERROR()  now include the VAX transfer vectors and               AXP symbol vectors.  "     3.4 Management Control Program  !           These "bugs" are fixed:   C           o  SET COMMUNICATION /INITIALIZE command - now in the UCX               startup procedure.e  @           o  15-character IP addresses - now resolved correctly.  B           o  UCX configuration procedure - no longer requires thatB              you specify your host's domain in order for you start              UCX.i  B           o  UCX startup procedure - no longer has problems with aB              local host name if either its canonical name or fully5              qualified name is a subset of the other._  E           o  Message Exchange (MX) lookups - no longer cause a memory               leak.  C           o  The network management commands in Table 3-1 have been               fixed.   E           Table_3-1_Corrected_Problems_with_Management_Commands______   E           Command_______________Fix__________________________________   D           SET NOBOOTP           If a host has duplicate IP addresses@                                 (2 records, 2 identical hardwareE                                 addresses, 2 different IP addresses),p;                                 the command now deletes ther3                                 appropriate record._  E           ___________________________________________________________O  E                                              (continued on next page)        3-6 Corrected Problems    t              B               Table 3-1 (Cont.) Corrected Problems with ManagementI               __________________Commands__________________________________  I               Command_______________Fix__________________________________   F               SET CONFIGURATION     No longer removes only the primaryF               NOBIND                BIND server from the Configuration-                                     Database.   I               ___________________________________________________________h  C               SET MX_RECORDS        In a host lookup, if UCX cannot D                                     find the host specified with theG                                     destination parameter, the software G                                     now correctly creates an MX record.   I               ___________________________________________________________l  D               SET NOMX_RECORDS      An unknown destination no longer8                                     results in an error.  I               ___________________________________________________________   G               SET NOMX_RECORDS *    Wildcarding no longer causes access /                                     violations.s  I               ___________________________________________________________e  G               SET NOMX_RECORDS *    The value of the /GATEWAY qualifierXG               /GATEWAY=gateway      is no longer treated as a wildcard.   I               ___________________________________________________________i  C               SET CONFIGURATION     When you specify multiple hosts E               NAME_SERVICE          as BIND servers, this command nowCH                                     properly maintains the order, as youA                                     enter it, of the server list.   I               ___________________________________________________________p  @               CONVERT/ULTRIX BIND   Can create a reverse domain.  I               ___________________________________________________________   H               SET CONFIGURATION     Properly supports /REMOTE=NOVIRTUAL.               COMMUNICATIONW  I               ___________________________________________________________i  I                                                  (continued on next page)   I                                                   Corrected Problems  3-7y s  t              >           Table 3-1 (Cont.) Corrected Problems with ManagementE           __________________Commands_________________________________n  E           Command_______________Fix__________________________________a  0           SHOW CONFIGURATION    Works correctly.           BIND /OUTPUT=file   E           ___________________________________________________________   A           SHOW ROUTE            Works correctly with alias names. E           /PERMANENT_________________________________________________d       3.5 BIND Serverc  A           These BIND Server problems are fixed in the Version 3.3            software:1  ?           o  The following VAX-only problem with the SHOW NAME_o?              SERVICE /QUERIES and SHOW NAME_SERVICE /STATISTICS_              commands is fixed.A  7           o  A problem with buffer flow has been fixed.i       3.6 Remote BOOT Server  C           BOOTP now provides optional vendor data for the boot fileg           size and gateways.                                       3-8 Corrected Problems o  e                       3.7 FTPf  %               These "bugs" are fixed:   H               o  The messages associated with the following FTP commands(                  now conform to RFC 959:  (                  o  mkd (make directory)  &                  o  pwd (show default)  C               o  The DIRECTORY /BRIEF command now produces the same E                  output as the UNIX ls command. The default is /FULL.e  I               o  Client and Server command-synchronization loss no longer                   occurs.  I               o  The mget command supports full path name specifications.n  G               o  Binary files with a size not in multiples of 512 bytes ;                  are now corrected transferred over DECnet.   F               o  The FTP command-line qualifiers /USER, /PASSWORD, and*                  /INPUT now work properly.  F               o  A remote PASV command no longer hangs up the session.  F               o  The PUT and GET commands used with the /FDL qualifier#                  now work properly.   D               o  More specific reply codes improve Client and Server!                  error reporting.   G               o  The GET command appropriately uses only the file name,i(                  not the full path name.  H               o  If VMS Plus mode is enabled, FTP properly does wildcard                  expansion.l  @               o  When you issue mget, FTP properly does wildcard                  expansion.m  C               o  Unless VMS Plus mode is enabled, OpenVMS-style GETiG                  transfers only one copy, and UNIX-style mget transfers &                  only multiple copies.  F               o  The GET command no longer strips device and directory?                  information from the local file specification.o  I               o  Users no longer get the number of bytes transferred evene+                  if none were due to error.s  I                                                   Corrected Problems  3-9. l  u              @           o  Writing to tape, FTP now satisfies tape driver size              requirements.  D           o  The GET, PUT, and DIRECTORY commands now work correctly1              if you specify the following syntax:o  4              node::node::device:[directory]file.type  B              If you copy a directory, it becomes unreadable on theD              target end. If access is denied, the returned error is:                 Failed to open file  D           o  FTP now correctly handles multidirectory linked logical              names.y  D           o  The PUT command processes correctly with an even number              of subdirectories.d  ;           o  A search list correctly releases all channels.   D           o  FTP now writes to nondirectory devices such as LTA: and              terminals.e  A           o  The PUT command to a concealed device with DIRECTORYa)              [000000] now works properly.w                                           3-10 Corrected ProblemsE X  E                       3.8 LPDd  C               These "bugs" are fixed and the following enhancementse               supplied.c  F                 ________________________ Note ________________________  8                 This section includes new documentation.  F                 ______________________________________________________  B               o  If mail notification is requested, LPD running in3                  UCX$LPD_QUEUE now works correctly.m  C               o  Outbound PRINT /PASSALL of a file with an embedded @                  carriage control no longer causes double-spacedE                  printing. (The most common cause of this problem was F                  the printing a non-stream LF file from an applicationG                  ending its text lines with <LFCR> rather than <CRLF>.)R  F                  If you have a problem with /PASSALL printing, you can3                  revert to the old behavior. Issue:   :                  $ DEFINE /SYSTEM UCX$LPD_STREAM_PASSALL 1  F                  However, if you have a problem with /PASSALL printingG                  that seems to be fixed by doing this, please report it                   to Digital.  @               o  All LPD Receiver diagnostics are now written toD                  UCX$LPD_RCV_STARTUP.LOG (UCX$LPD_RCV_LOGFILE.LOG is                  obsolete).   G               o  The LPD Server no longer loses jobs submitted in quickg.                  succession from UNIX clients.  @               o  LPD honors all OpenVMS FLAG PAGE print options,                  including:   <                  -  /FLAG qualifier of the DCL PRINT command  @                  -  /DEFAULT=FLAG setting on the LPD print queue  A                  -  /SEPARATE=FLAG setting on the LPD print queuen  I                  To turn on this behavior, define the system logical namepF                  UCX$LPD_VMS_FLAGPAGES. At queue start-up time, issue:  9                  $ DEFINE /SYSTEM UCX$LPD_VMS_FLAGPAGES 1n  <                  When you define UCX$LPD_VMS_FLAGPAGES, LPD:  I                                                  Corrected Problems  3-11  s  b              B              -  Honors what OpenVMS instructs regarding flag pages"                 for outbound jobs.  A              -  Submits inbound jobs with /FLAG or /NOFLAG, based D                 on the presence of the 'L' card in the control file."                 Inbound jobs with:  A                 .  An 'L' card - are submitted to the destinationt-                    print queue as PRINT/FLAG..  A                 .  No 'L' card - are submitted to the destination"/                    print queue as PRINT/NOFLAG.a  ?              -  Renders meaningless the DCL PRINT /PARAM=NOFLAGd                 command.  C              If you do not define this logical name, LPD behaves ass              it did before.o  @           o  The ROOT account no longer requires a communicationE              proxy in the Proxy Database regardless of the setting ofa(              the APPLICATION_PROXY flag.  E           o  If the SMTP transport is not installed, the LPD symbiontl4              correctly delivers a mail notification.  D           o  If jobs are pending in a stopped LPD queue, you can now,              successfully restart the queue.  ;           o  For outbound print jobs, LPD now has a "retry"               capability.  E           o  To identify a PostScript[TM] file, LPD now supports bothl4              the "o" card or the "Dpostscript" card.  @              Configuring LPD to use the LPD standard "o" card to>              indicate a PostScript file is useful for printing@              PostScript files over LPD to a system that does notA              implement the Digital LPD Printserver Extensions (PS               Extensions).c  @              You can configure this option for individual queuesC              with the new "ps" field in the Printcap File. Edit thedE              Printcap entries, adding a "ps" field, with one of these,              values:  D              -  "non_PS" - indicates that the remote system does not(                 implement PS Extensions.  B              -  "LPS" - Indicate that the remote system implements                 PS Extensions.       3-12 Corrected Problems                    F                  You can configure this option systemwide with the newI                  UCX$LPD_PS_EXT system logical name. The legal values foreI                  this logical are the same as for the 'ps' Printcap fieldeH                  - "non_PS" and "LPS." For each Printcap entry that doesF                  not have a 'ps' field defined, LPD uses the value youH                  assigned to the UCX$LPD_PS_EXT logical name. If you didH                  not define UCX$LPD_PS_EXT, LPD defaults to using the PS                  extensions.  F                  Configurations with no defined UCX$LPD_PS_EXT logicalG                  name and no "ps" fields in the Printcap file, continuelF                  to work exactly as they always have. No configuration>                  changes are required by this LPD enhancement.  9                  The legal values are not case sensitive.i  C               o  Adding printer entries to the Printcap Database no D                  longer causes the name of earlier entries to "bleedH                  over" into the names of later ones, if the earlier name.                  is longer than the later one.  C               o  The PRINT /PARAMETER=PRINTER="printer" command now H                  preserves the case of the name when you print to a UNIX                  system.  H               o  Issuing STOP /QUEUE /RESET for an LPD queue while a job8                  is processing no longer aborts the job.  C               o  With inbound jobs, if the remote host from the 'H'aG                  control card is unknown, LPD no longer inappropriatelyn2                  retains the job in UCX$LPD_QUEUE.  D                  If the remote host from the 'H' control card is notG                  known and the SET SERVICE LPD /FLAGS=APPLICATION_PROXYP                  is:  3                  -  Not set - the job goes through.s  .                  -  Set - UCX rejects the job.  G               o  When a remote LPD client sends the control file before D                  the data file, UCX no longer retains the job in theC                  UCX$LPD_QUEUE queue with a "file not found" error.   F               o  Outbound LPD jobs no longer fail with "File locked by                  another user."   I                                                  Corrected Problems  3-13  s                 B           o  LPD proxy mapping now finds proxies when you wildcard'              /REMOTE_USER, for example:   <              UCX> ADD PROXY /REMOTE_USER="*" /HOST=host.name  E           o  If SYS$SCRATCH is not defined in the system table and anhC              inbound print request with a mail notification requestwE              comes in, the UCX$LPD_QUEUE symbiont now works properly.e  .           o  If LPD has a problem with openingB              SYS$SPECIFIC:[UCX_LPD]UCX$LPD_RCV_LOGFILE.LOG and theE              logical name to turn on the diagnostics (LPD_RCV) is notxE              defined, LPD no longer sends diagnostics to the operatore              console.a  E           o  An inbound job completion OPCOM message is now generated 9              if the LPD service log option LOGOUT is set.W  D           o  The LPD_RCV and LPD_DEBUG logical names for diagnosticsE              are enhanced to track what the LPD Client sends compareda+              to what the Receiver receives.k  A              If you have used the old LPD diagnostics by defining E              the system logical names LPD_RCV and LPD_DEBUG to 65535, B              the new value to get the same effect is 7. Therefore,              replace:t  -              $ DEFINE /SYSTEM LPD_DEBUG 65535 +              $ DEFINE /SYSTEM LPD_RCV 65535                 with   )              $ DEFINE /SYSTEM LPD_DEBUG 7o'              $ DEFINE /SYSTEM LPD_RCV 7   B              LPD_DEBUG and LPD_RCV are bit-mapped values. The low-D              order three bits are used to give the effect previouslyE              produced by all the bits being set (old value of 65535).P  D              A new diagnostic is the fourth bit. If it is set (valueE              8), the LPD symbiont logs each buffer that it sends over C              the TCP/IP link, and the LPD Receiver logs each bufferxC              that it receives from the TCP/IP link. This provides ahE              way to see exactly what the LPD is sending (for outboundP4              jobs) and receiving (for inbound jobs).  =              To turn on just this new diagnostic and no other A              diagnostics, set the fourth bit of the LPD_DEBUG and 9              LPD_RCV logical names by defining them to 8.s       3-14 Corrected Problemsl l  s              D                  To get the old diagnostics along with this new one,E                  define LPD_DEBUG and LPD_RCV to 15 (recommended onlygH                  for the diagnosis of problems). Leaving the diagnosticsF                  on during normal use slows the performance of LPD andD                  produces large log files. LPD_DEBUG and LPD_RCV are                  independent:_  A                  LPD_      Applies to outbound jobs (LPD Client).f                  DEBUGI                            Writes diagnostics to an LPD queue's log file.e  @                  LPD_RCV   Applies to inbound jobs (LPD Server).  I                            Writes diagnostics to the Receiver's log file, 3                            UCX$LPD_RCV_LOGFILE.LOG.                                                             I                                                  Corrected Problems  3-15                         3.9 NFS Client  /           These Version 3.2 problems are fixed:e  A           o  When you issue the MOUNT command with a lowercase or_C              mixed case volume label, the quotation marks no longer_2              appear in the resulting volume label.  B           o  When you issue the MOUNT command and specify a volume>              label, MOUNT qualifiers, including /PROCESSOR and-              /FILEIDS, are no longer ignored.   1           o  The default ADFs now work correctly._       3.10 NFS Serverh  >           o  NFS now correctly accesses files with any form of%              variable length records.   A           o  If you configure ADD EXPORT /OPTIONS=PURGE_VERSIONS, E              the ls command to display NFS files now works correctly, @              even with the presence of a file with null name and)              extension, for example, .;1._  D           o  The file system works corrctly when the final record of)              a file crosses the EOF mark.   C           o  When you define the UCX$CFS_MODUS_OPERANDI mask 512 to_B              enable REAL_SIZE determination, write operations work              properly.       3.11 PC-NFSd  #           These problems are fixed:o  >           o  PC-NDSd no longer rejects logins to accounts with               "password expired."  ,           o  Authentication now logs errors.  A           o  When the client sends a fully qualified host name inaD              its RPC request to print, PC-NFSd correctly creates the              subdirectory.  =           o  When PC-NFSd renames a print file into the spool A              subdirectory, and a file by the same name is already A              queued up for printing, PC-NFSd now works correctly.d       3-16 Corrected Problems                             3.12 Portmapper   G               The Portmapper now correctly writes error messages to thep/               log file when registration fails.e           3.13 Remote Shell   '               These problems are fixed:_  D               o  The RSH command now properly maintains exit status.  <               o  RSH now executes properly on a nonterminal.                                                                  I                                                  Corrected Problems  3-17  e                 
     3.14 SMTP   C           The following "bugs" are fixed and enhancements supplied.   C              ________________________ Note ________________________   5              This section includes new documentation._  C              _______________________________________________________  A           o  You can now reply to mail forwarded with the OpenVMSI&              Mail SET FORWARD command.  D           o  SMTP now handles addresses that include a source route,D              which, upon receipt, appear on the VMS Mail From: line,              for example:_  9              <@PSUVM.PSU.EDU:owner-acm-l@UNIVVM.UNIV.EDU>h  E           o  SMTP now correctly truncates RFC 822 headers that exceede              1000 characters.g  A           o  Users no longer receive an error when trying to send B              a file with MAIL /NOEDIT and a DECnet address appears1              before an SMTP address, for example:n  =              To: SOMNOD::JANE, SMTP%"john@someplace.else.org"v  <           o  SMTP now delivers mail to an address with a dot;              in the local part of the address, for example:e&              To: G.Peach@xyz_corp.com.  ?           o  SMTP no longer looks at a local-part of an address D              within quotation marks. An example is a local-part withE              a percent (%) character all within quotation marks, sucht              as:  F              "PSI%abcdef.13911551526::somebody"@someplace.xyz_corp.com  D           o  SMTP handles messages even if the RFC header block has:  +              -  More than 100 lines of textC  $              -  More than 8192 bytes  E           o  SMTP correctly handles addresses with special charactersoB              inside a comment string, for example, " > " or " < ".  A           o  The SMTP VRFY and EXPN commands work properly. (Some D              systems do a VRFY on a user or an EXPN on a list before              sending mail.)/       3-18 Corrected Problems     /              I               o  SMTP now recognizes as "local" mail that is addressed to '                  the substitute domain.G  E                  (If you do not want it to recognize mail sent to therH                  substitute domain as "local," define the system logicalF                  name UCX$SMTP_NO_SUBS_DOMAIN_INBOUND before you start&                  the SMTP mail queue."                 o  Inbound mail   I                  -  When mail comes in from a non-SMTP user to a user who H                     has forwarded his mail via SMTP on the local system,F                     the VMSmail From: line no longer rejects the REPLY                     command.  G                     If the non-SMTP transport from which the mail comes F                     is DECnet, the From: line is no longer enclosed in$                     quotation marks.  G                     If the non-SMTP transport is MTS, the From: line isoG                     no longer enclosed in quotation marks and no longereF                     contains backslashes preceding the inner quotation3                     marks in the address. Examples:   1                     Old: From: "SOMNOD::SOMEBODY"   5                     Corrected: From: SOMNOD::SOMEBODYi                       Old:  D                     From: "MRGATE::\"MRGATE::SUMNOD::SENDING_USER\""                       Corrected:  @                     From: MRGATE::"MRGATE::SUMNOD::SENDING_USER"  A                  -  SMTP handles inbound print requests with maill*                     notification requests.  3                  -  SMTP sets the VMSmail CC: line.e  E                  -  If an X-VMS-To or X-VMS-Cc RFC header is present,iA                     SMTP puts the header in the VMSmail To: line.p  I                  -  If an X-VMS-To or X-VMS-Cc RFC header is not present, A                     SMTP puts the header in the VMSmail To: line.   C                     (If you do not want to put these headers in the H                     VMSmail To: and CC: lines, define the system logicalF                     name UCX$SMTP_INBOUND_NOXVMS before SMTP execution#                     queue startup.)e  I                                                  Corrected Problems  3-19  g  a              C              -  SMTP handles multiline replies to the HELO command.   E              -  SMTP handles forwarded incoming mail even if the SMTP ?                 configuration database relay option is not set._  =              -  When forwarding incoming mail, SMTP no longer B                 creates a new block of RFC headers, in addition toE                 putting the old headers inside of the text of the newR                 message.                                                                             3-20 Corrected Problemsi n  (                       3.15 TELNETe  4               The following TELNET "bugs" are fixed.  0         3.15.1 TELNET Print Symbiont (TELNETSYM)  I               The TELNET Print Symbiont (TELNETSYM) software is correcteda&               and enhanced as follows:  @               o  Each TELNETSYM queue has its own log file. (TheA                  UCX$TELNETSYM_LOGFILE logical name is obsolete.)   I               o  OPCOM messages sent by TELNETSYM now include the name of %                  the execution queue.   @               o  If you define UCX$TELNETSYM_SUPPRESS_FORMFEEDS,G                  TELNETSYM no longer prints over the last line of text.A  F               o  TELNETSYM now correctly puts out Form Feeds (<FF>) at%                  the end of each job.o  D               o  If you do not define the UCX$TELNETSYM_IDLE_TIMEOUTE                  logical name, TELNETSYM no longer truncates the last,(                  blocks of print output.  @               o  TELNETSYM sets its process names to UCX$TNSYM1,(                  UCX$TNSYM2, UCX$TNSYMn.  >               o  To configure printers that do not implement a>                  TELNET layer, use the new system logical nameI                  UCX$TELNETSYM_RAW_TCP. Before you start the TELNET printeH                  queue, follow these steps: define UCX$TELNETSYM_RAW_TCP                  to 1.  G               o  If you define the logical name UCX$TELNETSYM_LOG_KEEP, D                  TELNETSYM purges log files. (If the logical name isG                  not defined, no log purging occurs.) With purging, yousG                  can also use UCX$TELNETSYM_LOG_KEEP to set the maximumo-                  number of log files to keep.   F                  Example: This example enables purging after more than?                  three copies of the same log file are created:d  :                  $ DEFINE /SYSTEM UCX$TELNETSYM_LOG_KEEP 3  G               o  To set the number of execution queues that a TELNETSYM"I                  process can serve, define the new TELNETSYM logical namer2                  UCX$TELNETSYM_STREAMS as follows:  ;                  -  Define it to a number between 1 and 16.c  I                                                  Corrected Problems  3-21O c  n              ?              -  Defining it to 1 turns TELNETSYM into a single-rA                 threaded symbiont. Thus, a TELNETSYM crash bringsaD                 down only the one execution queue in which the crash                  occurred. Issue:  8                 $ DEFINE /SYSTEM UCX$TELNETSYM_STREAMS 1  E              -  Define it once. Do not define it differently for each &                 TELNETSYM print queue.  =              -  The value you enter for UCX$TELNETSYM_STREAMS @                 is passed to the PSM$PRINT system routine in the#                 "streams" argument."  A              -  If you do not define this logical name, TELNETSYMnD                 runs with the OpenVMS maximum of 16 execution queues%                 per symbiont process.e  ;           o  The following sequence of events now processese              correctly:E  A              1. A job is printed to a TELNETSYM queue, but a linkn@                 cannot be established to the printer because theB                 printer is not responding (the printer may be busy2                 with another job or out of paper).  =              2. You stop this queue with a STOP /QUEUE /RESETh                 command.  E              3. A TELNETSYM queue - either another queue or the firstaC                 one - is started, and the remote printer pointed to :                 by the queue that is started is available.  C           o  If the sequence described in the previous item occurs, @              and you issue a DELETE /ENTRY command, the queue no              longer hangs.       3.15.2 TELNET Client  #           These problems are fixed:   @           o  Socket options are correctly set against the socket'              after making a connection.   B           o  The OPEN and CONNECT commands properly accept 5-digit3              port numbers as one of the parameters.C  9           o  The SHOW SESSION command is now implemented.e       3-22 Corrected ProblemsC i  a              H               o  TELNET now returns an exit status. If you have multipleB                  sessions, the exit status is from either the last8                  session or the last command you issued.  +               o  The HELP command is fixed.   4               o  The PRINT-SCREEN function is fixed.  I               o  During a SPAWN commmand subprocess, non-privileged users <                  received OPER authorization. This is fixed.  G               o  TN3270 works properly with IBM-3278-4 model terminals.                                                                   I                                                  Corrected Problems  3-23e s  e                    I                                                                         4gI         _________________________________________________________________s  H                                                           Known Problems    G               This release of the DEC TCP/IP Services for OpenVMS (UCX)l1               product has the following problems:e  2               o  TELNET print symbiont (TELNETSYM)  >                  If you issue a DELETE /ENTRY command on a jobC                  while TELNETSYM is trying to establish a link to a:D                  nonresponding the printer, the print queue "hangs."*                  To reset the queue, type:  %                  $ STOP /QUEUE /RESETd                 o  SMTP   B                  -  SMTP does not set the RFC 822 "CC:" header for"                     outbound mail.  E                  -  SMTP does not work correctly when a user, sendingnB                     mail to multiple users, mixes local and remote<                     addresses. Use the following workaround.  @                     At the To: prompt, use the following syntax:                       $ MAIL                     MAIL> SEND0                     To: SMTP%"addr1,addr2,addr3"  I                     where each address is a fully qualified SMTP address.d  @                     Example: Mailing a copy of the same file to:  >                     o  Users gull and swan on the local system  ?                     o  User tern on remote host beach.ocean.comr  =                     o  User duck on remote host lake.tarn.eduV                       $ MAIL/                     MAIL> SEND EGG_HATCHING.TXT_P                     To: gull,swan,smtp%"tern@beach.ocean.com,duck@lake.tarn.edu"B                     Subj:      The Latest in High-Tech Egg Warming  I                                                       Known Problems  4-1L U  s              C                 To force use of SMTP for the local recipients, keep @                 the local recipients separate from the non-local5                 recipients. At the To: prompt, issue:   S                 To: SMTP%"gull,swan",smtp%"tern@beach.ocean.com,duck@lake.tarn.edu"o  <           o  NFS Client and Server - OpenVMS-to-OpenVMS mode  A              -  BACKUP/VERIFY - might issue spurious verificatione                 error messages.E  >              -  Remotely accessing CMS libraries via NFS - not                 recommended.  D              -  UCX's NFS Client with OpenVMS POSIX - not supported.  E                 You cannot MAP remote file systems for use by OpenVMSo8                 POSIX applications via UCX's NFS Client.             o  Installationp  D              The UCX$CLEANUP procedure states that there are no more@              questions. In actuality, there might two additional*              questions after this message.             o  FTP  @              -  The ENABLE PORT and DISABLE PORT commands do not                 work.r  C              -  Angle brackets (< >) are not supported in directory                  specifications.f  7              -  You cannot use exclamation points ( ! ) 5                 in strings or files pointed to by thet9                 logical names UCX$FTP_SERVER_ANNOUNCE andb*                 UCX$FTP_ANONYMOUS_WELCOME.                     4-2 Known Problems                         I                                                                         5nI         _________________________________________________________________r  H                                                             Restrictions    =               DEC TCP/IP Services for OpenVMS Version 3.3 hasf7               restrictions on the following components:i  4               o  NFS Client and Server (Section 5.1)  )               o  NFS Client (Section 5.2)t  8               o  UCX on VMScluster systems (Section 5.3)  *               o  BIND Server (Section 5.4)  2               o  Management commands (Section 5.5)  !         5.1 NFS Client and Server.  C               The NFS Client and Server software have the following                restrictions:   (               o  OpenVMS-to-OpenVMS mode  F                  These restrictions are either specific to OpenVMS-to-C                  OpenVMS mode or are more problematic in this mode:   !                  -  Write sharings  D                     The NFS server and client running in OpenVMS-to-H                     OpenVMS mode do not prevent opening files for sharedD                     write access. However, there is no provision forC                     synchronizing updates among multiple clients orfE                     between remote clients and local applications andaE                     users. If you have a file simultaneously open fordE                     write access by remote users on different OpenVMS H                     client nodes or by remote users and local users, you:                     risk corrupting the data in that file.  '                  -  Identification ACLse  I                                                         Restrictions  5-1h e  e              <                 The rights identifiers shown in ACLs are not:                 correctly converted to or from their ASCIIC                 equivalents. They may be displayed in their numeric B                 form, or may appear as the wrong ASCII identifier.C                 For this reason, the server ignores all attempts to %                 write or update ACLs.   &              -  OpenVMS BACKUP Utility  A                 You cannot use the /PHYSICAL or /IMAGE qualifiers B                 when backing up from or restoring to a remote NFS-#                 served file system.n  ?                 The /VERIFY qualifier might cause inappropriate ,                 verification error messages.  4              -  Running images with kernel mode code  E                 UCX does not support the running of an image residingeB                 on a remote NFS-served disk if that image includesC                 any code that runs in kernel mode. This restriction >                 does not apply to images that call kernel mode@                 routines in shared libraries residing locally on                  the client node.  <              -  Installing images, page files, or swap files  C                 It is not supported to specify an image, page file,a@                 or swap file that resides on a remote NFS-servedE                 disk as the target of any command of the VMSINSTAL or !                 SYSGEN utilities.              o  NFS Serverm  E              -  The NFS Server keeps access to open files by a remote >                 NFS client. The server closes opens files onlyA                 if they are not accessed by the client during the E                 INACTIVITY_TIMER interval. Local OpenVMS applications_A                 can access the files only after the server closesn                 them.d  @                 Reducing the INACTIVITY_TIMER interval increasesD                 the load on the server (more OPEN-CLOSE actions) butD                 also enables local applications to access files with                 shorter delays.   E              -  The NFS Server limits access to nonSTREAM_LF files too                 read-only.       5-2 Restrictions                            5.2 NFS Client  A               The NFS Client software differs somewhat from otheraC               implementations of this protocol. The main differencefC               is that, on an OpenVMS server, its disk's Master FileS4               Directory (MFD) is not world readable.  F               Both UNIX and OpenVMS NFS Clients can successfully mount(               the MFD (see Example 5-1).  I               ___________________________________________________________r  D               Example 5-1 Mounting from UNIX and OpenVMS NFS Clients  (                     From the NFS Server:  "                      UCX> SHOW MAP  7                                  Dynamic Filesystem Map5D                        Pathname                  Logical File System8                        /dkb100                   DKB100:  )                     From the UNIX Client:-  1                      # mount grackle:/dkb100 /mnt   ,                     From the OpenVMS Client:  I                      UCX> MOUNT DNFS1: /HOST="nfs_server" /PATH="/dkb100"   <                     The OpenVMS Client always reads the MFD.>                     However, if it is protected, the operation,                     fails (see Example 5-2).  I               ___________________________________________________________l                    I                                                         Restrictions  5-3( y  d                E           ___________________________________________________________c    C           Example 5-2 Viewing Directories from UNIX and OpenVMS NFSM                       Clients   %                 From the UNIX Client:                     # ls /mnt  8                 ... fails (by design) because the MFD is                 protected.  (                 From the OpenVMS Client:  #                  $ DIRECTORY DNFS1:   8                 ... fails (by design) because the MFD is                 protected.  %                 From the UNIX Client:                      # ls /mnt/mydir  <                 ...executes because the client does not read                 the MFD.  (                 From the OpenVMS Client:  *                  $ DIRECTORY DNFS1:[MYDIR]  ;                 ...also fails (unintentionally) because thel4                 OpenVMS client always reads the MFD.  >                 If the MFD of a disk you are mounting is read-=                 protected against the UIC to which the remoteY?                 OpenVMS clients are mapped ("destination UIC"), ?                 do not mount the MFD. Instead, mount the lower-G<                 level directories, which are readable by the                  destination UIC.  E           ___________________________________________________________b         5-4 Restrictions l                 %         5.3 UCX on VMScluster Systems   H               The UCX configuration procedure, UCX$CONFIG, creates node-E               specific data on a VMScluster in SYS$COMMON. UCX$CONFIG H               does not configure this data in SYS$SPECIFIC on a per node               basis.  I               Node-specific data is identified by the member's node name,oG               which is defined in SCSNODE in SYSGEN. If you change youri6               node name in SYSGEN, follow these steps:  6               1. Delete the node-specific information.  ,               2. Make the changes in SYSGEN.  0               3. Rerun the UCX$CONFIG procedure.  8               Avoid binding a socket to a cluster alias.  H               Because the cluster alias is distributed in time, a socketB               bound to it has periods during which it is not fullyD               active. A UDP socket may stop to receive data, while aD               TCP socket may stop both to transmit and receive data.  G               For receiving data destined to the cluster alias, use theo=               binding to the IP address 0 (UCX$C_INADDR_ANY).            5.4 BIND Servere  >               The BIND Server software has these restrictions:  G               o  You can configure only one primary BIND Server and one.8                  secondary server per VMScluster system.  @               o  The BIND Server does not correctly support wellE                  known services in the domain (WKS entries) in server                   databases.            5.5 Management CommandsE  F               The management commands have the following restrictions:  G               o  SET NOROUTE command - Partial wildcards are not valid,b                  for example:e  (                  UCX> SET NOROUTE route*  D               o  SET SERVICE command - When you modify parameters toE                  a service, disable and re-enable the service for the .                  modifications to take effect.  I                                                         Restrictions  5-5     I              D              Except for TELNET and Remote Login, the DISABLE SERVICEA              command disables the specified service, but does notpA              stop the current process, if one exists. To stop ando=              restart the current process, follow these steps:   D              1. Wait until the process exits or stop it with the DCL+                 STOP PROCESS /ID=n command.a  %              2. Issue ENABLE SERVICE.P                                                                             5-6 Restrictions E  M                    I                                                                         6YI         _________________________________________________________________n  H                                                            Documentation    ?               For information about the DEC TCP/IP Services for C               OpenVMS (UCX) Version 3.3 software, see the following                documentation:  )               o  Version 3.3 cover letter   *               o  Version 3.3 Release Notes  .               o  Version 3.2 documentation set  A                  This chapter updates and expands the Version 3.2u                  manuals.   G               (Documentation for the new Version 3.3 software comprises                Chapter 1.)S  !         6.1 Omitted Documentation   G               The following information is either missing from, or hard 2               to find in, the Version 3.2 manuals.  /         6.1.1 TELNET Print Symbiont (TELNETSYM)t  B               The TELNET print symbiont (TELNETSYM) is an OpenVMS-H               supplied print symbiont. It prints over TCP/IP to a deviceC               such as a terminal server that implements TELNET. Its G               function is similar to that of LATSYM for Digital's Locale,               Area Transport (LAT) software.  F               TELNETSYM is a true OpenVMS print symbiont that performsI               all print formatting. (This implementation differs from theIH               LPD Protocol, where the receiver of the print job does the                print formatting.)  D               For information about corrected and enhanced TELNETSYM0               features, see also Section 3.15.1.  I                                                        Documentation  6-1                    $     6.1.1.1 Setting Up a Print Queue  C           Set up a queue to use TELNETSYM just as you would for anye5           print queue, except for these requirements:s  ?           1. Specify the TELNETSYM image name in the /PROCESSORh              qualifier:   %              /PROCESSOR=UCX$TELNETSYMh  @           2. Specify the host and port number to which the queue9              sends the print data. Use the /ON qualifier:                 /ON="host:port"  @              Example: To set up a TELNETSYM queue named xyz_q to@              print to host printserver.xyz.com at TCP Port 4242,              issue:   ;              $ INITIALIZE /QUEUE /PROCESSOR=UCX$TELNETSYM -h4              _$ /ON="printserver.xyz.com:4242" xyz_q       6.1.1.2 Link Establishment  C           When a print job that has no link to the printer is giveni?           to TELNETSYM, the printer attempts to open a link. If A           a link is established successfully, printing starts. If C           not, TELNETSYM continues to try to establish a link untilOA           it is successful. The configurable period between link-m7           establishment-attempts is the retry interval.u       6.1.1.3 Link Shutdownv  D           You can configure TELNETSYM to release an open link in one           of two ways:  <           o  Configure the link to release after a period of-              inactivity, called idle timeout.e  E           o  Configure the link to release at the end of a print job.a  =           When multiple systems contend for the same printer,P@           configure TELENETSYM to release the link at the end of@           a job. This allows other systems to print quickly. The?           disadvantage is that this creates overhead because it 1           requires a new link for each print job.e  >           When there is little or no contention for a printer,?           configure TELNETSYM to release the link after an idle_@           timeout has elapsed. With this approach, the TELNETSYM?           waits for the configured idle time to elapse and then        6-2 Documentationo h  E              B               closes the link. This option works well within batch$               printing applications.  "         6.1.1.4 Output Byte Stream  B               The stream of bytes sent to the printer by TELNETSYMC               differs only slightly from the output of the standardnI               OpenVMS print symbiont. These differences can be controlledeG               with the following TELNETSYM configuration logical names:   I               o  TELNETSYM doubles any TELNET IAC characters found in therH                  byte stream unless UCX$TELNETSYM_RAW_TCP is defined forB                  the queue. The IAC character is a hexadecimal FF.  C               o  TELNETSYM sends the TELNET "do binary will binary".C                  options negotiation escape sequence before a printpA                  job that has been printed with /PASSALL, because ?                  /PASSALL print jobs may contain 8-bit data. If,@                  UCX$TELNETSYM_RAW_TCP is defined for the queue,F                  TELNETSYM does not send this sequence before printingE                  a /PASSALL job. The sequence is six bytes, which area                  symbolically:  3                  IAC, DO, BINARY, IAC, WILL, BINARY   )                  In hexadecimal, this is:t  "                  FF,FD,00,FF,FB,00  A               o  TELNETSYM generates a form feed before the first B                  job of a new print queue starts and at the end ofB                  every job. This is normal behavior for an OpenVMSB                  print symbiont. To suppress this behavior, define@                  UCX$TELNETSYM_SUPPRESS_FORMFEEDS for the queue.  (         6.1.1.5 Configuring Print Queues  A               You can customize TELNETSYM for each print queue by H               defining logical names before you start the queue. BecauseD               the logical names are translated once at queue startupF               time, they can be defined differently for each TELNETSYM               queue.  G               Some TELNETSYM configuration logical names are associated H               with a TELNETSYM configuration option that is either ON or'               OFF. If the logical name:t  .               o  Is defined, the option is ON.  3               o  Is not defined, the option is OFF.o  I                                                        Documentation  6-3s l  o              A           Define all the TELNETSYM configuration logical names as @           /SYSTEM. The following sections describe the TELNETSYM&           configuration logical names.  <           6.1.1.5.1 Stream of Print Bytes Sent Over the Link  .           o  UCX$TELNETSYM_RAW_TCP (ON or OFF)  D              Suppresses all "TELNET" type modifications of the print>              output stream. This is for cases where the remoteB              printer/terminal server does not implement the TELNET@              Protocol and, instead, expects the raw data stream.  E              Stops TELNETSYM from doubling IAC characters and sending-C              the TELNET escape sequence to negotiate binary options (              for files printed /PASSALL.  9           o  UCX$TELNETSYM_SUPPRESS_FORMFEEDS (ON or OFF)_  B              Suppresses form feeds between jobs. This includes theB              form feed that is normally sent before the very firstC              job printed to a print queue and the form feed sent atw"              the end of every job.  '           6.1.1.5.2 Diagnostics Logging   .           o  UCX$TELNETSYM_VERBOSE (ON or OFF)  B              Turns on or off the logging of TELNETSYM diagnostics,E              for example, messages that indicate when links have comeo1              up or gone down, and error messages.   /           o  UCX$TELNETSYM_NO_OPCOM (ON or OFF)h  D              Turns on or off the sending of messages to the operator              console.               o  UCX$TELNETSYM_DEBUG  @              Turns on or off TELNETSYM diagnostics to supplement#              UCX$TELNETSYM_VERBOSE.   C              Tells TELNETSYM which diagnostic message types to log.d  C              Specify a value, which is a bit-mapped longword, where D              each bit set in the value turns on a particular logging'              function. The options are:        6-4 Documentation  a                   3                  Bit 0     Tracks the flow of code.s  ?                            Example: such-n-such-routine enterede  ;                  Bit 1     Tracks the allocation of memory.e  8                            Example: about to call malloc=                            Example: just freed address 7F0000   G                  Bit 2     Logs the bytes sent and received over TCP/IPd                             link.  I                  To set a bit, assign the value to the logical name whose G                  binary equivalent would have the bit set. For example, H                  you can tell TELNETSYM to log everything that it writesC                  to, and receives from, the TCP/IP link by issuing:o  7                  $ DEFINE /SYSTEM UCX$TELNETSYM_DEBUG 4   B                  Decimal 4 is binary 100 with bit 2 set. Note thatG                  different combinations can be achieved by setting more F                  than one bit in the value. A value of 3, for example,H                  sets bits 0 and 1 and so causes logging of flow of code3                  and memory allocation diagnostics.R  H                  If UCX$TELNETSYM_DEBUG is undefined, TELNETSYM does not'                  log these diagnostics.g  D                  Bit 2 is useful in unassisted problem solving. BitsE                  0 and 1 are primarily for Digital use. However, with D                  knowledge of PSM$ symbionts, you might find all the                   options useful.  '               o  UCX$TELNETSYM_LOG_KEEPr  E                  Specify a value to set the number of copies of a lognD                  file that TELNETSYM stores before it starts purging                  them.  G                  If you do not define UCX$TELNETSYM_LOG_KEEP, TELNETSYMa                   does not purge.  &               o  UCX$TELNETSYM_SCRATCH  B                  Defines the directory for TELNETSYM to use as its#                  scratch directory.   I                                                        Documentation  6-5e y  r              E              TELNETSYM puts in this directory log files and temporary 5              files created by TELNETSYM relay queues.   E              -  If UCX$TELNETSYM_SCRATCH is not defined, the UCX$LPD_ (                 SPOOL directory is used.  0              -  If UCX$LPD_SPOOL is not defined,.                 SYS$SPECIFIC:[SYSEXE] is used.  6           6.1.1.5.3 Characteristics of the TCP/IP Link  D           The TELNETSYM configuration logical names in this categoryC           correspond directly to item list options for the UCX $QIO D           setmode function (for details, see the DEC TCP/IP Services=           for OpenVMS System Service and C Socket Programming            manual).  #           o  UCX$TELNETSYM_DROPTIMEf  E              TELNETSYM sets the UCX$C_TCP_DROP_IDLE $QIO setmode item E              to the value of UCX$TELNETSYM_DROPTIME if it is defined.r  0           o  UCX$TELNETSYM_KEEPALIVE (ON or OFF)  B              If you define UCX$TELNETSYM_KEEPALIVE, TELNETSYM sets5              the $QIO setmode UCX$C_KEEPALIVE option.F  $           o  UCX$TELNETSYM_PROBETIME  A              TELNETSYM sets the UCX$C_TCP_PROBE_IDLE $QIO setmode C              item to the value of UCX$TELNETSYM_PROBETIME, if it is               defined.N  !           o  UCX$TELNETSYM_SNDBUFX  D              TELNETSYM sets the UCX$C_SO_SNDBUF $QIO setmode item toA              the value of UCX$TELNETSYM_SNDBUF, if it is defined.m  @           Note that the value for drop time must be greater than?           the value for probe time. When you define only one ofu@           these TELNETSYM logicals, the value of the other comes@           from the UCX default value. To see this default, issue'           SHOW PROTOCOL TCP /PARAMETER.          6-6 Documentatione                   D               6.1.1.5.4 Establishment and Release of the TCP/IP Link  -               o  UCX$TELNETSYM_RETRY_INTERVAL_  E                  Defines the time for TELNETSYM to wait between link- B                  establishment retries when link establishment hasF                  failed. The value for this logical name is an OpenVMS                  delta time.  H                  If this logical name is not defined, TELNETSYM defaultsC                  to a wait period of three minutes between retries.   C                  Example: To define a retry interval of 30 seconds,                   issue:s  R                  $ DEFINE /SYSTEM UCX UCX$TELNETSYM_RETRY_INTERVAL "0 00:00:30.00"  +               o  UCX$TELNETSYM_IDLE_TIMEOUT.  A                  Defines the length of time after which TELNETSYM E                  terminates an inactive link. Specify a value that isd/                  an OpenVMS delta time. If you:e  @                  -  Define UCX$TELNETSYM_IDLE_TIMEOUT, TELNETSYMI                     disconnects the link only when a period of inactivity G                     on the link equal to the time specified has passed.n  G                  -  Do not define UCX$TELNETSYM_IDLE_TIMEOUT, TELNETSYMuI                     releases the link immediately after the completion oft#                     each print job.l  G                  Example: To define a link-idle-timeout of ten minutes,D                  issue:r  P                  $ DEFINE /SYSTEM UCX UCX$TELNETSYM_IDLE_TIMEOUT "0 00:10:00.00"                 6.1.1.5.5 Other_  &                  UCX$TELNETSYM_STREAMS  E                  Configures the number of execution queues handled by D                  each TELNETSYM process. Define this logical name as                  follows:n  ;                  o  Define it to a number between 1 and 16..  C                  o  Defining it to 1 turns TELNETSYM into a single-C&                     threaded symbiont.  I                  o  Define it once. Do not define it differently for each *                     TELNETSYM print queue.  I                                                        Documentation  6-7t :                      6.1.1.6 Relay Queues  D           You can redirect the output of TELNETSYM to another queue,@           rather than directly sending it to a remote printer. AD           queue with this setup is a "relay queue." Use relay queuesD           to funnel fully formatted output to an outbound LPD queue.D           LPD transfers jobs that are fully formatted on the sending           side by OpenVMS.  C           TELNETSYM saves the output stream to a temporary file andcC           then submits the file to the destination queue. TCP/IP isr           not used.   <           To set up a TELNETSYM relay queue, specify the /ON7           qualifier of the INITIALIZE/QUEUE command as:o             /ON="UCX$QUEUE:qname"              where:  D           qname is the name of the queue that you want the TELNETSYM            to send its output to.  C           Example: To set up a TELNETSYM relay queue named RELAYQ_4 :           to send output to the queue named LPD_Q4, issue:  6           $ INITIALIZE /QUEUE /ON="UCX$QUEUE:LPD_Q4" -<           _$ /PROCESS=UCX$TELNETSYM /DEVICE=PRINTER RELAYQ_4       6.1.1.7 Common Problems   >           Ensure that you have addressed the following issues:  E           o  The first use of UCX$TELNETSYM on systems formerly usingO.              the public domain TELNET symbiont  B              If you use the public domain TELNET symbiont and want>              to switch to the UCX TELNET symbiont, remember toB              change the value of /PROCESSOR on the TELNET symbiontC              queues, including any command procedures that start upc               the queues. Change:  !              /PROCESSOR=TELNETSYMa                to:  %              /PROCESSOR=UCX$TELNETSYM   1           o  Printing to Digital terminal serverso       6-8 Documentatione r  t              C                  When you print to a DECserver system, ensure that:t  G                  -  Input flow control for the port you are printing to .                     is set to DISABLED. Issue:  :                     $ CHANGE PORT port INPUT FLOW DISABLED  E                  -  The TELNET server for the terminal server port is (                     properly set. Issue:  (                     $ CHANGE PORT port -;                     _$ TELNET SERVER NEWLINE TO HOST <CRLF>   /               o  Print queue in "stalled" state   G                  When you print a job to a TELNETSYM queue, a link must E                  be established between the queue and the printer. If F                  there is high contention for the printer, it might beI                  busy, causing the first attempt at link-establishment tom                  fail.  B                  TELNETSYM continues to try to establish the link,H                  according to the retry interval logical. Until the linkE                  is established, the execution queue stalls. When theoE                  link comes up, the job prints. A "stalled" TELNETSYMn3                  queue is not necessarily an error.o  I                  If the queue stalls while printing a job, the printer is '                  probably out of paper.M  "               o  TELNETSYM logging  I                  Each TELNETSYM queue has a log file named UCX$TELNETSYM_ #                  qname.LOG. If you:T  F                  -  Define the logical name UCX$TELNETSYM_SCRATCH, theE                     log files are stored in the UCX$TELNETSYM_SCRATCHE                     directory.  I                  -  Do not define UCX$TELNETSYM_SCRATCH, the log files goi'                     into UCX$LPD_SPOOL.r  F                     If UCX$LPD_S POOL is not defined, the logs go into*                     SYS$SPECIFIC:[SYSEXE].                  o  Format problems  D                  To track down problems with wrong formatting on theD                  printed page (for example, "garbage" for a graphicsD                  file or unwanted blank pages), use Bit 2 of the theE                  TELNETSYM logical name UCX$TELNETSYM_DEBUG. Definingu  I                                                        Documentation  6-9a n                 C              UCX$TELNETSYM_DEBUG helps determine whether or not theYD              source of the problem is TELNETSYM. Follow these steps:  D              1. Define UCX$TELNETSYM_DEBUG to 4 in the system table.                 Issue:  6                 $ DEFINE /SYSTEM UCX$TELNETSYM_DEBUG 44                 $ STOP /QUEUE /RESET TELNETSYM_qname.                 $ START /QUEUE TELNETSYM_qname  ;              2. Print the job that does not print properly.   =              3. Look at the TELNETSYM log file for the queue.k  ?                 This file has messages that show you every byteeB                 sent over the link to the printer, such as control3                 characters and setup/reset modules.c  C                 If the raw TCP logical name is not defined, you seer8                 doubled IAC characters (hexadecimal FF).  B                 If you printed /PASSALL and the raw TCP logical isC                 not defined, the job starts with the TELNET options >                 negotiation sequence "do binary, will binary".  C              4. Identify the problem. Either fix it or report it toa                 Digital.  *              5. Start the TELNETSYM queue.  #           o  TELNETSYM buffer dumps   ?              TELNETSYM logs control characters and non-printing A              characters by preceding the hexadecimal value of thei?              byte with a backslash. For example, this sequence:r                Carriage Controlv              Form Feed              Carriage Control               Line Feed              TabA              the text "Use Your Screen Saver to Conserve Energy.",              Carriage Return              Line Feed                is logged as:  K              \0D\0C\0D\0A\09Use Your Screen Saver to Conserve Energy.\0D\0Ag  @              The "do binary will binary" sequence starting off a%              /PASSALL job appears as:e       6-10 Documentation    h              #                  \FF\FD\00\FF\FB\00            6.1.2 FTP Logical Names   H               To manage FTP, the software includes the following logical               names:  "               o  UCX$FTPD_SECURITY  H                  If you define UCX$FTPD_SECURITY systemwide, FTP promptsD                  for a password, even if there is not a user name to9                  match the one specified by the FTP user.h  #               o  UCX$FTP_NO_VERSION   D                  If you define UCX$FTP_NO_VERSION, FTP does not sendH                  file version numbers when you issue the mget and the ls0                  commands to a non-OpenVMS host.  F               o  UCX$FTP_ANONYMOUS_WELCOME and UCX$FTP_SERVER_ANNOUNCE  D                  You can define the welcome message and announcementI                  message by defining the logical name to be equivalent to ;                  a string or by storing the text in a file.   0                  -  Using an equivalence string:  E                     Enclose the message text in parentheses. Use this                      syntax:i  K                     $ DEFINE /SYSTEM /EXECUTIVE UCX$FTP_ANONYMOUS_WELCOME -                      _$ "text"                     -  In a file:  )                     Create the text file.r  G                     When you define the logical name, specify this filea*                     name. Use this syntax:  I                     $ DEFINE /SYSTEM /EXECUTIVE UCX$FTP_SERVER_ANNOUNCE - :                     _$ "@SYS$SYSDEVICE:[UCX$FTP]file_name"  '         6.1.3 BIND SERVER Error Message                   The error message:  -               No root nameservers for class 1   I                                                       Documentation  6-11h u  .              E           means that no root name servers were found because no cache D           data was available. Either the cache file is not installedE           on your host, or it has been deleted. Without these recordsnE           the UCX name server will be unable to resolve names outsideo$           of its authoritative data.  D           Check SYS$SPECIFIC:[UCX$BIND]NAMED.CA. Look for the record           using:             UCX SHOW CONFIG BIND  $           To add this record. Issue:  )           UCX> SET CONFIGURATION BIND /CAs  B           Example 6-1 shows a typical snapshot of a secondary BIND           Server.   E           ___________________________________________________________   =           Example 6-1 Typical SHOW CONFIGURATION BIND Display              Primary G             Domain:     0.0.127.IN-ADDR.ARPA          File: NAMED.LOCAL              Secondary"N             Domain:     UCX.LKG.DEC.COM               File: UCX_LKG_DEC_COM.DB$             Host:       16.20.208.53             SecondaryoU             Domain:     208.20.16.IN-ADDR.ARPA        File: 208_20_16_IN-ADDR_ARPA.DB.$             Host:       16.20.208.53             CachetD             Domain:     .                             File: NAMED.CA  E           ___________________________________________________________        6.1.4 Configuring SMTP  >           Part of configuring SMTP is using the SET MX_RECORDSA           command. Before you issue this command, ensure that youbC           understand how SMTP routes mail. Detailed examples are inh9           the description of the SHOW MX_RECORDS command.        6-12 Documentation c  o                       6.2 Known Errors  E               The UCX Version 3.2 documentation set has the following                problems.   A         6.2.1 "DEC TCP/IP Services for OpenVMS Management" Manual            6.2.1.1 Table 6-2   G               o  Incorrect:  The information about UCX$FTP_WINDSIZ says C                  to see Section 6.2 for information about setting a %                  default buffer size.S  -               o  Correct:  See Section 6.5.1.M           6.2.1.2 Section 6.6.4                  o  Incorrect:   F                 ________________________ Note ________________________  E                 The public directories are read-only, so GET commands 3                 work there and PUT commands do not.l  F                 ______________________________________________________  F                  There are limits on the number of files in the user'sC                  home directory. Also, the maximum transfer size isn                  restricted.  F               o  Correct:  Delete this information. Both directory andF                  file access are controlled by OpenVMS access methods.           6.2.1.3 Section 9.1.1   @               Organization of the Proxy Database - second bullet  C               o  Incorrect:  The system manager can define the Type F                  field of a Proxy Database entry with up to 3 letters:=                  O (outgoing), N (incoming), and D (dynamic).l  G               o  Correct:  The system manager can define the Type fieldiB                  of a Proxy Database entry with up to 2 letters: O-                  (outgoing) and N (incoming).   I                                                       Documentation  6-13e c  i                   6.2.1.4 Section 9.3   :           Adhere to the Rules for Accessing an NFS Client:  B           o  The third bullet states that if there is a one-to-oneC              correspondence between the OpenVMS account and the UID 7              /GID pair, the process chooses this entry.E  @           o  Incorrectly omitted was the statement that the hostB              names must match for the process to choose the entry.       6.2.1.5 Table 9-2p  =           Some items in the table refer to the previous page.d  D           o  Incorrect:  The second entry in the table instructs theC              system manager to map requests from UID 115 to OpenVMS               account USER2.u  B           o  Correct:  The system manager should map requests from.              UID 115 to OpenVMS account USER3.       6.2.1.6 Section 9.5.7o  -           MOUNT command, Examples, Example 2:              o  Incorrect:g  *              UCX> SHOW DEVICE DNFS3: /FULL             o  Correct:s  )              UCX> SHOW MOUNT DNFS3: /FULL   .           o  Incorrect:  Directory name DNFC3.  ,           o  Correct:  Directory name DNFS3.       6.2.1.7 Section 9.5.8.2   >           Creating a customized Attributes Data Files, Step 4:             o  Incorrect:l  &              $ COPY GAF.ADF SYS$SYSTEM             o  Correct:L  2              $ COPY GAF.ADF SYS$SYSTEM:UCX$GAF.ADF       6-14 Documentation e                 A         6.2.2 "DEC TCP/IP Services for OpenVMS Management Command[               Reference" Manual.  D               The DEC TCP/IP Services for OpenVMS Management Command=               Reference manual contains the following errors.d  <         6.2.2.1 NFS Server: MAP-Related Command Descriptions  I               MAP, NOMAP, SET CONFIGURATION MAP, SET CONFIGURATION NOMAP,y4               and GENERATE MAP command descriptions:  ?               o  Incorrect: The mapping (formerly BIND) commandSD                  descriptions fail to make clear the information forF                  temporarily mapping file systems and entering mappingG                  information into the permanent Configuration Database.S                 o  Correct:                     -  MAPd  C                     Created logical file systems are not permanent.                     -  NOMAP   F                     Temporarily unlinks existing logical file systems.  7                  -  SET CONFIGURATION MAP, GENERATE MAP   E                     Created logical file systems are entered into the_5                     permanent Configuration Database.o  +                  -  SET CONFIGURATION NOMAP   H                     Permanently unlinks existing logical file systems in/                     the Configuration Database.o  ,         6.2.2.2 CONVERT /ULTRIX HOST Command  5               Description of the dest_file parameter:e  4               o  Incorrect: The default file name is.                  SYS$COMMON:[SYSEXE]ETC.HOSTS.  C               o  Correct: The default file name is ETC.HOSTS in thet0                  directory with the BIND Server.  !         6.2.2.3 SET BOOTP Commandf  >               Description of the /SERVERS=type=host qualifier:  (               o  Incorrect: [NO]RESERVED  *               o  Correct: Omit this value.  I                                                       Documentation  6-15     I              "     6.2.2.4 SET MX_RECORDS Command  D           The description of the /PREFERENCE=n qualifier incorrectly@           states that /PREFERENCE is optional. The /PREFERENCE=n            qualifier is required.  2     6.2.2.5 SET CONFIGURATION NAME_SERVICE Command  C           /LOCAL qualifier - included by mistake. This qualifier is_           not supported.  4     6.2.2.6 SET CONFIGURATION NONAME_SERVICE Command             Mistakenly omitted.t       6.2.2.7 SET SERVICE Command   $           Command description - Note  ?           o  Incorrect:  SET NOSERVICE with neither a specifiedTA              service nor specified qualifiers deletes all entrieso              for all services.  -           o  Correct:  Delete this statement.   /           Description of the service parameter:E  @           o  Incorrect:  The system manager can specify up to 15              characters.  >           o  Correct:  The system manager can specify up to 10              characters.       6.2.2.8 MOUNT Commandn  ?           First bullet in the Notes in the command description:E  @           o  Incorrect:  If you MOUNT remote OpenVMS directoriesE              where the NFS Server is UCX, use the /NOADF qualifier on $              the MOUNT command line.  D           o  Correct:  If you MOUNT remote OpenVMS directories whereC              the NFS Server is UCX, use the /NOADF qualifier on the C              MOUNT command line unless you are using the VMS-to-VMSi!              Integration feature.i  B              The requirement for the /NOADF qualifier applies onlyE              if the remote UCX server is a version older than Version B              3.3 and cannot participate in OpenVMS-to-OpenVMS mode              operation.a       6-16 Documentation                         I                                                                         7,I         _________________________________________________________________   H                                                   Unsupported Components    B               The following software, included with the DEC TCP/IPD               Services for OpenVMS (UCX) Version 3.3 release, is not#               supported by Digital:e  6               o  Outbound TELNET devices (Section 7.1)  5               o  Remote File Copy (RCP) (Section 7.2)   6               o  Incoming RLOGIN proxies (Section 7.3)  G                 _______________________ Warning _______________________m  B                 For these unsupported components, Digital makes noC                 representations regarding their use or performance. C                 Digital accepts no responsibility for any expenses,E?                 losses, or action incurred or undertaken by any B                 party as a result of using of this software. In noE                 event shall Digital have any liability whatsoever forEC                 incidental and consequential damages as a result ofaD                 the performance, use, or operation of this software.  F                 ______________________________________________________                            I                                               Unsupported Components  7-1t t  h              +     7.1 Support for Outbound TELNET Devices   B           You can create a TELNET pseudo-device (virtual terminal)=           and connect it to a remote listener (port). Use thee#           following TELNET command:O  1           TELNET> CREATE_SESSION host port [unit]C             where:  3           host      Specifies the remote host name.   E           port      Specifies the listening port number at the remote                      end.  B           unit      Optional. A decimal number specifying the unit9                     number for the pseudo terminal (TNx).L  A                     The unit "0" is the default and has a specialL@                     meaning allowing the system to pick the nextD                     available unit. If the requested unit is alreadyB                     in use, the next available unit is chosen, andD                     the command completes successfully. In any case,D                     the user is notified of the unit number created.  %           TELNET> DELETE_SESSION unit              where:  E           unit        A decimal number specifying the the unit numbern$                       to be deleted.  B                       If the TN specified has been set via CREATE_>                       SESSION, it is disconnected and deleted.6                       Otherwise, an error is returned.       7.2 Remote File Copy (RCP)  A           Remote Copy (RCP command) copies files between interneto           hosts.               7-2 Unsupported Components E  T      H                                                                      RCP      I         _________________________________________________________________l           RCPM  H               Copies files between internet hosts. Issue the RCP command4               at the DCL prompt. You can copy files:  0               o  From a remote host to your host  0               o  From your host to a remote host  0               o  From one remote host to another  C               To use RCP, the Remote Shell Service must be enabled.o  9               You have two ways to set up proxy checking:   I               o  On the RCP command line, specify a remote user name and,n(                  optionally, a password.  3               o  Add proxies to the Proxy Database.a  @                  For remote UNIX hosts, add an entry in the host4                  equivalence file, /etc/hosts.equiv.  G               You can specify qualifiers in either OpenVMS-Style formateI               or UNIX-Style format, but do not mix both types on the sameT               command line.            DCL-Style Format  /               RCP  source_file destination_file            UNIX-Style FormatT  1               rcp  /source.file /destination.file            Parameters                 source_fileo               Required.   ?               Source host and file specification, in the format &               [user@]host:file, where:  B               o  user@ is the user name on the remote UNIX system.  H                  Needed only if the UNIX system has the name in its /etcC                  /hosts.equiv file or the UNIX user's .rhosts file.   B               o  host is the remote host, followed by a colon (:).  I                                               Unsupported Components  7-3h i  t           RCPs      >           o  file is the name of the file to copy. A file name@              without the full path specification defaults to the=              default (or home) directory. Table 7-1 shows the &              possible correct formats.  E           Table_7-1_RCP_Command:_Specifying_the_Source_File__________   E           Host______Possible_Formats_________________________________,             UNIXC           hosts     o  Absolute path name, such as /etc/user/hosts,   0                        followed by the file name  D                     o  Path name relative to your default directory,0                        followed by the file name  E           ___________________________________________________________              OpenVMSh=           hosts     o  Brackets ([ ]) (indicates your defaulti  <                        directory), followed by the file name  7                     o  Full file specification, such as B                        DKA0:[WILDLIFE.BIRDS.NORTHERN]BIG_BIRDS.TXT  E                        To specify a device name, type a colon (:) and B                        then the name. Enclose the entire parameter4                        within quotation marks (" ").  C                     o  A logical name, such as SYS$LOGIN:ROBIN.DAT,-4                        BIRDS$9:[AMERICAN]FINCHES.LIS  >                        To specify a logical name, type a colon@                        (:) and then the name. Enclose the entire>                        parameter within quotation marks (" ").  E           ___________________________________________________________s             destinationp           Required.e  C           Destination host and file specification information is of 8           the same form as the source parameter, except:  C              If the file specification is completely omitted or the D              file name portion of the file specification is omitted,C              the default file name used is the same as specified inXB              the source parameter, the directory being the default)              /home directory of the user.n       7-4 Unsupported Components b  e      H                                                                      RCP                 Qualifiers                 /LOG,               Optional. Default: no logging.  @               Logs the files copied to or from the local system.  '               /PRESERVE (OpenVMS-Style)                -p (UNIX-Style)T               Optional.   F               Preserves the file protection mode and modification date               during a copy.  (               /RECURSIVE (OpenVMS-Style)               -r (UNIX-Style)fE               Recursively copies each subtree rooted at the directory E               you specify in the UNIX file specification. For OpenVMS G               hosts, specify [dir...] (with three trailing ellipses) inr;               the filespec instead of using this qualifier.                  /USER=usernameG               User on the remote host. Use only if a proxy has not beenoF               added for this user on the remote host, or if the remoteD               host's host equivalence file does not contain an entryD               for this user. If necessary, truncate the user name toC               the required number of characters using the /TRUNCATEbH               qualifier below. Specifying "username@" with the source orH               destination parameter is the equivalent UNIX-style method.                  /PASSWORD=passwordD               Password on the destination system. Use with the /USER               qualifier.                 /TRUNCATE[=n]w/               Optional. Default: no truncation.   @               Truncates the user name to the specified number ofI               characters. If you omit n, the default is eight characters.i          I                                               Unsupported Components  7-5i    E           RCP              Examples  /           1. $ RCP /LOG unixhost:source_file []i  C              Copies a file from a remote UNIX system under its home >              directory to a local file of the same name in the@              current directory. The log information for the copy              is displayed.  5           2. $ RCP vmshost:source_file [dir]dest_filei  B              Copies a file from a remote VMS system under its homeA              directory to a local file of a different name in the !              specified directory.X  G           3. $ RCP /PRESERVE vmshost:[dir1]source_file ":dka300:[dir2]"b  <              Copies a file from a remote VMS system from the?              directory specified to the directory on the device @              system on the local system into the same file name.E              The copy preserves the source file's protection mode and               modification date.s  D              Use quotation marks (" ") for specifying the device and*              directory on the destination.  N           4. $ RCP /USER=user1 /PASS=pass1 ":SYS$LOGIN:source_file" unix_host:  A              Copies a file from your login directory of the localdA              system to a remote UNIX system into the user's login1E              directory. The user name and password on the UNIX system                are also specified.  D           5. $ rcp -r ":dka300:[source_dir...]" "unixhost:/usr/tmp/"  D              Copies all files under the local directory specified toE              a remote UNIX host's destination directory. If there are_C              subdirectories beneath the source directory specified,m?              all the files in them are copied as well, creating,?              subdirectories on the remote host, as appropriate. ?              Directory hierarchy on a UNIX host is preserved bya              default.l         7-6 Unsupported Components s  e      H                                                                      RCP        L               6. $ RCP /LOG /RECURSIVE [source_dir...] vmshost:[dest_dir...]  H                  Copies the complete local sub-directory tree specified,C                  to a remote VMS host's destination directory whileiD                  preserving the directory hierarchy and logging each                  file copy.o  I               7. $ RCP /LOG /RECURSIVE [source_dir...] vmshost:[dest_dir]   B                  Same as Example 6 except that the copy is done toD                  the destination directory itself without preservingA                  directory hierarchy (new sub-directories are not                   created).  9               8. $ RCP /USER=someone /PASSWORD=password -p9                 _$ /TRUNCATE=4 source_file host:dest_file   ?                  Copies the local file to a remote user's loginrH                  directory. Note the truncation of the remote user name.H                  A user name and password are necessary if proxy recordsB                  or host equivalence file entries are not present.  .               9. $ RCP host1:file1 host2:file2  G                  Copies a file from one remote host to another. AssumespC                  proxy records or host equivalence files are set ups;                  correctly for user executing this command.   K               10.$ RCP "user1@host1:sys$dir:file1" "user2@host2:/usr/user2",  F                  Copies a file from remote OpenVMS system host1 in theD                  directory pointed to by the logical name SYS$DIR toE                  remote UNIX system host2 in the specified directory.CI                  Different user names are used on the two remote systems..H                  Proxy records and host equivalence files must be set upE                  properly because the passwords are not being passed.   \               11.$ RCP /USER=username /PASSWORD=password host1:[dir]source_file "host2:/usr"  C                  Copies a file from an OpenVMS host to a UNIX host,eF                  following the directory specifications. The same userC                  name and password are used on both remote systems.     I                                               Unsupported Components  7-7v    -                   7.3 Incoming RLOGIN ProxiesA  B           UCX now supports incoming RLOGIN proxies. If you set theD           proxy flag for the RLOGIN Service, inbound requesters withE           valid proxies are automatically logged in, thus eliminating A           "Username:" and "Password:" prompting. (Users without ay*           valid proxy are still prompted.)  '           To set the proxy flag, issue:n  0           UCX> SET SERVICE RLOGIN /FLAGS=(PROXY)  A           To add a proxy for an incoming RLOGIN user to the Proxyi           Database, issue:  I           UCX> ADD PROXY user /HOST=host /REMOTE_USER=user [ /PERMANENT ]i  D           Example: This command adds to the Proxy Database the proxyA           REMOTE_UGLY_DUCKLING for incoming RLOGIN user cygnet ats           host swan.  /           UCX> ADD PROXY REMOTE_UGLY_DUCKLING - 6           _UCX> /REMOTE_USER="cygnet" /HOST="babyswan"                                                 7-8 Unsupported Components                         I                                                                         A I         _________________________________________________________________I  H                                                          Installed Files    I               The installation procedure installs the following software.            A.1 UCX Filesy  3               SYS$COMMON:[SYSEXE]UCX$SNMP_AGENT.EXEm1               SYS$COMMON:[SYSEXE]UCX$VERSIONS.EXEy,               SYS$COMMON:[SYSEXE]UCX$UCP.EXE-               SYS$COMMON:[SYSEXE]UCX$PING.EXEm0               SYS$COMMON:[SYSLIB]UCX$IPC_SHR.EXE6               SYS$COMMON:[SYSTEST.UCX]UCX$INET_IVP.EXE,               SYS$COMMON:[SYSMSG]UCX$MSG.EXE2               SYS$COMMON:[SYS$LDR]UCX$BGDRIVER.EXE;               SYS$COMMON:[SYS$LDR]UCX$INTERNET_SERVICES.EXEo>               SYS$COMMON:[SYS$LDR]UCX$INTERNET_SERVICES_V6.EXE4               SYS$COMMON:[SYS$LDR]UCX$INETDRIVER.EXE3               SYS$COMMON:[SYSLIB]UCX$ACCESS_SHR.EXEa0               SYS$COMMON:[SYSEXE]UCX$INETACP.EXE5               SYS$COMMON:[SYSEXE]UCX$INET_ROUTING.EXE D               SYS$COMMON:[SYSHLP.EXAMPLES.UCX]UCX$INTERNET_SERVICES_         SEC.EXEoG               SYS$COMMON:[SYSHLP.EXAMPLES.UCX]UCX$INTERNET_SERVICES_V6_e         SEC.EXEs  *               (moved from UCX$EXAMPLES:) -(         SYS$COMMON:[SYSEXE]UCX$TRACE.EXED               (new) - SYS$COMMON:[SYSHLP.EXAMPLES.UCX]UCX$TRACE_HAS_         MOVED.EXEr<               SYS$COMMON:[SYSHLP.EXAMPLES.UCX]TRACEROUTE.EXE  A               SYS$COMMON:[SYSHLP.EXAMPLES.UCX]BUILD_UCX_SECURITY_e            I                                                      Installed Files  A-1m n                      DRIVER.COMA           SYS$COMMON:[SYSHLP.EXAMPLES.UCX]UCX_SECURITY_DRIVER.MARo3           SYS$COMMON:[SYSMGR]UCX$BOOTP_SHUTDOWN.COMe2           SYS$COMMON:[SYSMGR]UCX$BOOTP_STARTUP.COM.           SYS$COMMON:[SYSMGR]UCX$CALLBACKS.COM,           SYS$COMMON:[SYSUPD]UCX$CLEANUP.COM+           SYS$COMMON:[SYSMGR]UCX$CONFIG.COM 2           SYS$COMMON:[SYSMGR]UCX$DNFS_SHUTDOWN.COM*           SYS$COMMON:[SYSMGR]UCX$FIXUP.COM.           SYS$COMMON:[SYSEXE]UCX$FTPSERVER.COM2           SYS$COMMON:[SYSMGR]UCX$FTPD_SHUTDOWN.COM1           SYS$COMMON:[SYSMGR]UCX$FTPD_STARTUP.COMX=           SYS$COMMON:[SYSHLP.EXAMPLES.UCX]UCX$IOCTL_ROUTINE.Cc(           SYS$COMMON:[SYSLIB]UCX$IPC.OLB*           SYS$COMMON:[SYSLIB]UCX$INETDEF.H,           SYS$COMMON:[SYSLIB]UCX$INETDEF.R32,           SYS$COMMON:[SYSLIB]UCX$INETDEF.MAR,           SYS$COMMON:[SYSLIB]UCX$INETDEF.PAS,           SYS$COMMON:[SYSLIB]UCX$INETDEF.FOR,           SYS$COMMON:[SYSLIB]UCX$INETDEF.PLI,           SYS$COMMON:[SYSLIB]UCX$INETDEF.ADA,           SYS$COMMON:[SYSLIB]UCX$INETDEF.BAS2           SYS$COMMON:[SYSMGR]UCX$INET_SHUTDOWN.COM1           SYS$COMMON:[SYSMGR]UCX$INET_STARTUP.COMu)           SYS$COMMON:[SYSTEST]UCX$IVP.COMt4           SYS$COMMON:[SYSMGR]UCX$LOAD_INETDRIVER.COM4           SYS$COMMON:[SYSMGR]UCX$LPD_RCV_STARTUP.COM1           SYS$COMMON:[SYSMGR]UCX$NFS_SHUTDOWN.COM 7           SYS$COMMON:[SYSMGR]UCX$NFS_SERVER_STARTUP.COM_3           SYS$COMMON:[SYSMGR]UCX$PORTM_SHUTDOWN.COMp2           SYS$COMMON:[SYSMGR]UCX$PORTM_STARTUP.COM-           SYS$COMMON:[SYSMGR]UCX$PRINTCAP.DAT 7           SYS$COMMON:[SYSMGR]UCX$REMOTE_TTY_STARTUP.COMe3           SYS$COMMON:[SYSMGR]UCX$REXECD_STARTUP.COM 1           SYS$COMMON:[SYSMGR]UCX$RSHD_STARTUP.COMl  9           (new) - SYS$COMMON:[SYSMGR]UCX$NTPD_STARTUP.COMl:           (new) - SYS$COMMON:[SYSMGR]UCX$NTPD_SHUTDOWN.COM                   A-2 Installed Filesa    u              :               SYS$COMMON:[SYSMGR]UCX$SMTP_RECV_STARTUP.COM6               SYS$COMMON:[SYSMGR]UCX$SMTP_SHUTDOWN.COM5               SYS$COMMON:[SYSMGR]UCX$SMTP_STARTUP.COM 6               SYS$COMMON:[SYSMGR]UCX$SNMP_SHUTDOWN.COM5               SYS$COMMON:[SYSMGR]UCX$SNMP_STARTUP.COM 2               SYS$COMMON:[SYSMGR]UCX$SNMPD_MIR.DAT1               SYS$COMMON:[SYSMGR]UCX$SHUTDOWN.COM 0               SYS$COMMON:[SYSMGR]UCX$STARTUP.COM6               SYS$COMMON:[SYSMGR]UCX$SERVICE_SETUP.COM0               SYS$COMMON:[SYSMGR]UCX$SYMBOLS.COM1               SYS$COMMON:[SYSMGR]UCX$REGISTER.COMoB               SYS$COMMON:[SYSHLP.EXAMPLES.UCX]UCX$TCP_CLIENT_IPC.CB               SYS$COMMON:[SYSHLP.EXAMPLES.UCX]UCX$TCP_CLIENT_QIO.CD               SYS$COMMON:[SYSHLP.EXAMPLES.UCX]UCX$TCP_CLIENT_QIO.MARB               SYS$COMMON:[SYSHLP.EXAMPLES.UCX]UCX$TCP_SERVER_IPC.CG               SYS$COMMON:[SYSHLP.EXAMPLES.UCX]UCX$TCP_SERVER_IPC_AUXS.CoB               SYS$COMMON:[SYSHLP.EXAMPLES.UCX]UCX$TCP_SERVER_QIO.CG               SYS$COMMON:[SYSHLP.EXAMPLES.UCX]UCX$TCP_SERVER_QIO_AUXS.CaD               SYS$COMMON:[SYSHLP.EXAMPLES.UCX]UCX$TCP_SERVER_QIO.MAR8               SYS$COMMON:[SYSMGR]UCX$TELNET_SHUTDOWN.COM6               SYS$COMMON:[SYSMGR]UCX$TFTP_SHUTDOWN.COM5               SYS$COMMON:[SYSMGR]UCX$TFTP_STARTUP.COM 1               SYS$COMMON:[SYSMGR]UCX$TIMEZONE.COM ;               SYS$COMMON:[SYSHLP.EXAMPLES.UCX]TN3270DEF.MAR 1               SYS$COMMON:[SYSHLP]UCX$UCP_HELP.HLBC4               SYS$COMMON:[SYSMGR]UCX$UCP_STARTUP.COMB               SYS$COMMON:[SYSHLP.EXAMPLES.UCX]UCX$UDP_CLIENT_IPC.CB               SYS$COMMON:[SYSHLP.EXAMPLES.UCX]UCX$UDP_CLIENT_QIO.CD               SYS$COMMON:[SYSHLP.EXAMPLES.UCX]UCX$UDP_CLIENT_QIO.MARB               SYS$COMMON:[SYSHLP.EXAMPLES.UCX]UCX$UDP_SERVER_IPC.CB               SYS$COMMON:[SYSHLP.EXAMPLES.UCX]UCX$UDP_SERVER_QIO.C5               SYS$COMMON:[SYSMGR]UCX$BIND_STARTUP.COM_6               SYS$COMMON:[SYSMGR]UCX$BIND_SHUTDOWN.COM7               SYS$COMMON:[SYSMGR]UCX$PCNFSD_STARTUP.COM 8               SYS$COMMON:[SYSMGR]UCX$PCNFSD_SHUTDOWN.COM:               SYS$COMMON:[SYSEXE]UCX$INTERNET_SERVICES.STB=               SYS$COMMON:[SYSEXE]UCX$INTERNET_SERVICES_V6.STBh>               SYS$COMMON:[SYSEXE]UCX$INTERNET_SERVICES_SEC.STBA               SYS$COMMON:[SYSEXE]UCX$INTERNET_SERVICES_V6_SEC.STB 0               SYS$COMMON:[SYSEXE]UCX$INETACP.STB5               SYS$COMMON:[SYSEXE]UCX$INET_ROUTING.STB 4               SYS$COMMON:[SYSEXE]UCX$NET_GLOBALS.STB      I                                                      Installed Files  A-3n t  i              ,           SYS$COMMON:[SYSLIB]UCX$CFS_SHR.EXE1           SYS$COMMON:[SYSEXE]UCX$DNFSMOUNT_V5.EXE 1           SYS$COMMON:[SYSEXE]UCX$DNFSMOUNT_V6.EXE-4           SYS$COMMON:[SYSEXE]UCX$DNFSDISMOUNT_V5.EXE4           SYS$COMMON:[SYSEXE]UCX$DNFSDISMOUNT_V6.EXE3           SYS$COMMON:[SYS$LDR]UCX$DNFSDRIVER_V5.EXE 3           SYS$COMMON:[SYS$LDR]UCX$DNFSDRIVER_V6.EXE//           SYS$COMMON:[SYSEXE]UCX$DNFSACP_V5.EXEe/           SYS$COMMON:[SYSEXE]UCX$DNFSACP_V6.EXEe+           SYS$COMMON:[SYSEXE]UCX$PCNFSD.EXEe/           SYS$COMMON:[SYSEXE]UCX$PORTMAPPER.EXEe/           SYS$COMMON:[SYSLIB]UCX$RPCXDR_SHR.EXE ,           SYS$COMMON:[SYSEXE]UCX$RPCINFO.EXE7           SYS$COMMON:[SYSTEST.UCX]UCX$RPCIVP_CLIENT.EXEe7           SYS$COMMON:[SYSTEST.UCX]UCX$RPCIVP_SERVER.EXEN/           SYS$COMMON:[SYSEXE]UCX$SERVER_NFS.EXE ,           SYS$COMMON:[SYSEXE]UCX$CONVERT.FDL,           SYS$COMMON:[SYSEXE]UCX$CONVERT.COM.           SYS$COMMON:[SYSHLP]UCX$VMS_FILES.DOC)           SYS$COMMON:[SYSLIB]UCX$RPCXDR.H (           SYS$COMMON:[SYSEXE]UCX$EXE.ADF(           SYS$COMMON:[SYSEXE]UCX$HLB.ADF(           SYS$COMMON:[SYSEXE]UCX$MLB.ADF(           SYS$COMMON:[SYSEXE]UCX$OBJ.ADF(           SYS$COMMON:[SYSEXE]UCX$OLB.ADF(           SYS$COMMON:[SYSEXE]UCX$STB.ADF(           SYS$COMMON:[SYSEXE]UCX$TLB.ADF*           SYS$COMMON:[SYSEXE]UCX$BOOTP.EXE(           SYS$COMMON:[SYSEXE]UCX$FTP.EXE)           SYS$COMMON:[SYSEXE]UCX$FTPC.EXEt)           SYS$COMMON:[SYSEXE]UCX$FTPD.EXEl,           SYS$COMMON:[SYSEXE]UCX$LPD_RCV.EXE,           SYS$COMMON:[SYSLIB]UCX$LPD_SHR.EXE,           SYS$COMMON:[SYSEXE]UCX$LPD_SMB.EXE)           SYS$COMMON:[SYSEXE]UCX$LPRM.EXE_-           SYS$COMMON:[SYSEXE]UCX$LPRSETUP.EXE (           SYS$COMMON:[SYSEXE]UCX$LPQ.EXE.           SYS$COMMON:[SYSEXE]UCX$TELNETSYM.EXE-           SYS$COMMON:[SYSEXE]UCX$NSLOOKUP.EXEe+           SYS$COMMON:[SYSEXE]UCX$RLOGIN.EXEa(           SYS$COMMON:[SYSEXE]UCX$RSH.EXE  0           (new) - SYS$COMMON:[SYSEXE]UCX$RCP.EXE1           (new) - SYS$COMMON:[SYSEXE]UCX$NTPD.EXEo       A-4 Installed Files     t              6               SYS$COMMON:[SYSLIB]UCX$SMTP_PARSESHR.EXE5               SYS$COMMON:[SYSLIB]UCX$SMTP_MAILSHR.EXEl6               SYS$COMMON:[SYSEXE]UCX$SMTP_RECEIVER.EXE6               SYS$COMMON:[SYSEXE]UCX$SMTP_SYMBIONT.EXE/               SYS$COMMON:[SYSEXE]UCX$TELNET.EXEn2               SYS$COMMON:[SYS$LDR]UCX$TNDRIVER.EXE-               SYS$COMMON:[SYSEXE]UCX$TFTP.EXEr1               SYS$COMMON:[SYSEXE]UCX$UUENCODE.EXE_1               SYS$COMMON:[SYSEXE]UCX$UUDECODE.EXEs4               SYS$COMMON:[SYSEXE]UCX$BIND_SERVER.EXE9               SYS$COMMON:[SYSEXE]UCX$BIND_SERVER_XFER.EXE 1               SYS$COMMON:[SYSHLP]UCX$FTP_HELP.HLBe4               SYS$COMMON:[SYSHLP]UCX$TELNET_HELP.HLB6               SYS$COMMON:[SYSHLP]UCX$NSLOOKUP_HELP.HLB/               SYS$COMMON:[SYSEXE]UCX$ENCODE.COM /               SYS$COMMON:[SYSEXE]UCX$DECODE.COMs  9               (new) - SYS$COMMON:[SYSEXE]UCX$TNDRIVER.STBo  1         A.2 Files Installed for PATHWORKS Systems   4               SYS$COMMON:[SYS$LDR]UCX$PWIPDRIVER.EXE0               SYS$COMMON:[SYSEXE]UCX$PWIPACP.EXE1               SYS$COMMON:[SYSEXE]UCX$PWIPSHUT.EXEe5               SYS$COMMON:[SYSMGR]UCX$PWIP_STARTUP.COMl6               SYS$COMMON:[SYSMGR]UCX$PWIP_SHUTDOWN.COM3               SYS$COMMON:[SYSEXE]UCX$PWIPDRIVER.STB 0               SYS$COMMON:[SYSEXE]UCX$PWIPSYM.STB  4               (new) - SYS$COMMON:[SYSLIB]UCX$SDA.EXE                              I                                                      Installed Files  A-5n