           H                     HP_DECnet-Plus_for_OpenVMS__________________________!                     Release Notes                          March 2010      E                     This manual describes installation notes for this F                     release, new features not discussed in the currentH                     documentation, corrections included in this release,@                     documentation errata, and operational notes.              E                     Revision/Update Information:  This revised manual G                                                   supersedes HP DECnet- B                                                   Plus for OpenVMSD                                                   Integrity servers-F                                                   Release Notes, V8.3-6                                                   1H1.  I                     Operating System:             OpenVMS Version 8.4 for C                                                   Integrity servers G                                                   OpenVMS Alpha Version 5                                                   8.4   D                     Software Version:             HP DECnet-Plus for9                                                   OpenVMS =                                                   Version 8.4                     +                     Hewlett-Packard Company )                     Palo Alto, California                    D            Copyright 2010 Hewlett-Packard Development Company, L.P.  ?           Confidential computer software. Valid license from HP >           required for possession, use, or copying. ConsistentC           with FAR 12.211 and 12.212, Commercial Computer Software, A           Computer Software Documentation, and Technical Data for D           Commercial Items are licensed to the U.S. Government under/           vendor's standard commercial license.   ?           The information contained herein is subject to change A           without notice. The only warranties for HP products and C           services are set forth in the express warranty statements A           accompanying such products and services. Nothing herein E           should be construed as constituting an additional warranty. E           HP shall not be liable for technical or editorial errors or %           omissions contained herein.   C           Intel and Itanium are trademarks or registered trademarks @           of Intel Corporation or its subsidiaries in the United%           States and other countries.   ;           UNIX is a registered trademark of The Open Group.                                  C   _________________________________________________________________   C                                                            Contents       C   Preface...................................................    vii      1  Installation   C         1.1   Features Not Supported in This Release........    1-1 C         1.2   License Requirements..........................    1-1 <         1.2.1     License Requirements for OpenVMS IntegrityC                   Servers...................................    1-1 8         1.2.2     License Requirements for OpenVMS AlphaC                   Systems...................................    1-2 C         1.3   OpenVMS Software Version Requirement..........    1-2 C         1.4   Other Software Version Requirements...........    1-3 C         1.5   Installing the New Release....................    1-3 9         1.6   AUTOGEN Errors During Installation (OpenVMS C               Alpha Only)...................................    1-4   "   2  New Features and Enhancements  C         2.1   Network Management............................    2-1 C         2.1.1     DECnet/IP Communication Through SSH.......    2-1 4         2.1.2     DECnet-Plus Support for Mixed CaseC                   Password..................................    2-4 C         2.1.3     NET$CONFIGURE Improvements................    2-5 C         2.1.4     NCL Updates...............................    2-5 7         2.1.4.1     Added information about Configuring 5                     the system to listen to DECnet/IP C                     connections.............................    2-6               C                                                                 iii                    E           2.1.5     NCL HELP Updates..........................    2-6 .           2.1.5.1     Added New Material aboutE                       Backtranslations and Towers.............    2-7 <           2.1.5.2     Added Information about Support for IPE                       Towers..................................    2-7 8           2.1.5.3     Added Help for register and modifyE                       decnet_register Commands................    2-7 >           2.1.5.4     Added Information about Flushing the CDIE                       Cache...................................    2-7 1           2.1.5.5     Modified Description of the 8                       Session Control Naming Search PathE                       Characteristic..........................    2-8 >           2.1.5.6     Directory System Agent (DSA) Entity HelpE                       Updated.................................    2-8 ;           2.1.5.7     Added DNS/BIND Namespace Examples for E                       LOOP Help...............................    2-8 >           2.1.5.8     Updated Help for FDDI Station Link EventE                       Reporting...............................    2-8 E           2.2   New Devices Supported by MOP..................    2-9 7           2.3   DECnet-Plus and DECnet Phase IV support E                 VLAN..........................................    2-9 E           2.4   Transport Improvements........................   2-10 E           2.5   Host-Based Routing Improvements...............   2-10 E           2.6   Session Control Improvements..................   2-11 E           2.7   Distributed Naming Service (DECdns)...........   2-12 6           2.7.1     DECdns Now Supports Dynamic DeviceE                     Recognition...............................   2-12 :           2.7.2     DECdns Now Supports DECnet over TCP/IPE                     Links.....................................   2-12 E           2.7.2.1     Protocol Towers.........................   2-13 =           2.7.3     decnet_register Now Supports IP Towers in E                     the DECdns Namespace......................   2-13 E           2.8   Distributed Time Service (DECdts).............   2-15 6           2.8.1     DECdts Now Supports Dynamic DeviceE                     Recognition...............................   2-16 :           2.8.2     DECdts Now Supports DECnet over TCP/IPE                     Links.....................................   2-16                      iv                   /         3  Corrections Included in this Release   I               3.1   DNS$ADVER.EXE.................................    3-1 I               3.2   DTSS Changes..................................    3-1 I               3.3   Network Management Changes....................    3-2 I               3.3.1     End System Routing........................    3-2 I               3.3.2     NET$CONFIGURE Command Procedure...........    3-3 I               3.3.3     NET$STARTUP Command Procedure.............    3-3 I               3.3.4     NCL$GLOBALSECTION.DAT.....................    3-3 I               3.4   OSAK Changes..................................    3-4 I               3.5   Session Control...............................    3-4 I               3.6   Transport Layer...............................    3-5   +         4  Documentation Errata and Addenda   I               4.1   Current Product Documentation.................    4-1 I               4.2   Documentation Update for Version 8.2..........    4-2 I               4.3   Network Management and NCL....................    4-7 I               4.3.1     Devices and OpenVMS Device Names..........    4-7 I               4.3.1.1     CSMA-CD Devices.........................    4-7 I               4.3.1.2     FDDI Devices............................   4-10 >               4.3.1.3     Synchronous Devices (OpenVMS VAX andI                           Alpha Only).............................   4-11 ;               4.3.1.4     Asynchronous Devices (OpenVMS VAX I                           Only)...................................   4-13 I               4.3.2     DTR/DTS...................................   4-13 I               4.4   OSAK Programming..............................   4-14 ?               4.4.1     called_aei Parameter on A-ASSOCIATE and I                         S-CONNECT Indication Events...............   4-14 I               4.4.2     ROSE Minimum Workspace Increased..........   4-14 I               4.4.3     Using OSAK with OSI over TCP/IP...........   4-14 >               4.4.4     New Status Code for osak_send_more andI                         spi_send_more Routines....................   4-15 I               4.4.5     New OSAK API Routine: osak_tc_no_sc() ....   4-15 I               4.4.6     Handling of Default Transport Templates...   4-16 I               4.4.7     Omitted Parameter Block Parameters........   4-17 9               4.5   File Transfer, Access, and Management I                     (FTAM)........................................   4-17 I               4.5.1     Possible Values for OSIF_FAILURE..........   4-17             I                                                                         v                         5  Operational Notes  E           5.1   Network Management............................    5-1 4           5.1.1     CTF Utility Now Requires ProcessE                     Privileges................................    5-1 :           5.1.2     Tuning to Support the Larger CML BYTLME                     Value.....................................    5-1 5           5.1.3     COLLECT Command and Addressing in E                     decnet_migrate Commands...................    5-3 E           5.1.4     Decimal Syntax DSPs Not Supported.........    5-3 E           5.2   Devices and Data Links........................    5-3 :           5.2.1     Receive Buffers Attribute on HDLC LINK=                     Entity Not Implemented (Integrity servers E                     and Alpha only)...........................    5-3 E           5.2.2     FDDI Large Packet Support.................    5-4 E           5.3   Transport Layer...............................    5-4 E           5.3.1     NSP Characteristics for X.25 PVCs.........    5-4 :           5.3.2     NSP Flow Control Policy and DECnis andE                     x25Gateway Routers........................    5-4 E           5.3.3     OSI Transport.............................    5-5 E           5.4   Session Control...............................    5-5 9           5.4.1     Transport Precedence in Predominantly E                     Phase IV Networks.........................    5-6 9           5.4.2     Session Control Back Translation Soft E                     Links.....................................    5-6 7           5.4.3     Restriction When Using Applications E                     Supported Using Cluster Aliases...........    5-6 E           5.5   Distributed Naming Service (DECdns)...........    5-7 >           5.5.1     Creating Clearinghouses When IP Address isE                     Zero Causes DNS Server Hang...............    5-7 E           5.5.2     Server Startup Delay......................    5-8 >           5.5.3     Delay in Node Name-to-Address Translations;                     When DECdns Is Using DECnet over TCP/IP E                     Connections...............................    5-8 8           5.5.4     Problem Creating Clearinghouse UsingE                     DECnet over TCP/IP Connections............    5-9 >           5.5.5     DNS$CONFIGURE Option 4 Does Not Display IPE                     Address...................................    5-9 9           5.5.6     Limitation on Size of Checkpoint File E                     Records...................................    5-9 E           5.5.7     PAGEDYN Resources: Clerks and Servers.....   5-10 ;           5.5.8     Error Message Generated by DECdns Clerk E                     During Startup............................   5-11 E           5.5.9     Miscellaneous DECdns Operational Notes....   5-11        vi                   I               5.6   Distributed Time Service (DECdts).............   5-12 @               5.6.1     Automatic Time Zone Changes on RebootingI                         Clusters..................................   5-12 I               5.7   OSAK Programming..............................   5-12 I               5.7.1     User Data Size Restriction for Tracing....   5-12 I               5.7.2     OSAK Version 1.1 No Longer Supplied.......   5-12 B               5.7.3     Migrating Applications from Version 2.0 toI                         Version 3.0 OSAK API Interface............   5-12 :               5.7.4     Misleading OSAK Error Message: SPMI                         Congestion at Connect Time................   5-13 I               5.8   DECnet Programming............................   5-14 I               5.8.1     64-Bit Virtual Address Restrictions.......   5-14 I               5.8.2     Backtranslation of IP Addresses...........   5-14 I               5.8.3     Applications Connection Requirement.......   5-14              Tables  :               4-1       Documentation Update/Release NotesI                         Cross-Reference...........................    4-3   I               4-2       CSMA-CD Devices...........................    4-7   I               4-3       FDDI Devices..............................   4-10   B               4-4       Synchronous Devices (OpenVMS VAX and AlphaI                         Only).....................................   4-11   I               4-5       Asynchronous Devices (OpenVMS VAX Only)...   4-13                                 I                                                                       vii                              I         _________________________________________________________________   I                                                                   Preface                    Intended Audience   H               This manual is intended for all HP DECnet-Plus for OpenVMSE               Version 8.4 software users. Read this manual before you ?               install, upgrade, or use DECnet-Plus for OpenVMS.            Structure of This Book  :               This manual contains the following chapters:  H               o  Chapter 1 contains installation notes for this release.  C               o  Chapter 2 describes new features not documented in F                  the DECnet-Plus Version 8.4/8.3-1H1/8.3/8.2-1/8.2/7.1#                  documentation set.   F               o  Chapter 3 lists corrections included in this release.  G               o  Chapter 4 contains documentation errata and additions.   I               o  Chapter 5 discusses operational notes, restrictions, and 9                  known problems with the current release.   B               This manual contains release notes introduced in theA               current release and notes from previous DECnet-Plus ;               versions that still apply to the new release.   G               For a list of additional documents available that support G               this version of the DECnet-Plus for OpenVMS software, see H               the DECnet-Plus for OpenVMS Introduction and User's Guide.    I                                                                       vii                         Reader's Comments   <           HP welcomes your comments on this manual or any of<           the DECnet-Plus documents. Please send comments to           openvmsdoc@hp.com   )     How To Order Additional Documentation   E           For information about how to order additional documentation D           and for online versions of most DECnet-Plus documentation,5           visit the following World Wide Web address:   +           http://www.hp.com/go/openvms/doc/        Conventions   :           The following conventions are used in this book.  E           ___________________________________________________________ E           Convention_______Meaning___________________________________   @           special type     Indicates a literal example of systemC                            output or user input. In text, indicates D                            command names, keywords, node names, fileD                            names, directories, utilities, and tools.  A                            You can abbreviate command keywords to A                            the smallest number of characters that ?                            OpenVMS, NCL, DECdns, DECdts and the @                            other utilities accept, usually three&                            characters.  A           UPPERCASE        Indicates keywords that you enter. You B                            can type the characters in uppercase or@                            lowercase. You can abbreviate command=                            keywords to the smallest number of @                            characters that OpenVMS, NCL, DECdns,A                            DECdts, or the other utilities accept, 4                            usually three characters.  @                            Uppercase also indicates the names of@                            files, directories, utilities, tools,@                            commands, parameters, and procedures.  0           italic type      Indicates a variable.  C           bold             Indicates a new term defined in the text 4                            or important information.       viii                 I               ___________________________________________________________ I               Convention_______Meaning___________________________________   G               <Return>         Indicates that you press the Return key.   G               <Ctrl/c>         Indicates that you press the Control key B                                while you press the key noted by c.  G               [YES]            Brackets indicate that the enclosed item D                                is a default value in an installation&                                prompt.  H               { }              In command format descriptions, indicatesA                                you must enter at least one listed '                                element.   I               $________________Represents_the_OpenVMS_DCL_system_prompt._                                                           I                                                                        ix                          I                                                                         1 I         _________________________________________________________________   I                                                              Installation     G               This chapter discusses installation information not found /               in the current documentation set.   2         1.1 Features Not Supported in This Release  I               X.25 synchronous data links are NOT supported by HP DECnet- G               Plus for OpenVMS Version 8.4 for OpenVMS Integrity server G               systems. They ARE supported by HP DECnet-Plus for OpenVMS 4               Version 8.3 for OpenVMS Alpha systems.            1.2 License Requirements  @         1.2.1 License Requirements for OpenVMS Integrity Servers  I               HP DECnet-Plus for OpenVMS Version 8.4 for Integrity server C               systems requires the Base Operating Environment (BOE) G               license. This license includes the basic function license E               (DVNETEND). If you intend to configure your system as a E               DNS server or use host-based routing, you must obtain a (               separate DVNETEXT license.  G                 _______________________ Warning _______________________   @                 If you install the software without the DVNETEXTA                 license and then attempt to configure your system A                 as a DNS server, the DNS server will fail and the @                 configuration utility (NET$CONFIGURE) will exit.  F                 ______________________________________________________              I                                                          Installation 1-1                 Installation     1.2 License Requirements    8     1.2.2 License Requirements for OpenVMS Alpha Systems  B           HP DECnet-Plus for OpenVMS Version 8.4 for Alpha systemsB           requires one of two licenses: the basic function licenseD           (DVNETEND) or the extended function license (DVNETEXT). IfB           you intend to configure your system as a DNS server, you(           must use the DVNETEXT license.  D              _______________________ Warning _______________________  =              If you install the software without the DVNETEXT >              license and then attempt to configure your system>              as a DNS server, the DNS server will fail and the=              configuration utility (NET$CONFIGURE) will exit.   C              ______________________________________________________   D              __ Warning for Installations over DECnet-Plus V7.3-1 __  C              When DECdns server support for Alpha systems was added A              to DECnet-Plus in Version 7.3-1, the DECdns software B              mistakenly verified the VAX extended function license>              (DVNETRTG) instead of the Alpha extended function4              license. This error has been corrected.  >              If you have a DECnet-Plus V7.3-1 system currently?              configured as a DECdns server, do not install this ?              software until you obtain and install the DVNETEXT B              license. If you fail to install the DVNETEXT license,/              your DECdns server will not start.   C              ______________________________________________________   ,     1.3 OpenVMS Software Version Requirement  <           HP DECnet-Plus for OpenVMS Version 8.4 for OpenVMS?           Integrity servers requires Version 8.4 of the OpenVMS @           Integrity servers operating system. HP DECnet-Plus forD           OpenVMS Version 8.4 for OpenVMS Alpha requires Version 8.40           of the OpenVMS Alpha operating system.  C              ________________________ Note ________________________   @              DECnet Phase IV and DECnet-Plus cannot be installed@              on the same system. They are mutually exclusive. If       1-2 Installation           I                                                              Installation I                                  1.3 OpenVMS Software Version Requirement     F                 either of the DECnet product is present on the system,B                 uninstall the product before installing the other.  F                 ______________________________________________________  /         1.4 Other Software Version Requirements   D               If your network includes X.25 connectivity, HP DECnet-B               Plus for OpenVMS Version 8.4 requires Version 2.0 ofF               the X.25 for OpenVMS product. See the HP DECnet-Plus forI               OpenVMS Installation and Configuration manual for important H               information about when to install this software during theA               DECnet-Plus installation and configuration process.   G                 ______________________ Important ______________________   @                 Version 2.0 of the X.25 for OpenVMS product doesD                 not support synchronous devices on OpenVMS IntegrityC                 server systems at this time. Therefore, synchronous C                 X.25 data links are not supported by HP DECnet-Plus C                 for OpenVMS Version 8.4 on OpenVMS Integrity server                  systems.  F                 ______________________________________________________  G               If your network includes TCP/IP connectivity and you plan I               to enable OSI over TCP/IP or DECnet over TCP/IP, HP DECnet- I               Plus for OpenVMS Version 8.4 requires the latest version of G               the HP TCP/IP Services supported by the Operating System.   &         1.5 Installing the New Release  I               Install this kit using the POLYCENTER Software Installation D               utility (PCSI) by logging into the SYSTEM account. TheD               following example is for the OpenVMS Integrity servers               platform.   C               Entering the following command at the DCL prompt (for F               OpenVMS Alpha systems, use DECnet_OSI instead of DECNET_               PLUS):  @               $ PRODUCT INSTALL DECNET_PLUS/SOURCE=file-location      I                                                          Installation 1-3                 Installation"     1.5 Installing the New Release    B           For the new software to take effect, you must reboot theA           system. If the system is a member of a VMS cluster, you )           must reboot the entire cluster.   C              ________________________ Note ________________________   :              This kit contains a correction to the CDI$SHR;              executable (see CDI$SHR.EXE in the Corrections B              section). To ensure that this correction takes effectA              on a previously configured system, use the following A              command to clear the CDI cache after you install the               kit:   C              $ MCR NCL FLUSH SESSION CONTROL NAMING CACHE ENTRY "*"   C              ______________________________________________________   ?     1.6 AUTOGEN Errors During Installation (OpenVMS Alpha Only)   B           The PCSI installation process now calls AUTOGEN near the?           end of the installation (with the parameters GETDATA, @           SETPARAMS, and CHECK_FEEDBACK). If AUTOGEN returns anyB           error indication, the PCSI installation process displays+           the following informational text:   9     %PCSI-I-PRCOUTPUT, output from subprocess follows ... 6     %AUTOGEN-W-REPORT, please read AUTOGEN warnings in!     SYS$SYSTEM:AGEN$PARAMS.REPORT   @           The AUTOGEN report may contain messages similar to the           following:  P     ** INFORMATIONAL ** - Removing CLU$PARAMS definition made by unknown product;         _UNKNOWN_$ADD_GBLPAGES = 55000    !Set by (unknown)   ;           This message is related to the fact that previous <           versions of DECnet-Plus were incorrectly using the<           NEWPARAMS.DAT/CLU$PARAMS.DAT method to pass systemA           parameter information to AUTOGEN. In previous versions, A           DECnet-Plus did not label its data in the NEWPARAMS.DAT @           file. The preceding message indicates that AUTOGEN has=           found an unlabeled system parameter in the existing ?           CLU$PARAMS.DAT file and is removing it. If the system =           parameter was set by DECnet-Plus, the newly-created B           NEWPARAMS.DAT file contains the current system parameterB           requirements and these will be automatically included in       1-4 Installation           I                                                              Installation I               1.6 AUTOGEN Errors During Installation (OpenVMS Alpha Only)     D               CLU$PARAMS.DAT. Therefore, you can safely ignore these               messages.                                                                                       I                                                          Installation 1-5                          I                                                                         2 I         _________________________________________________________________   I                                             New Features and Enhancements     F               This chapter describes new functionality or enhancementsB               provided by HP DECnet-Plus for OpenVMS. This sectionE               includes new functionality implemented in Versions 8.4, F               8.3-1H1, 8.3, 8.2-1, 8.2, 7.3-2, 7.3-1, 7.3, 7.2-1, 7.2,I               and 7.1 which was not documented in the Version 8.2/Version $               7.1 documentation set.           2.1 Network Management  E               This section describes new network management features.   1         2.1.1 DECnet/IP Communication Through SSH   H               The following improvement has been made to NET$DRIVER.EXE,G               NET$OSDRIVER.EXE, NET$SESSION_CONTROL.EXE, NET$TRANSPORT_ 1               OSI.EXE, and NET$TPCONS.EXE images:   B               This release of DECnet-Plus uses the port forwardingI               feature of Secure Shell (SSH). This enables you to transmit G               DECnet/IP data over a secure channel, thus providing data I               security. The DECnet transmitter side requires modification I               to support this feature; however the receiver side does not !               require any change.   @               This feature can be used Processwide or SystemwideB               by defining the logical with the /PROCESS or /SYSTEM               qualifiers.   I               A new process or systemwide logical, DECNET_IP_PORT_FORWARD I               is introduced to provide the SSH functionality. The logical E               value should be unique and the port must be unused. The B               logical value must be same as that of the local portE               used to establish the secure channel. After setting the F               processwide logical in a particular process context, allH               DECnet/IP connections initiated by this process is secure.  E               If the systemwide logical is defined, all the DECnet/IP >               connections initiated by this system is secured.  I                                         New Features and Enhancements 2-1            !     New Features and Enhancements      2.1 Network Management    E           Prerequisites: SSH client must be running on the local host <           and SSH server must be running on the remote host.  C              ________________________ Note ________________________   =              For SSH related queries and support, contact the )              TCP/IP SSH Engineering team.   C              ______________________________________________________   C           To enable the port forwarding feature of SSH, perform the            following steps:  C           1. To establish a secure channel between a client and the 6              server, execute the following SSH command  9              Host1$ SSH -"L"port:host:hostport remotehost                 Where:   -              -L is the local port forwarding.   E              port is the local port on the client (local) system. The 4              port value must be between 1 and 65535.  '              host is the server system.   +              hostport is the server's port.   B              remotehost is the remote system's IP address or name.  D              This command prompts you for the system password of the               remotehost (Host2).  C           2. Enter the system password and an output similar to the $              following is displayed:                system's password: '              Authentication successful. V              Welcome to HP OpenVMS Industry Standard 64 Operating System, Version V8.4  E           3. Define the processwide or systemwide logical, DECNET_IP_ D              PORT_FORWARD with the logical value. This logical value?              is same as that of the "Port" specified in Step 1.   C              ________________________ Note ________________________   9              In a particular process context, if both the A              processwide and systemwide logicals are defined, the 5              processwide logical gets the preference.   C              ______________________________________________________   %     2-2 New Features and Enhancements            I                                             New Features and Enhancements I                                                    2.1 Network Management     F               4. Execute the DECnet/IP commands such as directory, setG                  host, and copy from the terminal on Host1 on which the ?                  logical is defined using the following syntax:   #                  SET HOST LOCALHOST   G                  The localhost is used instead of the IP address. Using B                  localhost and port, an SSH channel is established=                  between the transmitter and receiver system.   B               5. Deassign the logical after completing the task by1                  executing the following command:   ?                  Host1$ DEASSIGN/PROCESS DECNET_IP_PORT_FORWARD                   OR >                  Host1$ DEASSIGN/SYSTEM DECNET_IP_PORT_FORWARD  F                  If the logical is not deassigned, all the connections                   still uses SSH.  G               Following is an example of how this implementation can be                used:   H               In this example, the following names and numbers are used:  L                  DECnet name: Host1                  IP Number: 18.138.72.14M                  DECnet name: Host2                  IP Number: 18.138.185.56   F               1. Set up a secure connection between local host (Host1)D                  and remote host Host 2 using the following command:  ?                  Host1$ssh "-L" 512:localhost:399 18.138.185.56 #                  system's password:   +                  Authentication successful.   2                   Welcome to OpenVMS (TM) on Host2                    Host2$   E                  Where: 18.138.185.56 is the system IP address of the E                  remotehost(Host2) to which you are transmitting data *                  using the local port 512.  H               2. From a different terminal on the local host with a userG                  login, a process or systemwide logical must be defined /                  to use the DECnet/IP over SSH:   A                  Host1$ DEFINE/PROCESS DECNET_IP_PORT_FORWARD 512                   OR @                  Host1$ DEFINE/SYSTEM DECNET_IP_PORT_FORWARD 512  I                                         New Features and Enhancements 2-3            !     New Features and Enhancements      2.1 Network Management                  Where;   C              512 is the logical value, which is same as that of the                "Port" specified in              Step 1.  E           3. Execute a DECnet/IP command, such as SET HOST or COPY or :              DIRECTORY from the local host to remote host:  R              Host1$ DIRECTORY localhost"system welcome123"::sys$sysdevice:[000000]  8              An output of the DIRECTORY command from the/              18.138.185.56 system is displayed.   C           4. After the communication is completed, you can deassign <              the logicals as follows, depending on whether a@              processwide or systemwide logical had been defined:  ;              Host1$ DEASSIGN/PROCESS DECNET_IP_PORT_FORWARD               OR :              Host1$ DEASSIGN/SYSTEM DECNET_IP_PORT_FORWARD  5     2.1.2 DECnet-Plus Support for Mixed Case Password   :           The following improvements have been made to the;           NET$OSVCM.EXE and NET$SESSION_CONTROL.EXE images:   E           o  OpenVMS version 7.3-2 and above allows you to use mixed- E              case and extended characters in passwords when PWDMIX is &              specified as login flags.  6              DECnet has two different methods for user=              authentication. This is controlled by the sysgen E              parameter, NET_CALLOUT. If this parameter is set to 255, E              then the verification and proxy lookups are performed in )              LOGINOUT rather than DECnet.   A              In earlier versions of DECnet, when DECnet performed C              the user verification there were restrictions on using B              mixed-case and extended characters in passwords. ThisD              version of DECnet supports mixed-case password for task:              to task communication and remote file access.      %     2-4 New Features and Enhancements            I                                             New Features and Enhancements I                                                    2.1 Network Management     (         2.1.3 NET$CONFIGURE Improvements  H               The following changes have been made to NET$CONFIGURE.COM:  D               o  This release adds support for listening to selectedD                  interfaces for incoming DECnet over IP connections.H                  DECnet-Plus, by default, would listen to inbound DECnetE                  over IP connections on all IP-configured interfaces. E                  With this new feature, you can select the interfaces @                  on which DECnet over IP listens to the incomingE                  connections. For example, if the system has five IP- E                  configured interfaces and you want DECnet over IP to E                  listen on only three interfaces, you can provide the D                  list of IP addresses for those required interfaces.  C                  To configure the system to listen to selective IP- G                  configured interfaces using the ADVANCED configuration                    of DECnet-Plus:  B                  o  Type "ALL" if all the connections are required                       or  @                  o  Type comma separated list of the required IP                     addresses ,                  for the following question:  D                  * Interface(s) for DECnet/OSI over TCP/IP ? [ALL] :  I                  Also, refer to Section 2.1.3.1 for the new NCL commands.   G               o  The NET$CONFIGURE.COM procedure now informs you of the G                  existence of the ISIS$CONFIGURE.COM procedure. You can D                  use this procedure to configure a routing node thatH                  uses the link state routing protocol. Previously, thereH                  was no support for configuring a routing node using theH                  link state routing protocol. For more information aboutD                  using the ISIS$CONFIGURE.COM procedure, see the newH                  appendix about configuring link state routing in the HPG                  DECnet-Plus for OpenVMS Installation and Configuration                   manual.           2.1.4 NCL Updates   ?               This section describes new features found in NCL.   I                                         New Features and Enhancements 2-5            !     New Features and Enhancements      2.1 Network Management    D     2.1.4.1 Added information about Configuring the system to listen$             to DECnet/IP connections  C           The following commands have been added to reflect the new 5           feature described in Section 2.1.2 for V8.3   @           $MC NCL SET OSI TRANSPORT RFC1006 LISTENER IPADDRESSES           {a.b.c.d, w.x.y.z}@           $MC NCL ADD OSI TRANSPORT RFC1006 LISTENER IPADDRESSES           {a.b.c.d, w.x.y.z}C           $MC NCL REMOVE OSI TRANSPORT RFC1006 LISTENER IPADDRESSES            {a.b.c.d, w.x.y.z}A           $MC NCL SHOW OSI TRANSPORT RFC1006 LISTENER IPADDRESSES   E           These commands will enable or disable DECnet-Plus to listen D           to inbound DECnet over IP connections on interfaces havingD           local node IP addresses specified. However, these commands@           do not support DECnet-Plus to listen to remote node IPA           addresses. This is applicable for both RFC 1006 and RFC            1859.   C              ________________________ Note ________________________   8              In this release, these commands are used toB              set/show/add/remove the OSI transport attributes on aC              local node only, but these commands cannot be used for               a remote node.   C              ______________________________________________________        2.1.5 NCL HELP Updates  >           Since Version 7.1, several changes have been made toB           NCL HELP. These changes represent new material about newC           functionality, new material about existing functionality, A           and corrections to existing material. The sections that A           follow describe help changes where some of the material E           discussed in the HELP updates is not present in the current 6           documentation set or in these Release Notes.            %     2-6 New Features and Enhancements            I                                             New Features and Enhancements I                                                    2.1 Network Management     D         2.1.5.1 Added New Material about Backtranslations and Towers  C               Added significant explanatory material about managing E               backtranslation softlink and tower maintenance entities :               to the help text for the following commands:  B               DELETE SESSION_CONTROL BACKTRANSLATION SOFTLINK SHOWF               SESSION_CONTROL BACKTRANSLATION SOFTLINK UPDATE SESSION_E               CONTROL BACKTRANSLATION SOFTLINK UPDATE SESSION_CONTROL                TOWER MAINTENANCE   D               For more information, see the help text (of particularE               interest is the help text for the two update commands).   =         2.1.5.2 Added Information about Support for IP Towers   H               Added a description of an IP tower to the NCL_Introduction8               -> Syntax -> Data_Types -> TowerSet topic.  B               Added IP examples to the help text for commands usedD               to manage session control backtranslation softlink andB               session control tower maintenance entities (see also               Section 2.1.5.1).   C               Added an example of registering an IP tower using the D               decnet_register node registration tool to the Network_;               Management -> Tools -> Decnet_Register topic.   B         2.1.5.3 Added Help for register and modify decnet_register                 Commands  G               Added new material about the modify and register commands 6               used to set the session control version.G               For more information about why these command examples may +               be useful, see the help text.   >         2.1.5.4 Added Information about Flushing the CDI Cache  E               Added material to the help text for the Flush_(OpenVMS) D               topic. This topic discusses flushing an entry from theI               Session Control Naming Cache (known as the CDI cache). Also =               added an example of flushing an IP cache entry.       I                                         New Features and Enhancements 2-7            !     New Features and Enhancements      2.1 Network Management    E     2.1.5.5 Modified Description of the Session Control Naming Search              Path Characteristic   <           Modified the description of the naming search path>           characteristic in the help text for the show sessionA           control command to reflect relaxed restrictions in both D           the content of and the order of the naming search path forD           DECdns servers. For more information about this topic, seeB           Chapter 7 of the HP DECnet-Plus for OpenVMS Installation>           and Configuration manual (in particular, the section@           entitled "Using the DECdns Namespace as Secondary on a           DECdns Server.")  <     2.1.5.6 Directory System Agent (DSA) Entity Help Updated  @           Replaced the Directory_Module help topic with new helpE           information for the HP OpenVMS Enterprise Directory product E           (HP's implementation of the ITU-T X.500 Recommendations for            OpenVMS).   ;     2.1.5.7 Added DNS/BIND Namespace Examples for LOOP Help   D           Added DNS/BIND namespace examples to the help for the loop@           loopback application command. For example, the example>           section now includes the following DNS/BIND example:  B           loop loopback application name DOMAIN:LAMCHP.SCH.DEC.COM  >     2.1.5.8 Updated Help for FDDI Station Link Event Reporting  E           Updated the Event_Messages -> FDDI_Station -> Link topic to C           reflect restrictions in FDDI Station Link event reporting :           which are imposed by the OpenVMS device drivers.  C           The following events are not logged, but their respective ;           counters are incremented when these events occur:                 block check error%              directed beacon received +              duplicate address test failure %              duplicate token detected               fci strip error              frame status error $              link buffer unavailable              pdu length error !              receive data overrun "              ring beacon initiated              ring purge error               trace initiated  %     2-8 New Features and Enhancements            I                                             New Features and Enhancements I                                                    2.1 Network Management     !                  transmit failure "                  transmit underrun  <               The "unrecognized individual pdu destination",H               "unrecognized multicast pdu destination", and "user bufferG               unavailable" events can be reported, and their respective G               counters can increase accordingly. However, DECnet blocks H               "unrecognized multicast pdu destination" by default. ReferE               to the SYS$MANAGER:NET$EVENT_LOCAL.TEMPLATE file if you &               wish to pass this event.  ;               The "ring initialization initiated" and "ring G               initialization received" events are now logged by certain A               OpenVMS device drivers. If an OpenVMS device driver E               supports these events, they are not logged on a one-to- G               one basis with increases in their corresponding counters. H               Instead, only one error report is issued for any number ofG               these events that occur within a sampling period. This is E               intended to decrease any possibility of flooding OPCOM.   (         2.2 New Devices Supported by MOP  F               Modified NET$NISCS_LAA.EXE to recognize new style deviceI               names returned by $GETDVI. This permits loads over SCSI PAC G               devices. Prior to this release, the satellite load failed E               with the following messages displayed at the satellite:   O         %VMScluster-I-MSCPCONN, Connected to a MSCP server for the system disk,            node nnnnnn M         %VMScluster-E-NOT_SERVED, Configuration change, the system disk is no &           longer served by node nnnnnn  8         2.3 DECnet-Plus and DECnet Phase IV support VLAN  >               The following improvements have been made to the=               NET$CONFIGURE.COM and NET$CONVERT_DATABASE.EXE:   I               o  DECnet-Plus and DECnet phase IV can be configured to run                   over VLAN.             I                                         New Features and Enhancements 2-9            !     New Features and Enhancements      2.4 Transport Improvements         2.4 Transport Improvements  E           The following improvements have been made to NET$TPCONS.EXE $           and NET$TRANSPORT_OSI.EXE:  @           o  This release adds support for listening to selectedD              interfaces for incoming DECnet over IP connections. ForE              more information, see Section 2.1.2 for V8.3 and Section               2.1.3.1.   C           o  The DECnet-Plus interface has been redesigned to allow B              independent restarts between the DECnet OSI TransportC              module and the HP TCP/IP Services for OpenVMS product. D              Previously, the entire system had to be rebooted if theD              TCP/IP PATHWORKS Internet Protocol (PWIP) interface wasE              restarted. Now, if the TCP/IP PWIP interface is disabled A              and then reenabled, DECnet-Plus starts new transport @              connections. Similarly, if the DECnet OSI TransportC              module is disabled and then reenabled, the TCP/IP PWIP @              interface receives new DECnet transport connections*              through the new TPCONS ports.  '     2.5 Host-Based Routing Improvements   ?           This release supports the configuration of host-based @           routers that use the link state routing algorithm. TheE           NET$CONFIGURE procedure always creates routers that use the D           routing vector algorithm. However, a new command procedure?           (ISIS$CONFIGURE.COM) can be used to modify the router @           configuration to use the link state routing algorithm.@           This procedure also allows more control of the routing?           configuration than is found in NET$CONFIGURE.COM. For @           more information, see the "Host-Based Routing" section@           in Chapter 8 of the HP DECnet-Plus for OpenVMS Network?           Management manual and the new ISIS$CONFIGURE appendix <           in the HP DECnet-Plus for OpenVMS Installation and           Configuration manual.   D           This release of the NET$ROUTING_IS.EXE module contains the!           following improvements:   C           o  Raised the maximum allowed routing circuits from 16 to               32.    &     2-10 New Features and Enhancements           I                                             New Features and Enhancements I                                       2.5 Host-Based Routing Improvements     H               o  Modified logic used to set maximum circuit segment sizeE                  for FDDI circuits. Previously, the calculation could I                  sometimes use the Phase IV default of 576. This has been @                  changed to always use the FDDI default of 4352.  (         2.6 Session Control Improvements  I               This release of the NET$SESSION_CONTROL.EXE module contains (               the following improvement:  I               o  On Integrity servers and Alpha systems, the NET$SESSION_ I                  CONTROL.EXE module now uses the name string from the PSB #                  instead of GETJPI.                                                                 I                                        New Features and Enhancements 2-11            !     New Features and Enhancements +     2.7 Distributed Naming Service (DECdns)     +     2.7 Distributed Naming Service (DECdns)   A           The following sections describe new features of DECdns.   8     2.7.1 DECdns Now Supports Dynamic Device Recognition  A           The static device tables formerly used to determine the D           devices used by DECdns have been removed. Now, DECdns usesE           the $DEVSCAN and $GETDVI system services to build a list of :           devices that have the following characteristics:  A           o  a device class of DC$SCOM (synchronous communication               device)  1           o  a device characteristic of DEV$V_NET   ?           o  a device status of UCB$V_ONLINE and UCB$V_TEMPLATE   -           o  a device name in the form _xxy0:   E           You can use the logical name DNS$ETHERNET_DEVICE to provide C           a list of devices that DECdns should NOT use. All devices C           must be in the form _xxy0:. The string can contain spaces C           and other text which is ignored by DTSS. For example, the B           following command tells DECdns not to use the _EIA0: and           _FWA0: devices.   N             $ DEFINE/SYSTEM DNS$ETHERNET_DEVICE "Don't use _EIA0: and _FWA0: "  C              ________________________ Note ________________________   @              Unterminated network adapters can cause the dynamicA              device recognition process to hang. Either terminate =              all network adapters or include any unterminated C              devices in the DNS$ETHERNET_DEVICE logical definition.   C              ______________________________________________________   6     2.7.2 DECdns Now Supports DECnet over TCP/IP Links  D           DECdns has been enhanced to support the DECnet over TCP/IPD           transport. The sections that follow discuss various topicsD           related to this new feature. For more information, see the>           HP DECnet-Plus for OpenVMS DECdns Management manual.  &     2-12 New Features and Enhancements           I                                             New Features and Enhancements I                                   2.7 Distributed Naming Service (DECdns)              2.7.2.1 Protocol Towers   H               The DNA$Towers attribute of the object entry for a Phase VG               node can now include a protocol tower with an IP address. H               The third tower in the following example is an IP protocol               tower.  +         DNS>show obj .xpr.wzbang dna$towers ,                                         SHOW@                                       OBJECT  WINTER:.xpr.wzbangB                                           AT  09-MAR-2004:14:55:020                             DNA$Towers (set) = :>                            Tower  1 Floor 1  = 01 13    (null)=                            Tower  1 Floor 2  = 03       00 13 >                            Tower  1 Floor 3  = 04       (null)U                            Tower  1 Floor 4  = 06       49 00 18 aa 00 04 00 2a 60 20 0                             DNA$Towers (set) = :>                            Tower  2 Floor 1  = 01 13    (null)=                            Tower  2 Floor 2  = 03       00 13 =                            Tower  2 Floor 3  = 05       de c0 U                            Tower  2 Floor 4  = 06       49 00 18 aa 00 04 00 2a 60 21 0                             DNA$Towers (set) = :>                            Tower  3 Floor 1  = 01 13    (null)=                            Tower  3 Floor 2  = 02       00 13 =                            Tower  3 Floor 3  = 05       de c0 C                            Tower  3 Floor 4  = 09       a1 72 5e 45          DNS>  B         2.7.3 decnet_register Now Supports IP Towers in the DECdns               Namespace   F               Normally, the IP towers and IP backtranslation softlinksG               for all nodes are now automatically updated in the DECdns E               namespace during regular tower and softlink maintenance F               operations. Occasionally, it may be necessary to performI               manual updates or to verify that the current information is I               correct. For this reason, the decnet_register tool has been I               enhanced to show and register IP towers and backtranslation B               softlinks for nodes within the DECdns namespace. TheD               following example illustrates how to use menu Option 1E               to display information about the node WINTER:.XPR.CASE:         I                                        New Features and Enhancements 2-13            !     New Features and Enhancements +     2.7 Distributed Naming Service (DECdns)          $  run decnet_register  M     DECNET_REGISTER - Manage node registrations in network directory services A       Use Return, CTRL/N, and CTRL/P to move between input fields .       Use "?" to obtain help, CTRL/Z to cancel  7        1 - Show information about registered node names (        2 - Register or modify node namesI        3 - Update registered node towers using information from the nodes (        4 - Rename a registered node nameI        5 - Repair the synonym and address links for registered node names          6 - Deregister node names  +        7 - Export node names to a data file -        8 - Import node names from a data file   -        9 - Set preferences and network values   '       10 - Manage the directory service        11 - Spawn to DCL   '       * Option (use CTRL/Z to exit):  1   $     Show registered node informationA       Use Return, CTRL/N, and CTRL/P to move between input fields .       Use "?" to obtain help, CTRL/Z to cancel  C     Specify the directory service as LocalFile, DECdns, or PhaseIV.         * Directory service:  DECdns  I     Specify the node to show using an explicit or wildcard name, an NSAP, %     or a Phase IV synonym or address.   -     * Node name or address:  WINTER:.XPR.CASE   G     Specify the information to display as either brief, full, or names. G     Specify the output file name (a blank line indicates the terminal).        * Display format:  full      * Output file:  :     Press Return to show the node values, CTRL/Z to cancel    &     2-14 New Features and Enhancements           I                                             New Features and Enhancements I                                   2.7 Distributed Naming Service (DECdns)       !         Directory Service: DECdns   '         Node name:     WINTER:.XPR.CASE          Phase IV synonym:  CASE   3         Address tower protocol and selector values: /           Session:   DNA_SessionControlV3 (SC3)                       00 13-           Transport: DNA_OSItransportV1 (TP4)                       DE C0*           Routing:   DNA_OSInetwork (CLNS);                      49::00-18:AA-00-04-00-24-60:21 (24.36)   /           Session:   DNA_SessionControlV3 (SC3)                       00 13"           Transport: DNA_NSP (NSP)(                      (no selector value)*           Routing:   DNA_OSInetwork (CLNS);                      49::00-18:AA-00-04-00-24-60:20 (24.36)   /           Session:   DNA_SessionControlV2 (SC2)                       00 134           Transport: DNA_OSItransportV1 (TP2 or TP0)                      DE C0            Routing:   DNA_IP (IP)"                      161.114.94.62           Synonym softlink name:(             WINTER:.DNA_NodeSynonym.CASE  A         Reverse address mapping (backtranslation) softlink names: B             WINTER:.DNA_BackTranslation.%X49.%X0018.%XAA00040024602             WINTER:.DNA_BackTranslation.%XA1725E3E  '         Number of nodes reported on:  1   -         2.8 Distributed Time Service (DECdts)   E               The following sections describe new features of DECdts.           I                                        New Features and Enhancements 2-15            !     New Features and Enhancements )     2.8 Distributed Time Service (DECdts)     8     2.8.1 DECdts Now Supports Dynamic Device Recognition  A           The static device tables formerly used to determine the D           devices used by DECdts have been removed. Now, DECdts usesE           the $DEVSCAN and $GETDVI system services to build a list of :           devices that have the following characteristics:  A           o  a device class of DC$SCOM (synchronous communication               device)  1           o  a device characteristic of DEV$V_NET   ?           o  a device status of UCB$V_ONLINE and UCB$V_TEMPLATE   -           o  a device name in the form _xxy0:   >           You can use the logical name DTSS$ETHERNET_DEVICE to?           provide a list of devices that DECdts should NOT use. @           All devices must be in the form _xxy0:. The string canE           contain spaces and other text which is ignored by DTSS. For D           example, the following command tells DECdts not to use the$           _EIA0: and _FWA0: devices.  O             $ DEFINE/SYSTEM DTSS$ETHERNET_DEVICE "Don't use _EIA0: and _FWA0: "   C              ________________________ Note ________________________   @              Unterminated network adapters can cause the dynamicA              device recognition process to hang. Either terminate =              all network adapters or include any unterminated 8              devices in the DTSS$ETHERNET_DEVICE logical              definition.  C              ______________________________________________________   6     2.8.2 DECdts Now Supports DECnet over TCP/IP Links  A           DECdts now supports operation in the DECnet over TCP/IP B           environment without requiring the use of a configuration;           file. This requires the use of the DECdns version ?           that supports DECnet over TCP/IP. From the management A           standpoint, global DECdts servers work much the same as C           they do in the DECnet-only environment. You still use the E           advertise command to add a global server to the global set. B           For more information, see the HP DECnet-Plus for OpenVMS#           DECdts Management manual.   &     2-16 New Features and Enhancements                         I                                                                         3 I         _________________________________________________________________   I                                      Corrections Included in this Release     G               This chapter discusses corrections included in HP DECnet- C               Plus for OpenVMS Version 8.4. The chapter contains an G               abbreviated list of the updates included in this release. E               If a specific update you are looking for is not listed, I               this does not mean that it is not included in this release. G               For further information on specific updates, contact your (               HP support representative.           3.1 DNS$ADVER.EXE   F               The following correction has been made to DNS$ADVER.EXE:  C               o  This release fixes the DECnet hang during start-up G                  when the DNS$ADVER process is in the RWAST state. This !                  happens when the I                  PQL_MBYTLM/BUFFER_LIMIT parameter is set to a high value G                  or when the number of network interfaces are more than                   10.  ?                  In addition to the messages that are logged in F                  DNS$ADVER_ERROR.LOG logfile, a message will be loggedF                  on the operator console when the DNS$ADVER process isD                  unable to start its protocol on any of the ethernet                  interfaces.           3.2 DTSS Changes  H               The following correction has been made to the DTSS$SERVICE               image:  C               o  This fix prevents the access violation error found >                  during DTSS server startup with global server                  configured.      I                                  Corrections Included in this Release 3-1            (     Corrections Included in this Release"     3.3 Network Management Changes    "     3.3 Network Management Changes  B           The following corrections are made to the network layer.  E           o  This release fixes the INVEXCEPTION crash in the routing @              layer caused because of accessing the corrupted end,              system cache database. When the@              $ MC NCL DISABLE ROUTING command is executed, apartA              from disabling the routing entity it clears the base C              address of the end system cache table while processing #              the incoming data PDU.   >           o  This release fixes the BADQHDR crash while trying@              to resume the network task, which is the "SUSPENDEDE              QUEUE" task at the session layer. Failure to acquire the E              secondary interlock on the header of the suspended queue =              at the session layer causes the system to crash.        3.3.1 End System Routing  D           The following correction has been made to the NET$ROUTING_           ES.EXE image:   ?           o  This release fixes some of the alignment faults in B              NET$ROUTING by aligning the unaligned variables found!              during DTSEND tests.   @           The following correction has been made to NET$ROUTING_*           ES.EXE and NET$ALIAS.EXE images:  E           o  This fix sets the ES hello packet with a holding time of E              zero so as to clear the adjacencies immediately when the /              "SHUT ALIAS port" command is used.   @           The following correction has been made to NET$ROUTING_3           VCM.EXE and SYS$NAME_SERVICES.EXE images:   @           o  This release fixes the alignment faults observed in?              SYS$NAME_SERVICES and NET$ROUTING_VCM on Integrity               server systems.  D           The following correction has been made to the NET$ROUTING_           IS.EXE image:   A           o  This release fixes the system crash while creating a ?              new manual adjacency with the same Adjacency name, A              LAN address, and ENDnode id on two different CSMA-CD               circuits.  ,     3-2 Corrections Included in this Release           I                                      Corrections Included in this Release I                                            3.3 Network Management Changes     -         3.3.2 NET$CONFIGURE Command Procedure   =               The following corrections have been made to the 2               NET$CONFIGURE.COM command procedure:  D               o  This fix validates the IP address and prompts untilD                  a valid IP address is entered for the "Interface(s)A                  for DECnet/OSI over TCP/IP" option while running 3                  NET$CONFIGURE in an advanced mode.   C               o  This release enables SYS$NODE* logicals to be read E                  from the NET$CONFIG.DAT file with the correct set of F                  privileges on an Integrity server satellite node. TheG                  following warning message is no longer displayed while .                  booting the satellite system:  T                  %DECnet-W-NOOPEN, could not open SYS$SYSROOT:[SYSEXE]NET$CONFIG.DAT  +         3.3.3 NET$STARTUP Command Procedure   ;               The following correction has been made to the 0               NET$STARTUP.COM command procedure:  F               o  The default protection of the OSIT$NAMES logical nameF                  table has been modified such that only the privilegedG                  user, such as SYSTEM will be able to modify the table.   C                  As described in Section 6.4.6.1 of DECnet-Plus for D                  OpenVMS Programming Manual, the SYSNAM privilege toG                  define a logical name in OSIT$NAMES is not applicable.   #         3.3.4 NCL$GLOBALSECTION.DAT   3               The following change has been made to $               NCL$GLOBALSECTION.DAT:  ?               o  In this release, the naming format of "rfc1006 G                  Duplicate Connection" is changed to "RFC1006 Duplicate D                  Connection". The following commands enable OSITP toI                  accept the RFC1006 CLASS-0 duplicate connections without 4                  affecting the original connections:  I                  $ mc ncl show osi transport RFC1006 Duplicate Connection X                  $ mc ncl set osi transport RFC1006 Duplicate Connection = TRUE or FALSE  I                                  Corrections Included in this Release 3-3            (     Corrections Included in this Release     3.4 OSAK Changes         3.4 OSAK Changes  9           The following corrections have been made to the !           OSAK$OSAKSHR.EXE image:   C           o  This release fixes the problem of OSAK ports not being A              closed properly even when the Directory System Agent C              (DSA) timer is set to 300. As a result, the DSA-server               would hang.  D           o  This fix avoids an access violation in OSAK$OSAKSHR.EXEE              when the OSAK library function, osak_close_port tries to 6              access a memory that is already freed-up.  9           o  When the OSI Transport connection is already A              established, remote NSAP address is not populated if >              a disruptive event occurs. This problem is fixed.       3.5 Session Control   9           The following corrections have been made to the (           NET$SESSION_CONTROL.EXE image:  B           o  This release suppresses the display of the Failure onC              the back translate address request message when a node E              is connected to another node using the SET HOST command.               This happens when:   A              -  A node with fullnodename, that is, with the first @                 octet (from left side) with greater than 8 alpha?                 numeric characters and without the alias in the +                 TCP/IP local host database.                    OR  A              -  A node is registered in the DECnet local database "                 without a synonym.  A           o  This releases fixes the crash in Session layer while @              processing an Expedited data event, which came from=              Transport layer for a non-existent Session port.         ,     3-4 Corrections Included in this Release           I                                      Corrections Included in this Release I                                                       3.6 Transport Layer              3.6 Transport Layer   =               The following corrections have been made to the *               NET$TRANSPORT_OSI.EXE image:  E               o  When there is a duplicate CONS connection at the OSI H                  transport, with the same source reference, this releaseH                  is fixed to reject the new connection without affecting)                  the existing connection.   G               o  This release fixes the INVEXCEPTION crash in the OSITP B                  port management routine while trying to access anE                  already deallocated network connection control block                   (NCCB).  I               o  This release fixes the INVEXCEPTION crash in OSITP$CLNS_ D                  CLOSEASSOCIATION because of an invalid VCRP addressF                  passed to this routine. The system crash occurs while?                  trying to access this invalid virtual address.   I               o  This release fixes the system crash with NAT Consumption I                  fault error in the NET$OSI_TRANSPORT module. This fix is =                  applicable only on Integrity server systems.   C               o  This release fixes the leaking BG devices which is G                  caused when an illegal packet is received and when the D                  transport connection between the TPCONS and the OSI)                  layer is not yet opened.   I               The following change has been made to CTF$OSITP_ANALYZE.EXE (               and NET$TRANSPORT_OSI.EXE:  I               o  This release is enhanced to display the Local and Remote E                  Transport Selector (Tsel) information as part of the B                  Remote Transport Disconnect OPCOM Event and LocalD                  Transport OPCOM Event on both Integrity servers andH                  Alpha systems. This will help you to debug or trace the%                  faulty applications.   =               The following corrections have been made to the *               NET$TRANSPORT_NSP.EXE image:  E               o  This release enhances the performance between DECnet D                  Alpha Phase IV and DECnet Integrity servers Phase VI                  (DECnet-Plus) system by transmitting less number of data "                  acknowledgements.  B                  The transmitter now processes less number of data:                  acknowledgements while transferring data.  I                                  Corrections Included in this Release 3-5            (     Corrections Included in this Release     3.6 Transport Layer     E           o  This release fixes the crash in NET$TRANSPORT_NSP caused 2              because of the NAT consumption fault.                                                                                      ,     3-6 Corrections Included in this Release                         I                                                                         4 I         _________________________________________________________________   I                                          Documentation Errata and Addenda     D               This chapter contains corrections and additions to theG               current documentation set for HP DECnet-Plus for OpenVMS.   )         4.1 Current Product Documentation   G               The current documentation set for DECnet-Plus is shown in !               the following list:   F               o  DECnet-Plus for OpenVMS Introduction and User's Guide                  Version 7.1,                  (Order number: AA-Q191F-TE)  +               o  DECnet-Plus Planning Guide                   Version 7.1,                  (Order number: AA-QBTHE-TE)  <               o  HP DECnet-Plus for OpenVMS Installation and                  Configuration                  Version 8.3,                  (Order number: BA406-90007)  >               o  HP DECnet-Plus for OpenVMS Network Management                  Version 8.2,                  (Order number: BA406-90006)  D               o  HP DECnet-Plus for OpenVMS Network Control Language                  Reference                  Version 8.2,                  (Order number: BA406-90004)  ,               o  DECnet-Plus Problem Solving                  Version 7.1,                  (Order number: AA-Q18ZE-TE)  =               o  HP DECnet-Plus for OpenVMS DECdns Management /                  Version 8.2/DECdns Version 2.0 ,                  (Order number: BA406-90002)  I                                      Documentation Errata and Addenda 4-1            $     Documentation Errata and Addenda%     4.1 Current Product Documentation     9           o  HP DECnet-Plus for OpenVMS DECdts Management +              Version 8.2/DECdts Version 2.0 (              (Order number: BA406-90003)  E           o  DECnet-Plus FTAM and Virtual Terminal Use and Management )              Version 7.1/FTAM Version 3.2 (              (Order number: AA-Q78TD-TE)  0           o  DECnet-Plus for OpenVMS Programming              Version 7.1(              (Order number: AA-Q195E-TE)  +           o  DECnet-Plus DECdts Programming +              Version 7.1/DECdts Version 1.1 (              (Order number: AA-PHEQC-TE)  )           o  DECnet-Plus OSAK Programming )              Version 7.1/OSAK Version 3.0 (              (Order number: AA-PJ1CE-TE)  3           o  DECnet-Plus OSAK Programming Reference )              Version 7.1/OSAK Version 3.0 (              (Order number: AA-PJ1DD-TE)  7           o  DECnet-Plus OSAK SPI Programming Reference )              Version 7.1/OSAK Version 3.0 (              (Order number: AA-QRAYB-TE)  )           o  DECnet-Plus FTAM Programming )              Version 7.1/FTAM Version 3.2 (              (Order number: AA-PJ1EF-TE)  '           o  DECnet/OSI for VMS CTF Use               Version 5.5(              (Order number: AA-PHEBB-TE)  ,     4.2 Documentation Update for Version 8.2  B           Several manuals have been updated for HP DECnet-Plus for>           OpenVMS Version 8.2. See the list in Section 4.1 for@           the version numbers associated with each manual in theC           documentation set. Much of the updated material came from D           entries in the Release Notes for several previous versions>           of DECnet-Plus. Table 4-1 provides a cross-reference@           between former Release Note topics and their locations@           in the new manuals. The manual references are given in  (     4-2 Documentation Errata and Addenda           I                                          Documentation Errata and Addenda I                                  4.2 Documentation Update for Version 8.2     E               the form manual-chapter or appendix where manual is the                following:  B                  INS - HP DECnet-Plus for OpenVMS Installation and                  ConfigurationD                  MNG - HP DECnet-Plus for OpenVMS Network ManagementA                  NCL - HP DECnet-Plus for OpenVMS Network Control #                  Language Reference C                  DNS - HP DECnet-Plus for OpenVMS DECdns Management C                  DTS - HP DECnet-Plus for OpenVMS DECdts Management   A               In many cases, the information in the Release Notes C               was interleaved with existing information. Therefore, G               references to specific sections in the new manuals is not                feasible.   A               Table 4-1 Documentation Update/Release Notes Cross- I               __________Reference________________________________________   I               Release_Note_Topic______________________Refer_to_..._______                  New Features                     NET$CONFIGURE   ;                       New option to configure DNS     INS-7                        servers   ;                       DNS server node can have other  INS-7 -                       name service as primary   ;                       Phase IV migration              INS-6 "                       improvements  ;                       New Support for DNS/BIND as     INS-6 *                       Primary Name Service  '                   NET$STARTUP Procedure   ;                       NET$STARTUP supports STARTUP_   MNG-8 )                       P2 SYSGEN procedure   #                   NET$LOGICALS File   ;                       New logicals                    MNG-6                      NET$SHUTDOWN  I                                                  (continued on next page)   I                                      Documentation Errata and Addenda 4-3            $     Documentation Errata and Addenda,     4.2 Documentation Update for Version 8.2    E           Table 4-1 (Cont.) Documentation Update/Release Notes Cross- E           __________________Reference________________________________   E           Release_Note_Topic______________________Refer_to_..._______   >                   New NET$APPLICATION_SHUTDOWN    MNG-6, MNG-8                   logical                  NCL   7                   Explanation of IP address       NCL-1 "                   backtranslations  7                   New management topics in NCL    NCL-1                    Help  7                   Improved explanation of access  NCL-1                    control   7                   Improved explanation of         NCL-1 "                   wildcard proxies  7                   New SHUT ALIAS PORT command     NCL-3                   Host Based Routing  8                   Routing Originating Queue       NCL-21/                   Limit characteristic modified   '               Session Control/CDI Cache   7                   CDI cache improvement           MNG-5   7                   CDI$SYSTEM_TABLE logical name   MNG-5                    table   7                   Resolution of IP fully-         MNG-5 !                   qualified names                  DECdns  7                   Establishing clerk connections  INS-7 '                   to WAN TCP/IP Servers   8                   New logicals for the DNS$ADVER  DNS-12                   process   7                   Controlling the LAN devices     DNS-6                     used by DECdts                 DECdts  E                                              (continued on next page)   (     4-4 Documentation Errata and Addenda           I                                          Documentation Errata and Addenda I                                  4.2 Documentation Update for Version 8.2     I               Table 4-1 (Cont.) Documentation Update/Release Notes Cross- I               __________________Reference________________________________   I               Release_Note_Topic______________________Refer_to_..._______   >                       New procedures for Changing     INS-7[1]                       Time  ;                       New DECdts NTP provider sample  DTS-C                        program   ;                       Designating Global Servers      DTS-2 -                       Using the BIND Database   ;                       Option to Disable DECdts at     DTS-2 !                       System Boot   ;                       Controlling the LAN devices     DTS-2 $                       used by DECdts                     OSAK  E                       OSAK new features moved to Documentation Errata                        chapter.  '               Documentation Corrections                      NCL   E                       Syntax corrections              NCL-(throughout =                                                       command C                                                       descriptions)   ;                       Alias Port Outgoing Default     NCL-3 *                       characteristic added  <                       Routing Entity Maximum Buffers  NCL-21-                       characteristic modified   <                       Removed restriction on          NCL-202                       modifying OSI Transport Cons,                       Filters characteristic  I               [1]See_also_the_"Setting_System_Time"_chapter_in_the_HP____   H               OpenVMS System Manager's Utility Guide, the "Creating TimeG               Zone Conversion Information" in the "Overview" chapter of G               the Compaq C Run-Time Library Utilities Reference Manual, F               and the "Date/Time Functions" chapter and tzset functionG               description in the HP C Run-Time Library Reference Manual )               for OpenVMS Systems manual.   I                                                  (continued on next page)   I                                      Documentation Errata and Addenda 4-5            $     Documentation Errata and Addenda,     4.2 Documentation Update for Version 8.2    E           Table 4-1 (Cont.) Documentation Update/Release Notes Cross- E           __________________Reference________________________________   E           Release_Note_Topic______________________Refer_to_..._______   7                   Added material about using SET  NCL-1 &                   NCL DEFAULT commands  7                   Added material about using NCL  NCL-1 "                   SNAPSHOT command                  Network Management  7                   New DECNET_VERSION values       MNG-3   ?                   Added material about using      MNG-11, NCL-1 "                   SNAPSHOT command             Operational Notes                   Network Management  >                   Startup procedure changed: NCL  MNG-6, MNG-8'                   information minimized   >                   decnet_register option 3 -      MNG-5, MNG-E*                   updating registered node                   towers                 DECdns  7                   Modifying a Clerk to use the    DNS-6                    Cluster Alias   8                   Providing adequate resources    DNS-12                   for DNS clerk   8                   Providing adequate resources    DNS-12                    for DNS server  8                   Using the DNS.CONF file         DNS-12  8                   Adjusting null_port_timeout in  DNS-12                   DNS.CONF file   8                   Note on using the NEW EPOCH     DNS-11                   command   8                   Default parameters for process  DNS-12'                   limits on DNS servers   8                   Removing Obsolete DNS$CACHE     DNS-12E           ________files______________________________________________   (     4-6 Documentation Errata and Addenda           I                                          Documentation Errata and Addenda I                                            4.3 Network Management and NCL     &         4.3 Network Management and NCL  B               The following sections describe documentation errataD               and addenda for the HP DECnet-Plus for OpenVMS NetworkD               Management, HP DECnet-Plus for OpenVMS Network ControlA               Language Reference, and DECnet-Plus Problem Solving                manuals.  .         4.3.1 Devices and OpenVMS Device Names  C               The sections that follow list the devices that can be D               configured using DECnet-Plus software. The last columnE               lists the device name to use for the communication port H               characteristic when creating entities that reference these               devices.  F                 ________________________ Note ________________________  B                 DECnet-Plus supports a subset of the communicationA                 devices supported by OpenVMS. Some of the devices D                 shown in these tables may be configurable (either byC                 NET$CONFIGURE or directly by NCL) but are no longer B                 supported by DECnet-Plus. See the Software ProductB                 Descriptions (SPDs) for HP DECnet-Plus for OpenVMSE                 and HP OpenVMS for a list of devices supported by the                   current release.  F                 ______________________________________________________           4.3.1.1 CSMA-CD Devices   G               The circuit devices listed in Table 4-2 can be configured C               using DECnet-Plus software. They provide multi-access G               connections among many nodes on the same CSMA-CD circuit.   I               Table_4-2_CSMA-CD_Devices__________________________________   K                                                                      DECnet   I               Device                                        OpenVMS  Comm I               Name______Type____________OS______I/O_Bus_____Name_____Port   H               82559     100BaseTX       IntegritPCI(embedded)I       EIc/               (Intel)                   servers   I                                                  (continued on next page)   I                                      Documentation Errata and Addenda 4-7            $     Documentation Errata and Addenda"     4.3 Network Management and NCL    E           Table_4-2_(Cont.)_CSMA-CD_Devices__________________________   G                                                                  DECnet   E           Device                                        OpenVMS  Comm E           Name______Type____________OS______I/O_Bus_____Name_____Port   D           A5230A    100BaseTX       IntegritPCI         EW       EWc+                                     servers   D           A5506B    100BaseTX       IntegritPCI         EW       EWc+                     (4-port)        servers   D           A6825A    1000BaseTX      IntegritPCI         EW       EWc+                                     servers   D           A6847A    1000BaseSX      IntegritPCI         EW       EWc+                                     servers   D           A7011A    1000BaseSX      IntegritPCI-X       EI       EIc+                     (2-port)        servers   D           A7012A    1000BaseTX      IntegritPCI-X       EI       EIc+                     (2-port)        servers   D           A9782A    1000BaseSX      IntegritPCI-X       EW       EWc+                                     servers   D           A9784A    1000BaseTX      IntegritPCI-X       EW       EWc+                                     servers   D           BCM5701   1000BaseTX      IntegritPCI(embedded)W       EWc,                                     servers,)                                     Alpha   D           BCM5703   1000BaseTX      IntegritPCI(embedded)W       EWc,                                     servers,)                                     Alpha   D           COREIO    10Base5         Alpha   TURBOchannelES       ESc  D           DEBNA     10Base5         VAX     BI-bus      ET       ETc  D           DEBNI     10Base5         VAX     BI-bus      ET       ETc  D           DEBNK     10Base5         VAX     BI-bus      ET       ETc  D           DEBNT     10Base5         VAX     BI-bus      ET       ETc  D           DEGPA-xx  1000BaseTX,SX   Alpha   PCI         EW       EWc  D           DEGXA-xx  1000BaseTX,SX   Alpha   PCI,PCI-X   EW       EWc  E                                              (continued on next page)   (     4-8 Documentation Errata and Addenda           I                                          Documentation Errata and Addenda I                                            4.3 Network Management and NCL     I               Table_4-2_(Cont.)_CSMA-CD_Devices__________________________   K                                                                      DECnet   I               Device                                        OpenVMS  Comm I               Name______Type____________OS______I/O_Bus_____Name_____Port   H               DELQA     10Base5         VAX     Q-bus       XQ       XQc  H               DELTA     10Base5 (2-     VAX     TURBOchannelEC       ECc                         port)   H               DELUA     10Base5         VAX     UNIBUS      XE       XEc  H               DEMNA     10Base5         VAX,AlphXMI         EX       EXc  H               DEQTA     10Base5         VAX     Q-bus       XQ       XQc  H               DESQA     10Base5         VAX     Q-bus       ES       ESc  H               DESVA     10Base5         VAX     embedded    ES       ESc  H               DEUNA     10Base5         VAX     UNIBUS      XE       XEc  H               DE20c     10Base2,5,T     Alpha   ISA         ER       ERc  H               DE422     10Base2/T       Alpha   EISA        ER       ERc  H               DE425     10Base2/5/T     Alpha   EISA        ER       ERc  H               DE434     10BaseT         Alpha   PCI         EW       EWc  H               DE435     10Base2/5/T     Alpha   PCI         EW       EWc  H               DE436     10BaseT (4-     Alpha   PCI         EW       EWc                         port)   H               DE450     10Base2/5/T     Alpha   PCI         EW       EWc  H               DE500-xx  100BaseTX,FX    Alpha   PCI         EW       EWc  H               DE504-BA  100BaseTX       Alpha   PCI         EW       EWc                          (4-port)  H               DE600-xx  100BaseTX,FX    Alpha   PCI         EI       EIc  H               DE602-xx  100BaseTX,FX    Alpha   PCI         EI       EIc                          (2-port)  H               KFE52     10Base5         VAX     Q-bus       EF       EFc  H               P2SE      100BaseTX       Alpha   PCI         EW       EWc  H               P2SE+     100BaseTX       Alpha   PCI         EW       EWc  H               PMAD      10Base5         VAX,AlphTURBOchannelEC       ECc  H               SGEC      10Base2         VAX     Local       EZ       EZc  I                                                  (continued on next page)   I                                      Documentation Errata and Addenda 4-9            $     Documentation Errata and Addenda"     4.3 Network Management and NCL    E           Table_4-2_(Cont.)_CSMA-CD_Devices__________________________   G                                                                  DECnet   E           Device                                        OpenVMS  Comm E           Name______Type____________OS______I/O_Bus_____Name_____Port   E           TGEC______10Base2_________Alpha___Local_______EZ_______EZc_   C              ________________________ Note ________________________   =              ATM devices are supported in emulated LAN (ELAN) A              mode by the OpenVMS EL device. For information about B              configuring an ELAN (and creating the EL device), see@              the "Configuring an Emulated LAN (ELAN)" section inB              the "Local Area Network (LAN) Device Drivers" chapter:              in the HP OpenVMS I/O Users Reference Manual.  >              LAN failover sets are supported by the OpenVMS LLC              device. For a general discussion of LAN failover sets, @              see Chapter 10 in Volume 2 of the HP OpenVMS System=              Manager's Manual. For information about managing @              LAN failover sets, see the description of the LANCP?              utility's DEFINE DEVICE and SET DEVICE commands in A              the HP OpenVMS System Management Utilities Reference               Manual.  C              ______________________________________________________        4.3.1.2 FDDI Devices  A           The devices listed in Table 4-3 can be configured using B           DECnet-Plus software. These devices provide multi-access@           connections among many nodes on the same FDDI circuit.  E           Table_4-3_FDDI_Devices_____________________________________   G                                                                  DECnet   E           Device                                        OpenVMS  Comm E           Name______Type____________OS______I/O_Bus_____Name_____Port   D           DEFAA     100 mmf         Alpha   FutureBus+  FA       FAc  E                                              (continued on next page)   )     4-10 Documentation Errata and Addenda            I                                          Documentation Errata and Addenda I                                            4.3 Network Management and NCL     I               Table_4-3_(Cont.)_FDDI_Devices_____________________________   K                                                                      DECnet   I               Device                                        OpenVMS  Comm I               Name______Type____________OS______I/O_Bus_____Name_____Port   H               DEFEA-xx  100 mmf, UTP    Alpha   EISA        FR       FRc  H               DEFPA-xx  100 mmf, UTP    Alpha   PCI         FW       FWc  H               DEFPZ-xx  100 mmf, UTP    Alpha   PCI         FW       FWc  H               DEFQA     100 mmf         VAX     Q-bus       FQ       FQc  H               DEFTA-xx  100 mmf, UTP    VAX,AlphTURBOchannelFC       FCc  H               DEFZA     100 mmf         VAX,AlphTURBOchannelFC       FCc  I               DEMFA_____100_mmf_________VAX,AlphXMI_________FX_______FXc_   @         4.3.1.3 Synchronous Devices (OpenVMS VAX and Alpha Only)  @               The synchronous devices listed in Table 4-4 can beH               configured by DECnet-Plus software. All of the synchronousB               line devices are either point-to-point or multipoint(               tributary circuit devices.  I               Table_4-4_Synchronous_Devices_(OpenVMS_VAX_and_Alpha_Only)_   K                                                                      DECnet   I               Device                                        OpenVMS  Comm I               Name______Type____________OS______I/O_Bus_____Name_____Port   I               DIV32                     VAX     Q-bus       SD       DIV- H                                                                      c-u  I               DMB32     1-port          VAX     VAXBI       SI       DMB- H                                                                      c-u  I               DMF32     1-port          VAX     UNIBUS      XG       DMF- H                                                                      c-u  H               DNSES     2-port          Alpha   EISA        ZE       ZE-H                                                                      c-u  I               DPV11     1-port          VAX     Q-bus       SE       DPV- H                                                                      c-u  I                                                  (continued on next page)   I                                     Documentation Errata and Addenda 4-11            $     Documentation Errata and Addenda"     4.3 Network Management and NCL    @           Table 4-4 (Cont.) Synchronous Devices (OpenVMS VAX andE           __________________Alpha_Only)______________________________   G                                                                  DECnet   E           Device                                        OpenVMS  Comm E           Name______Type____________OS______I/O_Bus_____Name_____Port   E           DSB32     2-port          VAX     VAXBI       SL       DSB- D                                                                  c-u  E           DSF32     2-port          VAX     MI-bus      SF       DSF- D                                                                  c-u  E           DSH32     2-port          VAX     Busless     ZS       DSH- D                                                                  c-u  E           DST32     1-port          VAX     Busless     ZS       DST- D                                                                  c-u  E           DSV11     2-port          VAX     Q-bus       SJ       DSV- D                                                                  c-u  E           DSW21     1-port          VAX     Busless     ZT       DSW- D                                                                  c-u  E           DSW41     1-port          VAX     Busless     ZT       DSW- D                                                                  c-u  E           DSW42     2-port          VAX     Busless     ZT       DSW- D                                                                  c-u  D           DSYT1     2-port          Alpha   TURBOchannelZY       ZY-D                                                                  c-u  E           DUP11     1-port          VAX     UNIBUS      SE       DPV- D                                                                  c-u  D           PBXDD-Ax  2-, 4-port      Alpha   PCI         ZZ       ZZ-D                                                                  c-u  D           PBXDI-Ax  2-, 4-port      Alpha   ISA         ZS       ZS-D                                                                  c-u  D           PBXDP-Ax  2-, 4-, 8-port  Alpha   PCI         ZW       ZW-D                                                                  c-u  D           SCC       1-port          Alpha   None        ZR       ZR-E           _______________________________________________________c-u_   )     4-12 Documentation Errata and Addenda            I                                          Documentation Errata and Addenda I                                            4.3 Network Management and NCL     7         4.3.1.4 Asynchronous Devices (OpenVMS VAX Only)   A               The asynchronous devices listed in Table 4-5 can be ?               configured by DECnet-Plus software on OpenVMS VAX                systems.  I               Table_4-5_Asynchronous_Devices_(OpenVMS_VAX_Only)__________   I                                                                    DECnet G               Device                                      OpenVMS  Comm I               Name________Type+___________I/O_Bus_________Name_____Port__   I               DHQ11       8-line,MC       Q-bus           TX       TX-c-u   I               DHU11       16-line,MC      UNIBUS          TX       TX-c-u   I               DHV11       8-line,MC       Q-bus           TX       TX-c-u   I               DMB32       8-line,MC       VAXBI           TX       TX-c-u   I               DMF32       8-line,MC       UNIBUS          TX       TX-c-u   I               DMZ32       24-line,MC      UNIBUS          TX       TX-c-u   I               DZ11        8-line,PMC      UNIBUS          TT       TT-c-u   I               DZ32        8-line,PMC      UNIBUS          TT       TT-c-u   I               DZQ11       4-line,PMC      Q-bus           TT       TT-c-u   I               DZV11       4-line,PMC      Q-bus           TT       TT-c-u I               +MC_=_full_modem_control,_PMC_=_partial_modem_control______   I               ___________________________________________________________            4.3.2 DTR/DTS   B               In Section 3.10.2 of the DECnet-Plus Problem SolvingF               manual, the documentation for the /nodename qualifier ofE               the DTS test command contains a statement that seems to I               indicate that DTS/DTR might support Phase V node names. The /               statement should read as follows:   H               The node-id can be 0, a Phase IV address or node name, or,I               on a Tru64 UNIX system, a DECnet-Plus NSAP address or Phase H               V node name. To specify a Phase V node on OpenVMS systems,B               you must use a node synonym of 6 characters or less.  I                                     Documentation Errata and Addenda 4-13            $     Documentation Errata and Addenda     4.4 OSAK Programming         4.4 OSAK Programming  A           The following sections provide information that updates @           the current OSI Applications Kernel (OSAK) programming           documentation.  ;     4.4.1 called_aei Parameter on A-ASSOCIATE and S-CONNECT            Indication Events   <           For A-ASSOCIATE indication events in the OSAK API,>           and S-CONNECT indication events in the SPI, the nsap?           field of the called_aei parameter is no longer filled >           in by OSAK. Previously, the called_aei.paddress.nsap@           structure contained the values specified in the local_C           aei.paddress.nsap parameter on the osak_open_responder or E           spi_open_responder call. However, these values are not used B           by osak_open_responder or spi_open_responder and may notC           contain correct information about the received connection ,           (for example, the transport type).  *     4.4.2 ROSE Minimum Workspace Increased  E           The minimum required size for the parameter block workspace C           for ROSE has increased. If your ROSE application is using @           the old minimum workspace size, you will now get a badB           parameter error. It is recommended that your applicationD           use the constant ROSE_WS_SIZE defined in osak_api.h to get-           the correct minimum workspace size.   C              ________________________ Note ________________________   B              Depending on the size of your application's parameterA              block workspace, you may have to recompile your ROSE               applications.  C              ______________________________________________________   )     4.4.3 Using OSAK with OSI over TCP/IP   D           On the initiator side, to make a connection using OSI over@           TCP/IP, specify as the NSAP the IP address as a 6-byteB           nibble packed hex value including the port number in theC           first two bytes. For example, the address of 16.36.12.142 2           on port 102 would be encoded as follows:  )     4-14 Documentation Errata and Addenda            I                                          Documentation Errata and Addenda I                                                      4.4 OSAK Programming     ,                           102  16.36.112.142+                            |   |  |   |   | ,                           0066  10 24  70 8E  A               In this case, the NSAP would be 00661024708E (hex). H               Specify the NSAP type as OSAK_C_RFC1006. For the transportG               template, specify either the pseudo-template "1006" or no H               template at all. OSAK uses a default template of "1006" if.               the NSAP type is OSAK_C_RFC1006.  B               On the responder side, to listen for OSI over TCP/IPH               connections, specify as the transport template the pseudo-               template "1006".  B         4.4.4 New Status Code for osak_send_more and spi_send_more               Routines  C               The routines osak_send_more and spi_send_more can now C               return a status code of OSAK_S_NODATA which indicates D               that there is no data remaining. In previous versions,H               the status code OSAK_S_INVFUNC may have been returned when"               this error occurred.  3         4.4.5 New OSAK API Routine: osak_tc_no_sc()   >               OSAK now contains a new API routine which allowsE               application programs to query OSAK to determine whether H               a transport connection has been established on a port, but+               a session connection has not.                  Syntax:   1               status = osak_tc_no_sc(port, state)                  C Binding:  +                  osak_tc_no_sc(port, state)                    osak_port port;                  int *state;                 Arguments:                 port  3               The OSAK port that you wish to query.                  state   I                                     Documentation Errata and Addenda 4-15            $     Documentation Errata and Addenda     4.4 OSAK Programming    D           A pointer to an integer where OSAK should return the state@           information. If the port is connected at the transportB           layer, but not at the session layer, OSAK returns a non-D           zero value (true). If the port is connected at the session3           layer, OSAK returns a zero value (false).              Description:  <           Call this routine to determine whether the port isB           connected at the transport layer, but not at the sessionC           layer. This information can be useful when interoperating B           with some other OSI implementations that may incorrectly>           terminate the transport connection, or may establish?           a transport connection but never complete the session C           connection. Use of this routine can assist an application @           in determining if the OSAK port is hung. An equivalentD           routine also exists for the SPI interface: spi_tc_no_sc().             Return Values:  B           OSAK_S_NORMAL    The routine has finished without error.  :           OSAK_S_INVPORT   The port identifier is invalid.  1     4.4.6 Handling of Default Transport Templates   C           The following information clarifies statements made about A           template defaulting in the DECnet-Plus OSAK Programming B           Reference and DECnet-Plus OSAK SPI Programming Reference           manuals.  <           If no transport template is specified in the osak_E           associate_req (API and ROSE) or spi_connect_req (SPI) call, +           OSAK takes the following actions:   C           o  If the NSAP in the osak_nsap data structure is CONS or <              CLNS, OSAK uses the default transport template.  E           o  If the NSAP in the osak_nsap data structure is RFC 1006, ;              OSAK uses the osit$rfc1006 transport template.           )     4-16 Documentation Errata and Addenda            I                                          Documentation Errata and Addenda I                                                      4.4 OSAK Programming     0         4.4.7 Omitted Parameter Block Parameters  G               In the DECnet-Plus OSAK SPI Programming Reference manual, H               the following OSAK parameter block parameters were omittedH               from the SPI routine descriptions. Although the parametersG               are listed in Section 1.2 and described in Section 1.4.2, E               they should also appear in the Parameters Used table as                follows:  I               ___________________________________________________________                ParametersI               Used_________Data_Type____Access___________________________   1               [user_       Address      read only                context]  I               port_id______osak_port____write_only_______________________   C               The preceding parameters should be listed for all SPI C               routines that have the OSAK parameter block argument, '               except for the following:                   o  spi_async_close                 o  spi_close_port                  o  spi_collect_pb   "               o  spi_expedited_req  8         4.5 File Transfer, Access, and Management (FTAM)  F               The following section describes the documentation update6               for DECnet-Plus FTAM Programming Manual.  .         4.5.1 Possible Values for OSIF_FAILURE  A               The error_code argument for the osif_get_event call F               provides further information if the status returned fromC               the call is OSIF_FAILURE. All the possible values for H               OSIF_FAILURE is documented in DECnet-Plus FTAM ProgrammingD               Manual. The two more possible values for OSIF_FAILURE,D               which is not documented includes the following values:  A               o  44743722 - corresponds to OSAK_S_INVAEI, invalid /                  application entity invocation.   C               o  44743770 - corresponds to OSAK_S_INVPCTXT, invalid +                  presentation context list.   I                                     Documentation Errata and Addenda 4-17                          I                                                                         5 I         _________________________________________________________________   I                                                         Operational Notes     F               This chapter contains operational notes and restrictionsH               for HP DECnet-Plus for OpenVMS. This chapter also includes6               known problems with the current release.           5.1 Network Management  F               The following sections discuss several operational notes'               about network management.   9         5.1.1 CTF Utility Now Requires Process Privileges   C               The CTF utility has always required that the invoking E               process have certain rights identifiers in order to use F               the START and STOP commands to control the collection ofF               trace records. These rights identifiers are described inA               Chapter 3 of the DECnet/OSI for VMS CTF Use manual.   D               Now, in addition to one or more of the required rightsG               identifiers, the invoking process must have the following E               process privileges before invoking CTF for any purpose:   E               ALTPRI, BYPASS, CMKRNL, NETMBX, PRMGBL, PRMMBX, PSWAPM, 7               SYSGBL, SYSLCK, SYSNAM, TMPMBX, and WORLD   C               If you invoke CTF from a process without the required A               process privileges, the utility exits with an error E               message indicating the first of the required privileges                not granted.  :         5.1.2 Tuning to Support the Larger CML BYTLM Value  E               The default BYTLM value for CML has been increased from C               10,000 to 64,000. This correction was done to prevent F               NCL from returning the NCL-E-OVERFLOWBYTLM error messageE               when large amounts of data were needed from CML. If you C               have ever experienced this problem, or if your MAXBUF   I                                                     Operational Notes 5-1                 Operational Notes      5.1 Network Management    B           value is already set to 64000 and you have received NCL-D           E-NORESOURCEAVAIL error messages, then you should make the,           changes described in this section.  B           To fully take advantage of the increased BYTLM value, do           the following:  4           1. Increase the value of MAXBUF to 64,000.  B           2. Raise the BYTLM quota on any account that might issueA              NCL commands requiring the increased resources to at E              least 65,000. Be sure to do this to at least the SYSTEM, @              CML$SERVER, and MIRRO$SERVER accounts. For example,@              to modify the CML$SERVER account, use the following              command:   '              $ run sys$system:authorize /              UAF> modify cml$server/bytlm=65000   =           3. Check for the existence of the logicals NET$ACP_ >              BYTLM, NET$EVD_BYTLIM, and NET$MOP_BYTLIM. If any>              of these logicals are defined and they are set to?              a value lower than 65,000, modify their entries in A              SYS$MANAGER:NET$LOGICALS.COM to raise their value to               at least 65,000.   >           4. Check for the existence of the NET$LESACP_BUFFER_@              LIMIT logical. If this logical is defined and it isB              set to a value lower than 65,000, modify its entry inE              SYS$STARTUP:NET$LES_STARTUP.COM to raise the value to at               least 65,000.  B           5. Check for the existence of the NET$ADVER_BUFFER_LIMIT>              logical. If this logical is defined and it is set?              to a value lower than 300,000, modify its entry in @              SYS$STARTUP:SYLOGICALS.COM to raise the value to at              least 300,000.   @           6. Reboot the system to make all the preceding changes              effective.   C           If, after applying the measures described in the previous D           list, you now receive NCL-E-NORESOURCEAVAIL errors insteadB           of NCL-E-OVERFLOWBYTLIM errors, this generally indicatesC           that your process BYTLM quota is not set high enough. Set E           the quota to a value slightly higher than the MAXBUF value. E           Setting process BYTLM quotas to 65,000 (as specified in the D           previous list) should be sufficient to avoid this problem.       5-2 Operational Notes            I                                                         Operational Notes I                                                    5.1 Network Management     G         5.1.3 COLLECT Command and Addressing in decnet_migrate Commands   E               Some connection errors might be reported for nodes with G               DECnet-Plus addresses that are not Phase-IV compatible as E               well. These errors occur because the network management @               interface on the OpenVMS operating system does notE               recognize connections to nodes by the explicit use of a B               DECnet-Plus address that is not Phase-IV compatible.  B               If a DECnet-Plus node also has a Phase-IV compatibleA               address, information is collected for it using that                address.  /         5.1.4 Decimal Syntax DSPs Not Supported   I               DECnet-Plus supports only those IDPs (initial domain parts) I               that specify the use of binary syntax DSPs (domain-specific C               parts). IDPs that specify decimal syntax DSPs are not                supported.  "         5.2 Devices and Data Links  D               The following sections discuss operational notes about,               device support and data links.  ?         5.2.1 Receive Buffers Attribute on HDLC LINK Entity Not <               Implemented (Integrity servers and Alpha only)  F               The receive buffers attribute of the hdlc link entity isG               not implemented in DECnet-Plus. If you attempt to set the H               attribute according to the following example, NCL displays4               the subsequent informational messages:  ?               NCL>set node 0 hdlc link hdlc-0 receive buffers 8   %               Node 0 HDLC Link HDLC-0 4               at 2004-04-28-09:51:10.780-04:00I0.113  $               Command failed due to:               set list error                 Characteristics 7               no such attribute ID: Receive Buffers = 8   I               HDLC (High-level Data Link Control) allocates the number of G               receive buffers that it requires; you cannot specify this                setting.  I                                                     Operational Notes 5-3                 Operational Notes      5.2 Devices and Data Links    #     5.2.2 FDDI Large Packet Support   C           Phase IV nodes do not support FDDI large packets. If your >           node has an FDDI controller that uses large packets,=           routing selects a smaller segment size for Phase IV C           adjacencies. To communicate with Phase IV nodes, you must C           enable Phase IV addressing on the routing circuit. Verify E           that the enable phaseiv address attribute is set to true on E           one FDDI circuit in the SYS$MANAGER:NET$ROUTING_STARTUP.NCL            file.        5.3 Transport Layer   B           The following sections discuss operational notes for the$           transports in DECnet-Plus.  +     5.3.1 NSP Characteristics for X.25 PVCs   B           If a node has routing circuits of type x25 permanent you?           should set the NSP flow control policy characteristic =           to no flow control. In addition, if the call packet B           window size is 8 or less, you should set the NSP maximum?           window characteristic to 8. This lowers the number of @           NSP unacknowledged transmits and thus prevents the NSP*           out-of-order cache from filling.  C     5.3.2 NSP Flow Control Policy and DECnis and x25Gateway Routers   C           In DECnet-Plus Version 6.3, several corrections were made D           to NSP flow control algorithms. Previous to these changes,D           if segment flow control was used flow control credits were@           sometimes improperly handled and the connections wouldD           appear to hang. The NSP software in DECnis routers and theD           x25Gateway product is based on the pre-DECnet-Plus VersionE           6.3 software. For this reason, whenever a connection is set C           up to one of these hardware products the NSP flow control D           should always be set to no flow control. Note that segmentC           flow control is the default for NSP's flow control policy ?           characteristic. Therefore, you must explicitly select @           NONE when running NET$CONFIGURE, use NCL to modify theC           running system, or edit the NCL startup script created by            NET$CONFIGURE.           5-4 Operational Notes            I                                                         Operational Notes I                                                       5.3 Transport Layer              5.3.3 OSI Transport   9               The following notes apply to OSI transport:   E               o  If OSI transport times out during data transfer mode A                  because the remote end is unreachable, the error D                  SS$_CONNECFAIL may also be returned in the IOSB forD                  the $QIO(IO$_READVBLK) or $QIO(IO$_WRITEVBLK) call.D                  User code should handle SS$_TIMEOUT as well as SS$_                  CONNECFAIL.  G               o  When defining an RFC 1006 address using the OSIT$NAMES I                  logical name table, you must put a quotation mark around %                  the address portion.   F               o  The requirement against using 0 (zero) and 1 as validD                  NSELs (network selectors) has been removed, but the.                  following restrictions apply:  E                  -  The selector fields for OSI transport must be the D                     same in both transport partners if the packet isI                     traversing a backbone containing Phase IV routers (as 7                     opposed to routing vector domains).   I                  -  Although the cluster alias uses two ranges of network E                     transport selector fields to reduce the risk of a C                     collision, HP recommends that you do not choose E                     values from those ranges, or at least that you do B                     not choose the first few values in each range.  E               o  The osi transport entity does not support a value of G                  0 for the maximum remote NSAPs (network service access #                  points) attribute.   E               o  The osi transport template entity does not support a H                  value of any for the network service attribute. If thisH                  attribute is set to any, it is treated by OSI transport                  as clns.            5.4 Session Control   D               The following sections discuss operational notes about               Session Control.    I                                                     Operational Notes 5-5                 Operational Notes      5.4 Session Control     A     5.4.1 Transport Precedence in Predominantly Phase IV Networks   ?           When using a Phase V node in a predominantly Phase IV >           network, the default for session control's transportE           precedence characteristic is {OSI,NSP}. This causes session A           control to attempt an OSI connection first, followed by A           an NSP connection. If you have a predominantly Phase IV C           network, this causes an unnecessary delay when connecting D           to Phase IV nodes. If the precedence is causing the delay,B           the delay is not seen when connecting in the reverse. ToE           change the precedence, insert the following line at the end .           of the NET$SESSION_STARTUP.NCL file:  E           set node 0 session control transport precedence = {NSP,OSI}   B           Remember to reinsert this line if you run NET$CONFIGURE.  5     5.4.2 Session Control Back Translation Soft Links   =           Although the default for Session Control's maintain D           backward soft links characteristic is correctly documentedB           as false, on OpenVMS systems the Session Control startup9           script always sets this characteristic to true.   E     5.4.3 Restriction When Using Applications Supported Using Cluster            Aliases   E           Due to a design restriction, incoming ALIAS connections are E           forwarded to cluster members somewhat differently depending ?           upon whether the SESSION CONTROL APPLICATION entity's =           ADDRESS set contains a NUMBER parameter (equivalent ;           to Phase IV's connect by object number) or a TASK ?           parameter (equivalent to Phase IV's connect by object ?           name). For an incoming connect by object number, each A           ALIAS entity has access to a cluster-wide object number =           table that specifies which object numbers have been A           defined for each cluster member and the status of their ?           INCOMING ALIAS characteristic. The result is that the A           connection forwarding mechanism works as expected, that C           is, connections are forwarded or not forwarded to cluster B           members correctly depending upon whether the applicationB           exists on the member and depending on the setting of the#           INCOMING ALIAS parameter.          5-6 Operational Notes            I                                                         Operational Notes I                                                       5.4 Session Control     E               However, the mechanism for mapping incoming connections B               by object name using this cluster-wide object numberE               table does not exist and the result is that connections C               are forwarded to a given cluster member regardless of B               whether the application exists on a given member andG               regardless of the setting of the INCOMING ALIAS parameter D               on a given member. If you wish to restrict access to aI               network application supported using a cluster alias (either E               by not having the application present on a member or by E               setting the INCOMING ALIAS characteristic to FALSE on a I               member), you must create the SESSION CONTROL APPLICATION by I               supplying the NUMBER keyword for the ADDRESS characteristic H               (that is, supplying the object number), so that connection+               forwarding works as expected.   /         5.5 Distributed Naming Service (DECdns)   B               The following sections discuss operational notes for               DECdns.   H         5.5.1 Creating Clearinghouses When IP Address is Zero Causes DNS               Server Hang   F               Do not create a clearinghouse when the node's IP addressG               is all zeros. You can determine if the address is zero by 1               using the NCL command SHOW ADDRESS.   I               After each system boot, the local node's IP address is zero E               until the first incoming or outgoing OSI over TCP/IP or H               DECnet over TCP/IP connection occurs on the local node. AtF               that time, the PATHWORKS Internet Protocol (PWIP) driverC               included with HP TCP/IP Services for OpenVMS provides E               DECnet-Plus with its IP address. Consequently, at least G               one OSI over TCP/IP or DECnet over TCP/IP connection must @               occur before attempting to create a clearinghouse.  H               An easy method to ensure that at least one OSI over TCP/IPF               or DECnet over TCP/IP connection has been made is to useI               the SET HOST command with the IP address of the local node. I               (If you don't know the local node's IP address, use the DCL I               SHOW LOGICAL *HOSTADDR command to display it.) The SET HOST F               command causes HP TCP/IP Services for OpenVMS to provideF               the local IP address to DECnet-Plus. Remember to use theI               NCL SHOW ADDRESS command to verify that the local node's IP '               address has been defined.   I                                                     Operational Notes 5-7                 Operational Notes +     5.5 Distributed Naming Service (DECdns)     8           If fail to do this, you may have to delete the@           clearinghouse and start over after you have obtained a           non-zero IP address.  E           If you try to use a clearinghouse with zero IP addresses in C           the towers it is likely that the DECdns server will hang.        5.5.2 Server Startup Delay  B           There can be a delay in the startup of the DECdns serverB           when the server is using DECnet over TCP/IP connections.B           This delay is due to the time required for the server toD           obtain a non-zero IP address from DECnet and the PATHWORKS>           Internet Protocol (PWIP) software. The IP address isD           initially zero until it is updated by DECnet and PWIP with-           the actual IP address for the node.   C     5.5.3 Delay in Node Name-to-Address Translations When DECdns Is .           Using DECnet over TCP/IP Connections  B           When DECdns is using DECnet over TCP/IP connections, youB           may experience delays whenever DECnet has to translate a@           node name to a node address using the node's IP tower.A           These delays can occur when you are using NCL, when you D           invoke a DECnet application, or when you perform any otherD           action that requires translating the node's name to its IP           address.  >           The DECdns clerk, like any other DECnet application,=           uses DECnet to access the DECdns server. Currently, ?           Session Control's transport precedence characteristic ?           does not support a value for the IP tower. Therefore, B           Session Control always attempts to connect to the DECdnsB           server using the NSP and OSI towers before trying the IPC           tower. After DECnet notifies DECdns that it cannot make a B           connection on a OSI or NSP tower, the DECdns clerk tries           the IP tower.   C              ________________________ Note ________________________   B              This problem is especially noticeable in environmentsB              where a process spawns multiple subprocesses, each of@              which performs a network command. This is common in%              some batch environments.   C              ______________________________________________________        5-8 Operational Notes            I                                                         Operational Notes I                                   5.5 Distributed Naming Service (DECdns)     E         5.5.4 Problem Creating Clearinghouse Using DECnet over TCP/IP                Connections   F               When creating a new clearinghouse that joins an existingF               namespace in an environment that uses DECnet over TCP/IPI               connections, it is possible to have a clearinghouse created C               without the root directory. This is usually due to an D               intermittent communications error during clearinghouse9               creation. This problem occurs infrequently.   I               The current workaround is to force the creation of the root I               directory by issuing a manual skulk command as shown below:                  $ mcr dns$control $               DNS>set dir . to skulk  @         5.5.5 DNS$CONFIGURE Option 4 Does Not Display IP Address  :               Option 4 of the DECdns configuration programD               (DNS$CONFIGURE.COM) is used to display a server node'sE               address (as described in Section 10.5 of the HP DECnet- E               Plus for OpenVMS DECdns Management manual). This option E               has not been enhanced to display the node's IP address. F               As a workaround, use the NCL show node [node-id] address               command.  ;         5.5.6 Limitation on Size of Checkpoint File Records   H               The checkpoint file has a limitation of 500 blocks maximumF               on the size of individual records. To detect any recordsH               over this limit or approaching this limit, run the SURGEONG               "-scanrx" option. You will need to take corrective action F               if you see a line indicating greater than 500 blocks andG               the number of records is one (RECS: 1) because the server C               may bugcheck with a 902 error in the DB_COMPRESSION.C                module.   E               Records that exceed the 500 block maximum can be caused H               by an application that is writing records larger than thisG               limit or the garbage collector mechanism (removes deleted &               records) is not running.  I               To correct the problem, apply one of the following actions:   @               o  Use the SURGEON "-exciser" option to remove the"                  offending records  I                                                     Operational Notes 5-9                 Operational Notes +     5.5 Distributed Naming Service (DECdns)     <           o  Use the recreate object command (if the garbage'              collector is not running).   E           If you have any questions about doing this, consult your HP            representative.   D           Avoid the situation with the garbage collector not running@           by making sure all your directories skulk to a success9           status and that the DNS$ALLUPTO date is recent.   E           Use the following command in DNS$CONTROL to check the skulk 5           status of all directories in the namespace:   &           SHOW DIR ... DNS$SKULKSTATUS  ?           Use the following command in DNS$CONTROL to check the ?           DNS$ALLUPTO date on all directories in the namespace:   "           SHOW DIR ... DNS$ALLUPTO  /     5.5.7 PAGEDYN Resources: Clerks and Servers   @           DECdns clerk and server systems can require additional3           paged dynamic memory resources (PAGEDYN).   C           For DECdns clerk systems, consider increasing the PAGEDYN E           resource on the node if you see either the RESOURCEERROR or 6           NONSRESOURCES error during skulk operations.  A           Before you configure a system as a DECdns server, check A           that the system has at least 50,000 free bytes of paged >           dynamic memory. Insufficient paged dynamic memory onE           servers can cause configuration errors, skulk failures, and C           in some cases normal clerk operations can fail, returning :           either the RESOURCEERROR or NONSRESOURCES error.  E           The DNS$SERVER.LOG file can also contain messages regarding +           failures caused by this resource.   B           Servers holding master replicas of directories that haveC           many read-only replicas can also require additional paged            dynamic memory.            5-10 Operational Notes           I                                                         Operational Notes I                                   5.5 Distributed Naming Service (DECdns)     D         5.5.8 Error Message Generated by DECdns Clerk During Startup  G               The DECdns clerk startup might output the following error                message:  8               create node 0 dns clerk known namespace CZ  $               command failed due to:               process failure   F               A Known Namespace with this name or NSCTS already exists  >               You can disregard this message. The DECdns clerkC               configuration procedure puts a create dns clerk known I               namespace command for the default namespace into the DECdns G               clerk NCL startup file. The command remains there in case B               the DECdns cache file has been deleted or corrupted.  4         5.5.9 Miscellaneous DECdns Operational Notes  @               You might encounter the following DECdns problems:  F               o  DNS$CONTROL might return Syntax Error if the clerk is                  disabled.  B               o  You should not use DNS$CONTROL to modify the DNA_>                  NodeSynonym attribute on DECnet node objects.E                  DNS$CONTROL displays the attribute properly but does E                  not modify it properly. Use the decnet_register node B                  registration tool to modify DECnet data stored in                  DECdns.  I               o  Re-created entries retain the case of the original entry                   name.  H               o  If you have trouble creating a clearinghouse, make sureE                  that both the dns$server account (user authorization =                  file entry) and its default directory exist.               I                                                    Operational Notes 5-11                 Operational Notes )     5.6 Distributed Time Service (DECdts)     )     5.6 Distributed Time Service (DECdts)   >           The following sections discuss operational notes for           DECdts.   ;     5.6.1 Automatic Time Zone Changes on Rebooting Clusters   C           If all members of a cluster are down when daylight saving A           time (DST) takes effect and automatic time zone changes A           are enabled, then members may reboot with the incorrect @           local time. If you anticipate that the cluster will beA           down during the change to or from daylight saving time, E           you should disable automatic time zone changes and make the            changes manually.        5.7 OSAK Programming  B           The following sections discuss operational notes for the3           OSI Applications Kernel (OSAK) interface.   0     5.7.1 User Data Size Restriction for Tracing  E           OSAK does not support tracing with user data buffers larger            than 32,765 bytes.  -     5.7.2 OSAK Version 1.1 No Longer Supplied   ?           HP no longer provides the OSAK Version 1.1 interface.   =           If you use the OSAK Version 1.1 interface, you must B           migrate to the OSAK Version 3.0 SPI (session programming@           interface). The OSAK Version 3.0 SPI provides the same9           capabilities as the OSAK Version 1.1 interface.   B           For detailed information about the OSAK Version 3.0 SPI,D           see the DECnet-Plus OSAK SPI Programming Reference manual.  E     5.7.3 Migrating Applications from Version 2.0 to Version 3.0 OSAK            API Interface   C           Version 3.0 of OSAK includes a programming interface that B           is backwards compatible with the Version 2.0 programming=           interface. As a result of more rigorous conformance B           testing, some additional problems have been uncovered in$           the Version 2.0 interface.       5-12 Operational Notes           I                                                         Operational Notes I                                                      5.7 OSAK Programming     B               As a result, applications built against OSAK VersionE               2.0 might encounter problems when using the Version 2.0 C               backwards-compatible interface in OSAK Version 3.0 if G               the applications contain previously untrapped application                problems.   F         5.7.4 Misleading OSAK Error Message: SPM Congestion at Connect               Time  B               When OSAKserver receives an association request thatE               specifies a nonexistent user identity, it generates the =               error message "SPM Congestion at Connect Time."   A               If you see this error, check that the user name and C               password specified in the request are correct. If the E               user name is correct but the password is incorrect, the G               OPCOM message %LOGIN-F-INVPWD is logged. If the user name 7               is incorrect, no OPCOM message is logged.                                                       I                                                    Operational Notes 5-13                 Operational Notes      5.8 DECnet Programming         5.8 DECnet Programming  @           The following sections discuss programming issues that4           apply to the DECnet programming interface.  -     5.8.1 64-Bit Virtual Address Restrictions   =           You can use 64-bit virtual addresses only with $QIO ?           operations on the NET: devices; you cannot use 64-bit D           virtual addresses with $QIO operations on the OS: devices.  A           For transparent task-to-task communication, the $ASSIGN A           system service accepts only 32-bit addresses and 32-bit B           descriptors for the DEVNAM parameter when it describes aB           network connect block (NCB). You can use non-transparentA           task-to-task operations when you want 64-bit descriptor =           addresses and 64-bit descriptors to specify an NCB.   )     5.8.2 Backtranslation of IP Addresses   A           For IP addresses, session control returns the full name C           if the synonym is not available regardless of the Session B           Control Application Node Synonym setting. If neither the@           full name nor synonym is available, the IP$aa.bb.cc.dd           format is returned.   E           If the system is configured to use IP addresses, you should C           prepare the application to receive a node name or address E           string longer than six characters in length even if Session B           Control Application Node Synonym = TRUE is specified for           the application.  -     5.8.3 Applications Connection Requirement   >           With DECnet-Plus, your application must wait for theC           completion of the $QIO system service call used to accept A           the connection before attempting to use the connection.                      5-14 Operational Notes