                                   H                     Compaq_DECnet-Plus_for_OpenVMS______________________!                     Release Notes                          March 2001      D                     This manual describes new features not discussedF                     in the current documentation, corrections includedF                     in this release, documentation errata, operational?                     notes, and known problems and restrictions.               C                     Revision/Update Information:  This is a revised 9                                                   manual.   G                     Operating Systems:            OpenVMS Alpha Version 5                                                   7.3 I                                                   OpenVMS VAX Version 7.3   H                     Software Version:             Compaq DECnet-Plus forF                                                   OpenVMS, Version 7.3        /                     Compaq Computer Corporation "                     Houston, Texas                   ,            2001 Compaq Computer Corporation  A           COMPAQ, VAX, VMS, the Compaq logo, and the DIGITAL logo 9           Registered in U.S. Patent and Trademark Office.   D           ACMS, DDCMP, DECdtm, DECnet, DNA, OpenVMS, VAXcluster, andD           VMScluster are trademarks of Compaq Information Technology           group, L.P.   A           Motif, OSF/1, and UNIX are registered trademarks of The            Open Group.   =           All other product names mentioned herein may be the A           trademarks or registered trademarks of their respective            companies.  C           Confidential computer software. Valid license from Compaq D           or authorized sublicensor required for possession, use, orD           copying. Consistent with FAR 12.211 and 12.212, CommercialA           Computer Software, Computer Software Documentation, and A           Technical Data for Commercial Items are licensed to the E           U.S. Government under vendor's standard commercial license.   ?           Compaq shall not be liable for technical or editorial /           errors or omissions contained herein.   B           The information in this publication is subject to changeA           without notice and is provided "AS IS" WITHOUT WARRANTY @           OF ANY KIND. THE ENTIRE RISK ARISING OUT OF THE USE OFB           THIS INFORMATION REMAINS WITH THE RECIPIENT. IN NO EVENT?           SHALL COMPAQ BE LIABLE FOR ANY DIRECT, CONSEQUENTIAL, D           INCIDENTAL, SPECIAL, PUNITIVE, OR OTHER DAMAGES WHATSOEVERE           (INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS =           PROFITS, BUSINESS INTERRUPTION, OR LOSS OF BUSINESS >           INFORMATION), EVEN IF COMPAQ HAS BEEN ADVISED OF THE@           POSSIBILITY OF SUCH DAMAGES. THE FOREGOING SHALL APPLY?           REGARDLESS OF THE NEGLIGENCE OR OTHER FAULT OF EITHER B           PARTY AND REGARDLESS OF WHETHER SUCH LIABILITY SOUNDS INB           CONTRACT, NEGLIGENCE, TORT, OR ANY OTHER THEORY OF LEGALA           LIABILITY, AND NOTWITHSTANDING ANY FAILURE OF ESSENTIAL (           PURPOSE OF ANY LIMITED REMEDY.  D           The limited warranties for Compaq products are exclusivelyD           set forth in the documentation accompanying such products.>           Nothing herein should be construed as constituting a)           further or additional warranty.                                  C   _________________________________________________________________   C                                                            Contents       C   Preface...................................................    vii      1  Installation   C         1.1   OpenVMS Software Version Requirement..........    1-1      2  New Features   C         2.1   NET$CONFIGURE Improvements....................    2-1 C         2.2   Phase IV Migration Improvements...............    2-1 7         2.3   NET$SHUTDOWN_APPLICATION Logical Added to C               NET$SHUTDOWN..................................    2-2 C         2.4   NCL$GLOBALSECTION.DAT Updated.................    2-2 C         2.5   NCL HELP Updates..............................    2-3 C         2.5.1     Improved Organization.....................    2-3 C         2.5.2     Help for SHOW DTSS Updated................    2-3 <         2.5.3     Updated Information for Access Control andC                   Proxy Information.........................    2-3 :         2.5.4     Updated Help for FDDI Station Link EventC                   Reporting.................................    2-8 C         2.6   New Devices Supported by MOP..................    2-9 C         2.7   Host Based Routing Improvements...............    2-9 C         2.8   Session Control Improvements..................    2-9 C         2.9   CDI$SYSTEM_TABLE Logical Name Table...........   2-10 C         2.10  Backtranslation Over DNS/BIND.................   2-10 C         2.11  OSAK Programming..............................   2-10 9         2.11.1    called_aei Parameter on A-ASSOCIATE and C                   S-CONNECT Indication Events...............   2-11 C         2.11.2    New Status Code...........................   2-11 C         2.11.3    ROSE Minimum Workspace Increased..........   2-11 C         2.11.4    Handling of Default Transport Templates...   2-11 C         2.12  DECdns........................................   2-12 C         2.12.1    New Device Support........................   2-12   C                                                                 iii                    E           2.12.2    DNS Logging Enhanced......................   2-12 E           2.12.3    New System Logicals for DNS$ADVER.........   2-12 E           2.13  DECdts........................................   2-13 E           2.13.1    New Device Support........................   2-13 8           2.13.2    New Procedures for Changing DaylightE                     Savings Time Zone Rules (Alpha Only)......   2-13 E           2.13.3    Option to Disable DTSS at System Boot.....   2-16 E           2.13.4    New DTSS NTP Provider Sample Program......   2-17   +     3  Corrections Included in This Release   E           3.1   Network Management Changes....................    3-1 E           3.1.1     NET$CONFIGURE Command Procedure...........    3-1 E           3.1.2     NET$STARTUP Command Procedure.............    3-2 E           3.1.3     NET$SHUTDOWN Command Procedure............    3-2 E           3.1.4     NCL Syntax Change for MTS Entity..........    3-2 >           3.1.5     NCL Parsing Fix for End User SpecificationE                     Data Types................................    3-3 E           3.1.6     Event Dispatcher..........................    3-3 E           3.1.7     Common Management Listener (CML)..........    3-4 E           3.1.8     Common Trace Facility (CTF)...............    3-4 E           3.2   Transport Layer...............................    3-4 E           3.2.1     Network Services Protocol (NSP)...........    3-4 E           3.2.2     OSI Transport Protocol....................    3-5 E           3.2.3     DECnet over IP (RFC 1006).................    3-6 E           3.3   Network Layer.................................    3-6 E           3.3.1     End System Routing........................    3-6 E           3.3.2     Host Based Routing........................    3-6 E           3.3.3     Alias.....................................    3-7 E           3.4   Session Control...............................    3-7 E           3.5   QIO Interface.................................    3-8 E           3.6   Maintenance Operations Protocol (MOP).........    3-9 E           3.7   Distributed Naming Service (DECdns)...........   3-10 E           3.7.1     Clerk Changes.............................   3-10 E           3.7.2     Server Changes (VAX Only).................   3-10 E           3.8   Distributed Time Service (DECdts).............   3-13 E           3.9   X.25 Native Mode (VAX Only)...................   3-13 <           3.10  Wide Area Network Device Driver Support (VAXE                 Only).........................................   3-14                  iv                            4  Documentation Errata   I               4.1   Network Management and NCL....................    4-1 I               4.1.1     Routing Maximum Buffers Characteristic....    4-1 I               4.1.2     DTS/DTR and Phase V Node Names............    4-1 B               4.1.3     Using the ADD Verb with OSI Transport CONSI                         Filter Entities...........................    4-2 I               4.1.4     NET$EXAMINE Right Required................    4-2 I               4.1.5     Configuring Multiple Cluster Aliases......    4-2 I               4.1.6     Supplying Access Control Information......    4-2 I               4.1.7     NCL Snapshot Command......................    4-6 I               4.2   OSAK Programming..............................    4-6 I               4.2.1     Using OSAK over RFC1006...................    4-6 I               4.2.2     New OSAK API Routine: osak_tc_no_sc() ....    4-6 I               4.2.3     Omitted Parameter Block Parameters........    4-7 I               4.3   DECdns........................................    4-8            5  Operational Notes  I               5.1   NSP Characteristics for X.25 PVCs.............    5-1 I               5.2   OSI Transport.................................    5-1 B               5.3   Transport Precedence in Predominantly Phase IVI                     Networks......................................    5-2 A               5.4   Upgrading to DECnet-Plus with Systems Running I                     DEC X.25 (Alpha Only).........................    5-2 5               5.5   COLLECT Command and Addressing in I                     DECNET_MIGRATE Commands.......................    5-3 I               5.6   Decimal Syntax DSPs Not Supported.............    5-3 I               5.7   FDDI Large Packet Support.....................    5-3 =               5.8   Startup Procedure Change: NCL Information I                     Minimized.....................................    5-4 I               5.9   Setting Alias Selection Weights...............    5-4 B               5.10  Configuring X.25 Access Filters for Use by OSII                     Transport (VAX Only)..........................    5-4 I               5.11  DECdns........................................    5-5 I               5.11.1    Adjusting null_port_timeout in DNS.CONF...    5-6 I               5.11.2    Providing Adequate Resources for DECdns...    5-6 I               5.11.3    Using the DNS.CONF Configuration File.....    5-7 =               5.11.4    Limitation on Size of Checkpoint File I                         Records...................................   5-10 I               5.11.5    Using the NEW EPOCH Command...............   5-11 I               5.11.6    Configuring a Node as a DECdns Server.....   5-11 I               5.11.6.1    Creating A New Namespace................   5-12     I                                                                         v                    <           5.11.7    Default Parameters for Process Limits onE                     DECdns Servers............................   5-12 E           5.11.8    PAGEDYN Resources: Clerks and Servers.....   5-13 =           5.11.9    Use the Outgoing Alias When Connecting to E                     DECdns Servers............................   5-13 E           5.12  DECdts........................................   5-14 <           5.12.1    Automatic Time Zone Changes on RebootingE                     Clusters..................................   5-14 E           5.13  OSAK Programming..............................   5-14 E           5.13.1    User Data Size Restriction for Tracing....   5-14 E           5.13.2    OSAK Version 1.1 No Longer Supplied.......   5-14 >           5.13.3    Migrating Applications from Version 2.0 toE                     Version 3.0 OSAK API Interface............   5-14 6           5.13.4    Misleading OSAK Error Message: SPME                     Congestion at Connect Time................   5-15 E           5.14  DECnet Programming............................   5-15 E           5.14.1    64-Bit Virtual Address Restrictions.......   5-15 E           5.14.2    Backtranslation of IP Addresses...........   5-15 E           5.14.3    Applications Connection Requirement.......   5-16 ;           5.15  FTAM, Virtual Terminal, and OSI Application E                 Kernel........................................   5-16 E           5.15.1    FTAM......................................   5-16 6           5.15.1.1    Downstream Processing Support inE                       OSIF$FAL................................   5-16 E           5.15.1.2    COPY Command Enhancement................   5-17 E           5.15.1.3    DAP/Gateway.............................   5-17 0           5.15.1.4    RMS Record I/O PerformanceE                       Enhancements............................   5-17 E           5.15.2    Virtual Terminal..........................   5-18 E           5.15.2.1    CTRL-@..................................   5-18 E           5.15.2.2    Amode Repertoire........................   5-18 E           5.15.2.3    Responder...............................   5-18 E           5.15.2.4    VT/LAT Gateway..........................   5-18        6  Known Problems   E           6.1   NET$SHUTDOWN May Fail to Complete.............    6-1 =           6.2   Receive Buffers Attribute on HDLC LINK Entity E                 Not Implemented (Alpha Only)..................    6-1 E           6.3   DECdns........................................    6-2 E           6.3.1     Error Creating New Namespaces.............    6-2 E           6.3.2     System Hangs at Startup in DNS Clerk......    6-2            vi                   <               6.3.3     Server Software Is Not Available forI                         OpenVMS Alpha Systems.....................    6-2 I               6.3.4     Startup Error Message: DECdns Clerk.......    6-2 I               6.3.5     General DECdns Problems...................    6-3 I               6.3.6     Handling Clerk Cache Startup Problems.....    6-3 I               6.3.7     Removing Obsolete DNS$CACHE Files.........    6-4                                                                               I                                                                       vii                              I         _________________________________________________________________   I                                                                   Preface                    Intended Audience   D               This manual is intended for all Compaq DECnet-Plus forE               OpenVMS (formerly DECnet/OSI) software users. Read this G               manual before you install, upgrade, or use Compaq DECnet- ,               Plus for OpenVMS, Version 7.3.           Structure of This Book  :               This manual contains the following chapters:  H               o  Chapter 1 contains installation notes for this release.  G               o  Chapter 2 describes new features not documented in the /                  Version 7.1 documentation set.   F               o  Chapter 3 lists corrections included in this release.  G               o  Chapter 4 contains documentation errata and additions.   E               o  Chapter 5 discusses operational notes and additional D                  product documentation not included in the product's'                  primary documentation.   B               o  Chapter 6 lists known problems with this release.  B               This manual contains release notes introduced in theE               current release and notes from previous DECnet versions D               that still apply to the new release. Each release note@               (except those in Chapter 3) contains a margin note@               indicating in which product version the note first               appeared.   I                                                                       vii                    C           For a list of additional documents available that support <           this version of the Compaq DECnet-Plus for OpenVMS@           software, see the DECnet-Plus for OpenVMS Introduction           and User's Guide.        Reader's Comments   D           Compaq welcomes your comments on this manual or any of theB           DECnet-Plus documents. Please send comments to either of"           the following addresses:  +           Internet    openvmsdoc@compaq.coma  1           Mail        Compaq Computer Corporationa:                       OSSG Documentation Group, ZKO3-4/U08(                       110 Spit Brook Rd.+                       Nashua, NH 03062-2698   )     How To Order Additional Documentation   ;           Use the following World Wide Web address to order #           additional documentation:   (           http://www.openvms.compaq.com/       Conventions   :           The following conventions are used in this book.  E           ___________________________________________________________ E           Convention_______Meaning___________________________________o  @           special type     Indicates a literal example of systemC                            output or user input. In text, indicates D                            command names, keywords, node names, fileC                            names, directories, utilities and tools.S  A           UPPERCASE        Indicates keywords that you enter. YoucB                            can type the characters in uppercase or@                            lowercase. You can abbreviate command=                            keywords to the smallest number ofr@                            characters that OpenVMS, NCP, NCL, or2                            the other tools accept.  @                            Uppercase also indicates the names of@                            files, directories, utilities, tools,@                            commands, parameters, and procedures.       viii o  r            I               ___________________________________________________________hI               Convention_______Meaning___________________________________m  4               italic type      Indicates a variable.  G               bold             Indicates a new term defined in the texto8                                or important information.  G               <Return>         Indicates that you press the Return key.d  G               Ctrl/x           Indicates that you press the Control keyIB                                while you press the key noted by x.  G               [YES]            Brackets indicate that the enclosed itemCD                                is a default value in an installation&                                prompt.  H               { }              In command format descriptions, indicatesA                                you must enter at least one listedNI               _________________element.__________________________________T                                                    I                                                                        ixH E  U                    I                                                                         1 I         _________________________________________________________________U  I                                                              Installationr          0         1.1 OpenVMS Software Version Requirement  B               Compaq DECnet-Plus for OpenVMS, Version 7.3 requiresA               Version 7.3 of the Compaq OpenVMS operating system.y                                                          I                                                          Installation 1-1                          I                                                                         2.I         _________________________________________________________________V  I                                                              New FeaturesE    I               This chapter describes new functionality provided by CompaqgG               DECnet-Plus for OpenVMS Version 7.3 not documented in thePF               Version 7.1 documentation set. This section includes newE               functionality implemented in Version 7.2. Also included.G               is new functionality present in Version 7.1 which was not.>               documented in the Version 7.1 documentation set.  &         2.1 NET$CONFIGURE Improvements  H               The following changes have been made to NET$CONFIGURE.COM:  D               o  The status of both DECnet over TCP/IP (RFC1859) andE                  OSI over TCP/IP (RFC1006) is now included in the OSIr#                  transport summary.   H               o  The OSI transport script contains an explanation of theG                  RFC1006 listener ports attribute so that it is easy tosF                  determine if OSI over TCP/IP or DECnet over TCP/IP is                  enabled..  I               o  When FDDI routing circuits are present, a comment in the.H                  Routing script explains if a small or large packet size                  is in use.r  H               o  When using Advanced Option 1 or 4, the entire transportE                  configuration is displayed before asking if the usere%                  wishes to change it.1  +         2.2 Phase IV Migration Improvements.  F               This section describes improvements that enhance a Phase&               IV-to-Phase V migration.  >               The following improvements have been made to the2               NET$CONFIGURE.COM command procedure:  D               o  During migration from Phase IV, Phase IV addressing?                  is no longer disabled on all routing circuits.   I                                                          New Features 2-1  1              New Features'     2.2 Phase IV Migration Improvements2    @              This prevented the newly migrated Phase V node fromA              communicating with Phase IV nodes. Instead, Phase IV.D              addressing is now enabled on one broadcast circuit, andE              a message is displayed which explains how and when Phase A              IV addressing can be enabled on additional circuits.1  B           o  When selecting a broadcast circuit on which to enableC              Phase IV addressing, the migration process now prefers @              FDDI broadcast devices over CSMA broadcast devices.  B           o  During migration from Phase IV, FDDI routing circuits?              are no longer configured with the "Reserved" type. D              Instead, they are configured to use a small packet sizeD              by default (type = csma-cd), and a message is displayedE              which explains how and when that default can be changed.   :           The following improvements have been made to the)           NET$CONVERT_DATABASE.EXE image:.  C           o  EI/82558, EB, and EO devices are now recognized during %              migration from Phase IV.   B           o  All FDDI and CSMA stations are now enabled in the NCLB              scripts regardless of the line states in the Phase IV              line database.e  >     2.3 NET$SHUTDOWN_APPLICATION Logical Added to NET$SHUTDOWN  :           NET$SHUTDOWN now checks for the existence of the>           NET$SHUTDOWN_APPLICATION logical. If this logical isB           defined, NET$SHUTDOWN invokes the site-specific shutdown?           command procedure referenced by the logical. This new-E           logical does not change the function of the NET$AUX_CONTROL-           logical.  %     2.4 NCL$GLOBALSECTION.DAT Updated.  D           NCL$GLOBALSECTION.DAT has been modified to include changesD           needed to manage the Message Transfer Agent (MTA), MessageD           Transfer Server (MTS), Directory Services Agent (DSA), and!           X.25 over TCP/IP (XOT).i             2-2 New Features .  .      I                                                              New Features3I                                                      2.5 NCL HELP Updates              2.5 NCL HELP Updates  D               This release includes several updates to NCL HELP. The:               sections that follow describe these changes.  #         2.5.1 Improved OrganizationX  I               NCL HELP utility has been reorganized to include additional G               network management information, diagrams and descriptions <               of the entity hierarchy, and command examples.  F               The Network_Management topics now contains the followingD               subtopics: Controlling_Access, Logical_Names, Startup_C               Scripts, MOP, Event_Dispatcher, Shutdown_and_Restart, D               Running_over_TCP_IP, Namespace_Management, and Remote_               Node_management.  D               The new entity hierarchy diagrams and descriptions are3               accessed using the following command:i  1               HELP ENTITY module-name SUBENTITIES   C               You can view the entire entity hierarchy by using then                following command:                 HELP ENTITY   (         2.5.2 Help for SHOW DTSS Updated  H               In Version 7.1, the syntax for the SHOW DTSS LOCAL SERVERSG               and SHOW DTSS GLOBAL SERVERS commands changed in order to(F               distinguish DECnet servers from DCE servers. The updatedD               help file contains the new versions of these commands:H               SHOW DTSS DECNET LOCAL SERVERS and SHOW DTSS DECNET GLOBAL               SERVERS.  >         2.5.3 Updated Information for Access Control and Proxy               Information.  G               NCL HELP has been updated to more clearly describe accesslD               control policies, especially with regard to the use ofG               wildcard proxies. Note that there has NOT been any recentmI               change to DECnet's access control checking procedures; this.?               HELP update is merely for documentation purposes.   I                                                          New Features 2-3                 New Features     2.5 NCL HELP Updates    @           The following text is now included under HELP NETWORK_3           MANAGEMENT ACCESS_CONTROL OPENVMS_POLICY:r  A           Access can be established using an explicitly specified.C           account, a default proxy account, an application-specificlC           default account, or a nonprivileged default account.  Thef@           following steps are used to determine if a remote userE           will be granted access.  (Note that access control checking1G           is handled in the same fashion for a local user who specifies.,           the local node or 0 in a command.)  I              1.  If explicit access control information is provided, this.0                  information is evaluated first.  H                  When an empty access control string is provided, as in:  !                  $ DIR PRKCHP""::                   $ DIR 0""::  J                  No proxy checking is performed.  Instead, access checking(                  is continued at Step 3.  K                  When both a username and password are explicitly provided, .                  as in the following examples:  3                  $ DIR PRKCHP"PRKCHP_USER PASSWD":: .                  $ DIR 0"PRKCHP_USER PASSWD"::C                  $ MCR NCL SHOW NODE PRKCHP"PRKCHP_USER PASSWD" ALL   M                  that account must be accessible using that password (even if K                  a valid proxy exists), in order for access to succeed.  If.K                  this fails (say, for example, the password is wrong or thesE                  account does not exist), then no further checking is.0                  performed and access is denied.  F                  When only the username is explicitly provided, as in:  ,                  $ DIR PRKCHP"PRKCHP_USER"::'                  $ DIR 0"PRKCHP_USER"::.<                  $ MCR NCL SHOW NODE PRKCHP"PRKCHP_USER" ALL  J                  the local proxy database is searched for one proxy recordF                  matching source_node::username_on_source.  An exactlyJ                  matching proxy record is preferred over a wildcard match.I                  (Refer to HELP NETWORK_MANAGEMENT ACCESS_CONTROL PROXIESsF                  for more information if a wildcard proxy is present.)E                  If a match is not found, then no further checking is.0                  performed and access is denied.       2-4 New Features 1         I                                                              New Features I                                                      2.5 NCL HELP Updates5    O                      If a match is found, the selected proxy record is examined.J                      to determine if access should be attempted using thisF                      explicitly specified local username.  It does notL                      matter if this local username is specified in the proxyK                      record as the default account or not.  As long as that N                      username is included somewhere in that proxy record, then?                      access will be attempted via that account.   P                      For example, if the following command were issued by SYSTEM                      on LAMCHP:1  0                      $ DIR PRKCHP"PRKCHP_USER"::  M                      And PRKCHP had one of the following proxy records in its.                      database:  #                      LAMCHP::SYSTEM.#                         PRKCHP_USERT  #                      LAMCHP::SYSTEM '                         PRKCHP_USER (D)   #                      LAMCHP::SYSTEMl1                         SYSTEM (D)    PRKCHP_USERu  H                      Then access would be attempted using the explicitly3                      specified PRKCHP_USER account.d  P                      If this access succeeds, the remote user is mapped into theI                      specified account and granted the rights and default N                      privileges for that account.  If there is a problem (say,N                      for example, the directory for that account does not haveN                      the correct owner), then no further checking is performed*                      and access is denied.  N                  2.  If no access control information was provided at all (not2                      even an empty string), as in:  #                      $ DIR PRKCHP::                       $ DIR 0::3                      $ MCR NCL SHOW NODE PRKCHP ALL   N                      The proxy database is scanned for a proxy record matchingP                      source_node::username_on_source.  (A default wildcard proxyL                      may not be sufficient. Refer to HELP NETWORK_MANAGEMENTB                      ACCESS_CONTROL PROXIES for more information.)  F                      If no matching proxy record is found, then access9                      control checking proceeds to Step 3.f  I                                                          New Features 2-5o n  l           New Features     2.5 NCL HELP Updates    E                  If a matching proxy record is found, but it does not C                  specify a default account, then access will NOT be G                  attempted using that proxy.   Instead, access checking $                  proceeds to Step 3.  J                  If the matching proxy record specifies a default account,F                  then access is attempted using that account.  If thisE                  succeeds, the user is granted the rights and default I                  privileges of this default account.  If this fails (say, E                  for example, the directory for that account does not I                  have the proper owner), then no further checking is doneo&                  and access is denied.  B              3.  If an application-specific default is present, asG                  indicated by the session control application user name D                  attribute, then access will be attempted using thatF                  account.  If this access fails (say, for example, theD                  specified account is non-existent), then no further<                  checking is performed and access is denied.  @                  If no default was specified for that particularG                  application, access checking is continued with Step 4.h  1                                      --- NOTE ---   ?                  The CMIP Management Listener (CML) applicationGD                  uses this method of access to allow remote users toD                  perform NCL SHOW commands.  This is why the sessionD                  control application CML user name is usually set toB                  CML$SERVER, and this account is generally grantedC                  the NET$EXAMINE right.  Even if a remote user doesaC                  not include explicit access control information in B                  an NCL command, and even if he does not possess aB                  default proxy account with NET$EXAMINE or BYPASS,B                  his NCL SHOW requests will still be permitted via(                  the CML$SERVER account.  B              4.  If a non privileged default has been established,C                  as indicated by the session control non privileged_D                  user attribute, then access will be attempted using?                  that account.  If this access fails, or if the B                  session control non privileged user attribute has5                  not been set, then access is denied.w         2-6 New Features           I                                                              New Features I                                                      2.5 NCL HELP Updatesc    D               The following text is now included under HELP NETWORK_H               MANAGEMENT ACCESS_CONTROL PROXIES to describe why wildcardD               proxies are sometimes ignored during proxy evaluation:  N                  Proxies are managed using the AUTHORIZE facility.  Each proxyO                  record should specify a default account, regardless of whether M                  a default wildcard proxy exists, to ensure that at least onerK                  valid destination account is specified.  For example, if a_:                  default wildcard proxy existed on PRKCHP:  "                  UAF> SHOW/PROXY *  6                   Default proxies are flagged with (D)                    LAMCHP::*                      * (D)  O                  The SYSTEM user on node LAMCHP would have default proxy access 3                  into the SYSTEM account on PRKCHP.   J                  If the network manager then wished to add ALTERNATE as anP                  alternate account to be used from the SYSTEM account on LAMCHP,N                  while still retaining SYSTEM as the default, he would need toQ                  explicitly specify that default in the new proxy record like so:n  H                  UAF> ADD/PROXY LAMCHP::SYSTEM SYSTEM/DEFAULT, ALTERNATE  J                  So the proxy database on PRKCHP would now look like this:  "                  UAF> SHOW/PROXY *  6                   Default proxies are flagged with (D)                    LAMCHP::*                      * (D)                    LAMCHP::SYSTEM -                      SYSTEM (D)     ALTERNATE   (                  If he instead did this:  8                  UAF> ADD/PROXY LAMCHP::SYSTEM ALTERNATE  8                  So the proxy database looked like this:  "                  UAF> SHOW/PROXY *  6                   Default proxies are flagged with (D)                    LAMCHP::*                      * (D)  I                                                          New Features 2-7                 New Features     2.5 NCL HELP Updates                  LAMCHP::SYSTEM                   ALTERNATE  D              then LAMCHP::SYSTEM would no longer have default accessH              to PRKCHP's SYSTEM account.  That is because only one proxyI              record is considered for proxy processing; and in this case,_A              the exact match LAMCHP::SYSTEM is preferred over the H              LAMCHP::* match.  This LAMCHP::SYSTEM proxy record does not)              specify any default account.   E              For further information on how proxies are used to granttD              access, refer to HELP NETWORK_MANAGEMENT ACCESS_CONTROL              OPENVMS_POLICY.  <     2.5.4 Updated Help for FDDI Station Link Event Reporting  <           NCL HELP EVENT_MESSAGES FDDI_STATION LINK has beenD           updated to reflect restrictions in FDDI Station Link event@           reporting which are imposed by the VMS device drivers.  E           The following events cannot be logged, but their respectivea8           counters will increment if these events occur:                block check error%              directed beacon received +              duplicate address test failuree%              duplicate token detectedn              fci strip error              frame status error $              link buffer unavailable              pdu length error !              receive data overrun "              ring beacon initiated              ring purge error               trace initiated              transmit failurex              transmit underrun  8           The "unrecognized individual pdu destination",D           "unrecognized multicast pdu destination", and "user bufferC           unavailable" events can be reported, and their respective C           counters can increase accordingly. However, DECnet blockstD           "unrecognized multicast pdu destination" by default. ReferE           to SYS$MANAGER:NET$EVENT_LOCAL.TEMPLATE if you wish to passl           this event.        2-8 New Features           I                                                              New FeaturesaI                                                      2.5 NCL HELP Updateso    ;               The "ring initialization initiated" and "ring G               initialization received" events are now logged by certainsG               VMS device drivers. If a VMS device driver supports theseiD               events, they are not logged on a one-to-one basis withF               increases in their corresponding counters. Instead, onlyG               one error report is issued for any number of these eventshF               that occur within a sampling period. This is intended to9               decrease any possibility of flooding OPCOM.i  (         2.6 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 failedeE               with the following messages displayed at the satellite:   U               %VMScluster-I-MSCPCONN, Connected to a MSCP server for the system disk,s                 node nnnnnnpS               %VMScluster-E-NOT_SERVED, Configuration change, the system disk is non,                 longer served by node nnnnnn  +         2.7 Host Based Routing Improvements,  H               This release of the NET$ROUTING_IS.EXE module contains the%               following improvements:   C               o  Raised the maximum allowed circuits from 20 to 40.s  H               o  Modified logic used to set maximum circuit segment sizeE                  for FDDI circuits. Previously, the calculation couldEI                  sometimes use the Phase IV default of 576. This has beenI@                  changed to always use the FDDI default of 4352.  (         2.8 Session Control Improvements  I               This release of the NET$SESSION_CONTROL.EXE module contains (               the following improvement:  I               o  On Alpha systems, the NET$SESSION_CONTROL.EXE module now E                  uses the name string from the PSB instead of GETJPI.           I                                                          New Features 2-9S e  M           New Features+     2.9 CDI$SYSTEM_TABLE Logical Name Table(    +     2.9 CDI$SYSTEM_TABLE Logical Name Table   @           You can use a logical name table (CDI$SYSTEM_TABLE) toE           define node synonyms. You should use the following commandsHD           to create and examine logical names in a CDI$SYSTEM_TABLE.D           For example, you can define a system named bks.pub.dec.com=           as bks according to the following command examples.d  9           To define a table, enter the following command:r  O           $ create/name_table/exec/parent=lnm$system_directory cdi$system_tablea  @           To define a logical name, enter the following command:  =           $ define/table=cdi$system_table bks bks.pub.dec.com   A           To examine a logical name, enter the following command:L  3           $ show logical/table=cdi$system_table bksn  ;           The system displays the logical name information:r  8           $ "bks.pub.dec.com" = "bks" (cdi$system_table)  0           SYSNAM system privileges are required.  &     2.10 Backtranslation Over DNS/BIND  @           Incoming connections over an IP network might not work>           with applications that require a Phase IV-style (sixA           character or less) node name unless Domain synonyms areoC           set up as described in the Compaq DECnet-Plus for OpenVMST           installation manuals.r  D           CDI now attempts to backtranslate the IP address using theE           first simplename in the fully qualified DNS/BIND host name.iA           For example, NOTAMI.div.cmp.com translates into NOTAMI. D           If the first simplename is not a legal Phase IV-style nodeE           name, such as NOTAMI2.div.cmp.com, backtranslation is still            provided.        2.11 OSAK Programmingo  A           The following sections discuss new programming features 7           that apply to the OSAK programming interface.s       2-10 New Features  i  s      I                                                              New Features I                                                     2.11 OSAK Programmingt    @         2.11.1 called_aei Parameter on A-ASSOCIATE and S-CONNECT                 Indication Events  @               For A-ASSOCIATE indication events in the OSAK API,B               and S-CONNECT indication events in the SPI, the nsapC               field of the called_aei parameter is no longer filled B               in by OSAK. Previously, the called_aei.paddress.nsapD               structure contained the values specified in the local_G               aei.paddress.nsap parameter on the osak_open_responder ornI               spi_open_responder call. However, these values are not used F               by osak_open_responder or spi_open_responder and may notG               contain correct information about the received connectioni0               (for example, the transport type).           2.11.2 New Status Code  C               The routines osak_send_more and spi_send_more can nowiC               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.  /         2.11.3 ROSE Minimum Workspace Increasedn  I               The minimum required size for the parameter block workspaceiG               for ROSE has increased. If your ROSE application is using D               the old minimum workspace size, you will now get a badF               parameter error. It is recommended that your applicationH               use the constant ROSE_WS_SIZE defined in osak_api.h to get1               the correct minimum workspace size.v  F                 ________________________ Note ________________________  E                 Depending on the size of your application's parameter D                 block workspace, you may have to recompile your ROSE                 applications.d  F                 ______________________________________________________  6         2.11.4 Handling of Default Transport Templates  @               If no transport template is specified in the osak_I               associate_req (API and ROSE) or spi_connect_req (SPI) call,s/               OSAK takes the following actions:   G               o  If the NSAP in the osak_nsap data structure is CONS orm@                  CLNS, OSAK uses the default transport template.  I                                                         New Features 2-11     f           New Features     2.11 OSAK Programming)    E           o  If the NSAP in the osak_nsap data structure is RFC 1006, ;              OSAK uses the osit$rfc1006 transport template.        2.12 DECdns            2.12.1 New Device Support   D           This version of DECdns provides support for EB, EI, and EO           Ethernet devices.L       2.12.2 DNS Logging Enhanced   ;           The option to include more communications logging.>           information in the SYS$MANAGER:DNS$CHFAIL.LOG is nowC           available. Prior to this enhancement, hard communicationseB           errors were only reported to the DNS$CONTROL program andD           the DECnet-Plus IPC status was lost. With this new featureB           enabled, these errors are reported to the DNS$CHFAIL.LOG2           (along with the DECnet-Plus IPC status).  C           To enable this feature, define the logical name DNS$MORE_ C           COMMO_LOGGING in the DNS$SYSTEM_TABLE and give it a valueM            of one as shown below:  @           DEFINE/TABLE=DNS$SYSTEM_TABLE DNS$MORE_COMMO_LOGGING 1  =           To disable this feature, deassign the logical name..  ,     2.12.3 New System Logicals for DNS$ADVER  C           Five new user-defined system logicals have been added for             the DNS$ADVER process:              o  DNS$ADVER_AST_LIMIT  #           o  DNS$ADVER_BUFFER_LIMITE             o  DNS$ADVER_EXTENTM  &           o  DNS$ADVER_MAX_WORKING_SET              o  DNS$ADVER_PAGE_FILE  @           These system logical names correspond to qualifiers on>           the RUN statement which are described in the OpenVMSA           documentation. If any of these system logical names ared?           defined at the time that the DNS$ADVER process starts >           up, then the values defined for these system logical       2-12 New Featurese r  o      I                                                              New FeaturesrI                                                               2.12 DECdns     F               names are used instead of the default quotas. Typically,@               these system logical names are defined in the file)               SYS$MANAGER:SYLOGICALS.COM.   A               Use these system logical names if you have a system I               configured with more than two ethernet controllers. You cancG               also use these logicals to define increased quota for theiI               DNS$ADVER process when you receive a message on the consoleWI               during startup that the DNS cache is not initialized (DNS$_a5               NOCACHE,"Clerk cache not initialized").o  D               Selected default quotas for the DNS$ADVER process haveG               also been increased for this release. The selected quotasNI               that have been increased include direct I/0, enqueue limit, A               queue limit, buffer limit, and maximum_working_set.e           2.13 DECdts   !         2.13.1 New Device Supports  H               This version of DECdts provides support for EB, EI, and EO               Ethernet devices.o  E         2.13.2 New Procedures for Changing Daylight Savings Time Zonee!                Rules (Alpha Only)   I               This version of DECdts (Alpha only) uses the timezone filescI               provided by the DEC C RTL. These timezone files are locatedeH               in the directories pointed to by the logical SYS$TZDIR. IfH               there is an error in any of these files you can correct itF               by using the update procedure given in the next section.  )               Updating the Time Zone Filea  F               The time zone source files are a database which providesI               information about time zone rules in the past, present, andn>               future for virtually every country in the world.  @               The time zone source files are updated as follows:  E               1. Modify the appropriate time zone source file so that E                  it reflects the new rule. Time zone source files aresE                  located in SYS$COMMON:[SYS$ZONEINFO.SYSTEM.SOURCES].eF                  The format of the time zone source files is describedB                  in the DEC C Run-Time Library Utilities ReferenceH                  Manual. Please refer to the section describing the Zone,                  Information Compiler (ZIC).  I                                                         New Features 2-13u    e           New Features     2.13 DECdtsS    B           2. Recompile the modified time zone source file with theC              ZIC compiler. The ZIC compiler is available on OpenVMSuB              V7.0 and above. It is described in the DEC C Run-Time0              Library Utilities Reference Manual.  B           3. Make sure that the new binary time zone file is being@              used by applications. To make use of the new binaryE              time-zone file, the user should place it in the locationg7              referred to by the SYS$TZDIR logical name.i  C              ________________________ Note ________________________r  ?              The DEC C RTL has the ability to cache environmentc?              variables and binary time-zone files. This cachingn@              may prevent either the newly defined TZ environment>              variable or the newly created time-zone file from?              taking effect. The simplest way to ensure that the 9              change takes effect is to reboot the system.   C              ______________________________________________________t  >           To verify that the rule is set up correctly, use the           following command:  "           $ SHOW LOGICAL SYS$TIME*  @           For example, the output might look like the following:  .           "SYS$TIMEZONE_DAYLIGHT_SAVING" = "1"0           "SYS$TIMEZONE_DIFFERENTIAL" = "-14400"%           "SYS$TIMEZONE_NAME" = "EDT"e?           "SYS$TIMEZONE_RULE" = "EST5EDT4,M4.1.0/02,M10.5.0/02"h  B           The SYS$TIMEZONE_RULE is a POSIX-style rule. POSIX-style=           rules are discussed in the section below. This rulexA           corresponds to the value of the TZ environment variable (           that is found on UNIX systems.  @           The SYS$TIMEZONE_DIFFERENTIAL is the time differentialC           (expressed in seconds) from GMT. The time differential iso<           the time you add to GMT to compute the local time.  :           Format of the SYS$TIMEZONE_RULE POSIX-style Rule  C           The material presented here was extracted from the Compaqt+           Tru64 UNIX manual page for tzset.   ;           stdoffset[dst[offset] [,start[/time],end[/time]]]   6           The components of the string are as follows:       2-14 New Features            I                                                              New Features I                                                               2.13 DECdts                    std and dst C               Three or more characters that are the designation for E               the standard (std) or alternative (dst) time zone (suchED               as Daylight Saving Time). Only std is required. If dstE               is not supplied, the alternative time does not apply toTF               the locale. Upper- and lower-case letters are explicitlyE               allowed. Any characters, except digits, a leading colonxE               (:), comma (,), minus (-), plus (+), and ASCII NUL, are                allowed.                 offsetB               Indicates the value to be added to the local time toB               arrive at GMT. The offset has the form hh[:mm[:ss]].F               The minutes (mm) and seconds (ss) are optional. The hourG               (hh) is required and can be either one or two digits. TheiI               offset following std is required. If no offset follows dst,sE               the alternative time is assumed to be one hour ahead ofsF               standard time. One or more digits can be used; the valueG               is always interpreted as a decimal number. The hour value D               must be between zero and 24. The value for the minutesF               and seconds, if present, must be between zero and 59. IfD               preceded by a minus sign (-), the time zone is east ofD               the Prime Meridian; otherwise it is west, which can be5               indicated by a preceding plus sign (+).                  start and end E               Indicates when to change to and return from alternative G               time. The start argument is the date when the change from F               standard to alternative time occurs; end is the date forD               changing back. If start and end are not specified, theI               default is the US Daylight Saving Time start and end dates. H               The format for start and end must be one of the following:  E               Jn        The Julian day n (1 < n < 365). Leap days aretE                         not counted. That is, in all years, including H                         leap years, February 28 is day 59 and March 1 isG                         day 60. It is impossible to explicitly refer tod$                         February 29.  E               n         The zero-based Julian day (0 < n < 365). LeaptG                         days are counted making it possible to refer to $                         February 29.      I                                                         New Features 2-15o S  N           New Features     2.13 DECdts       C           Mm.n.d    The dth day (0 < d < 6) of week n of month m of B                     the year (1 < n < 5, 1 < m < 12). When n is 5,D                     it refers to the last d day of month m which mayB                     occur in either the fourth or fifth week. WeekD                     1 is the first week in which the dth day occurs.'                     Day zero is Sunday.e             timeA           Describes the time when, in current time, the change to D           or return from alternative time occurs. The time parameterA           has the same format as offset, except that there can beu?           no leading minus (-) or plus (+) sign. If time is noti-           specified, the default is 02:00:00.              Sample Rulei  .           As an example, the TZ variable value?           EST5EDT4,M4.1.0,M10.5.0 describes the rule defined int@           1987 for the Eastern time zone in the US. EST (EasternD           Standard Time) is the designation for standard time, whichC           is 5 hours behind GMT. EDT (Eastern Daylight Time) is thelC           designation for alternative time, which is 4 hours behindsB           GMT. EDT starts on the first Sunday in April and ends onC           the last Sunday in October. In both cases, since time wasoE           not specified, the changes occur at the default time, whicheE           is 2:00 A.M. Note that the start and end dates did not need 6           to be specified since they are the defaults.  0     2.13.3 Option to Disable DTSS at System Boot  D           You can now disable DTSS when the system boots. You shouldA           use this option when another time provider controls them:           system clock. To disable DTSS, do the following:  &           1. Boot the system normally.  E           2. Set the TDF using NET$CONFIGURE OPTION 5 (Set Timezone).c:              This allows DTSS to run DTSS$SET_TIMEZONE.EXE<              which sets the EXE$GQ_TDF cell and the SYS$TIMEB              logicals (SYS$TIMEZONE_DAYLIGHT_SAVING, SYS$TIMEZONE_E              DIFFERENTIAL, SYS$TIMEZONE_NAME, and SYS$TIMEZONE_RULE).I  6           3. Disable DTSS using the following command:  #              $ MCR NCL DISABLE DTSS        2-16 New Features            I                                                              New FeaturesrI                                                               2.13 DECdtsB    @               4. Define the following logical in SYLOGICALS.COM:  3                  $ DEFINE/SYSTEM NET$DISABLE_DTSS 1o  #               5. Reboot the system.   G                 _______________________ Caution _______________________   C                 DECnet-Plus requires the TDF to be properly set. Do A                 not attempt to prevent DTSS$SET_TIMEZONE.EXE fromoA                 running; to do so will cause a system hang duringe                 system startup.m  F                 ______________________________________________________  3         2.13.4 New DTSS NTP Provider Sample Programs  G               A new sample program, DTSS$PROVIDER_NTP, may be used on atF               DTSS server to obtain the time from an NTP V3 server (on+               another node in the network).h  8               The new files are located in SYS$EXAMPLES:  B               DTSS$PROVIDER_NTP.C        DTSS NTP Provider Program  @               DTSS$PROVIDER_NTP.EXE      DTSS NTP Provider Image  H               RUN_NTP_TP.COM             Procedure to run DTSS$PROVIDER_,                                          NTP  G               START_DETACHED_NTP_TP.COM  Procedure to run as a detachede0                                          process                          I                                                         New Features 2-17s i  t                    I                                                                         3lI         _________________________________________________________________l  I                                      Corrections Included in This Release.    C               This chapter discusses corrections included in Compaq ?               DECnet-Plus for OpenVMS, Version 7.3. The chapterrE               contains an abbreviated list of the updates included ineC               the Version 7.3 release. If a specific update you are C               looking for is not listed, this does not mean that it E               is not included in the Version 7.3 release. For further1B               information on specific updates, contact your Compaq%               support representative.   &         3.1 Network Management Changes  F               This section describes network management corrections in:               Compaq DECnet-Plus for OpenVMS, Version 7.3.  -         3.1.1 NET$CONFIGURE Command Procedureh  =               The following corrections have been made to the 2               NET$CONFIGURE.COM command procedure:  F               o  If the transport information in the checksum databaseD                  becomes corrupted, NET$CONFIGURE no longer prevents@                  configuration of both transports in the future.  I               o  Creation of the PHONE$SERVER account has been corrected.   I               o  Corrected an error that could result in duplicate device E                  names (and duplicate commands for the devices). This H                  error occurred if NET$CONFIGURE had been previously runE                  and either aborted or was stopped by the user with a H                  CTRL-C. The correction allows NET$CONFIGURE to properly6                  clean up the temporary files it uses.  F               o  Corrected an error in the "ADD an Application" optionA                  that frequently caused this option to generate auE                  RMS warning message and prevented the procedure fromi.                  creating the new application.  I                                  Corrections Included in This Release 3-1s t  S      (     Corrections Included in This Release"     3.1 Network Management Changes    '     3.1.2 NET$STARTUP Command Procedure_  9           The following corrections have been made to then,           NET$STARTUP.COM command procedure:  D           o  No longer requires DNS Server nodes to include LOCAL in              their search path.   E           o  Corrected a condition that could cause the generation of #              the following message:a  P              %DECnet-W-NOREAD, could not read SYS$SYSROOT:[SYSEXE]NET$CONFIG.DAT  E              If this message was received, the SYS$NODE and SYS$NODE_l2              FULLNAME logicals would be undefined.  (     3.1.3 NET$SHUTDOWN Command Procedure  7           The following correction has been made to theA-           NET$SHUTDOWN.COM command procedure:   D           o  Modified to prevent aborting when a NET process logical              was defined.s  *     3.1.4 NCL Syntax Change for MTS Entity  =           The NCL$GLOBALSECTION.DAT file has been modified to @           correct an error with the SET MTS command. Previously,<           the following NCL SET MTS command failed as shown:  9           NCL>set mts "/C=fr/O=mm/MTS=MMmts" ora "C=gb" - K           _NCL>rout inst [action = md redirect, redirection = "C=gb;A=TEST]             %NCL-E-MISSINGRIGHTBKT  ?           To correct this error, it was necessary to modify theO@           syntax of the SET MTS command to include a new routing!           instruction as follows:   9           NCL>set mts "/C=fr/O=mm/MTS=MMmts" ora "C=gb" -EN           _NCL>rout inst [action = md redirect, md redirection = "C=gb;A=TEST]  C           Note that redirection in the action list has been changedn           to md redirection.    ,     3-2 Corrections Included in This Release N  O      I                                      Corrections Included in This Release I                                            3.1 Network Management ChangesO    C         3.1.5 NCL Parsing Fix for End User Specification Data Typesi  I               NCLSHR.EXE has been modified to correct the handling of thenH               UIC format of attributes using the end user spec data typeH               (for example, the remote end user address attribute of theE               session control port entity). Prior to this correction,V/               specifying the following command:_  H               SHOW SESS CONT PORT * ALL, WITH REMOTE END USER ADDR = UIC               = [0,0]SYSTEMc  1               returned the %NCL-E-BADVALUE error.o           3.1.6 Event Dispatcher  B               The following change has been made to the NET$EVENT_#               DISPATCHER.EXE image:   I               o  Created new filters to block the following CSMA and FDDI E                  events to correct the command RESET EVENT DISPATCHER H                  OUTBOUND STREAM. The global filter blocks the following#                  events by default:s  J                  node,csma,station, unrecognized multicast destination pdu>                  node,csma,station, unavailable station bufferO                  node,fddi,station,link, unrecognized multicast pdu destination   F                  If you do not want these events blocked by default atC                  creation time, create a new SYS$MANAGER:NET$EVENT_iF                  LOCAL.NCL by copying the NET$EVENT_LOCAL.TEMPLATE andD                  include appropriate commands to pass one or more of                  these events.  B               The following change has been made to the NET$EVENT_"               LOCAL.TEMPLATE file:  I               o  If a NET$EVENT_LOCAL.NCL was previously created from the F                  old NET$EVENT_LOCAL.TEMPLATE, then your site-specificC                  NET$EVENT_LOCAL.NCL should be edited to remove the 3                  following duplicate block command:u  F                  BLOCK EVENT DISPATCHER OUTBOUND STREAM local_stream -R                      GLOBAL FILTER ((NODE,MOP,CIRCUIT), Unrecognized Dump Client).  H                  Since new filters now block the CSMA and FDDI events byF                  default, the following pass commands have been added:  I                                  Corrections Included in This Release 3-3            (     Corrections Included in This Release"     3.1 Network Management Changes    E              !PASS EVENT DISPATCHER OUTBOUND STREAM * GLOBAL FILTER -gQ              !   ((NODE,CSMA-CD,STATION), Unrecognized Multicast Destination PDU) E              !PASS EVENT DISPATCHER OUTBOUND STREAM * GLOBAL FILTER -hE              !   ((NODE,CSMA-CD,STATION), Unavailable Station Buffer)sE              !PASS EVENT DISPATCHER OUTBOUND STREAM * GLOBAL FILTER -hS              !   ((NODE,FDDI,STATION,LINK), Unrecognized Multicast PDU Destination)   A              If you have previously created a NET$EVENT_LOCAL.NCL ?              script by copying the old .TEMPLATE, regardless ofsD              whether you choose to use these commands or not, pleaseB              update that site-specific NET$EVENT_LOCAL.NCL script.  *     3.1.7 Common Management Listener (CML)  ?           The following correction has been made to the CML.EXE            image:  A           o  Deleted an unnecessary entity name length check that A              could cause remote LAPB management commands (such as1D              SHOW NODE NODEA LAPB LINK * PHYSICAL PORT) to fail withC              a data corruption error. The commands failed when usedZA              with a remote node name but succeeded when used with               NODE 0.  %     3.1.8 Common Trace Facility (CTF)   B           The following correction has been made to the CTFDCP.EXE           image:  @           o  Included a sanity check of the TP_CELL parameter on?              a CTF$$DECLARE call. Invoking CTF with unsupporteddE              parameter values occasionally resulted in a system crasho=              because TP_CELL did not contain a valid address._       3.2 Transport Layer   E           This section describes changes made to the transport layer.   )     3.2.1 Network Services Protocol (NSP)a  9           The following corrections have been made to thee&           NET$TRANSPORT_NSP.EXE image:  D           o  Corrected logic used to ensure that a receive buffer isE              always available. Previously, this logic failed when theb6              number of receive buffers exceeded 32767.  ,     3-4 Corrections Included in This Release r         I                                      Corrections Included in This Release I                                                       3.2 Transport Layerk    G               o  Corrected logic associated with extending the internal D                  TCTB table when the number of transport connectionsC                  exceeds 8191. Previously, a crash would occur with.G                  the NETNOSTATE bugcheck when the number of connectionss                  exceeded 8191.e  G               o  Prevent a remote TCID from attempting to be reused forhE                  a connection if the previous connection failed to be                   deaccessed.  D               o  Brought NSP more in line with the Phase IV protocolG                  by correcting the possible delivery of protocol errorsmG                  with disconnect data. If the user string (P2) is not atG                  counted string, this will now be included on behalf ofCH                  the user. Phase IV did this previously, but removed theE                  first byte of the user data while making it counted.o  $         3.2.2 OSI Transport Protocol  =               The following corrections have been made to the *               NET$TRANSPORT_OSI.EXE image:  D               o  Modified state tables such that if the port is in aI                  WFNC state and receives a DR or DC, the port ignores the /                  message rather than bugchecks.a  1               o  Corrected restraint mode window.   C               o  Corrected default packet size (from 7 to 128) when .                  remote fails to set the size.  H               o  Prevent OSITP retransmission timeouts with zero credit.  ;               o  Prevent OSITP premature port deallocation.s  G               o  Corrected I/O completion processing to verify the VCIBAC                  prior to using a field in the VCIB as a completion !                  routine address.d  >               o  Prevent possible system crash on a disconnect                  indication.        I                                  Corrections Included in This Release 3-5  )         (     Corrections Included in This Release     3.2 Transport Layerf    #     3.2.3 DECnet over IP (RFC 1006)l  9           The following corrections have been made to theb           NET$TPCONS.EXE image:   C           o  Corrected I/O completion processing to verify the VCIB ?              prior to using a field in the VCIB as a completion               routine address.a  :           o  Prevent possible system crash on a disconnect              indication.       3.3 Network Layer   @           This section describes corrections made to the network           layer.       3.3.1 End System Routing  9           The following corrections have been made to then#           NET$ROUTING_ES.EXE image:   A           o  Corrected handling of routing circuit reenable timerv@              expirations to prevent a system crash that occurredC              when the timer handler attempted to reenable a deleted               circuit.   A           o  Corrected Phase V to Phase IV translation padding on               transmit header.S  B           o  Prevent possible shutdown crash on disable when a WCB?              contained an unexpected Routing Routine, net$clns_hA              transmit_discard. Clear the CLNS_CDB before deleting -              the TSEL in the CLNS port close.   @           o  Prevent invalid NSAP on initial ES hello message byE              checking the area address and not the HIORD of the NSAP.r       3.3.2 Host Based Routing  9           The following corrections have been made to thea#           NET$ROUTING_IS.EXE image:   C           o  Prevent a possible crash in the GetBuffer routine when +              allocating forwarding buffers.   .           o  Corrected alias forwarding logic.  B           o  Prevent a possible shutdown crash when the alias port              was deallocated.a  ,     3-6 Corrections Included in This Release           I                                      Corrections Included in This Release I                                                         3.3 Network Layer     7               o  Prevent possible crash with X.25 PVCs.f  A               o  X.25 circuit enable code was modified to preventi<                  possible corruption if the X.25 channel was                  disconnected.  G               o  Modify the use of R9 to avoid corruption in LES (Alpha                   only).a  A               o  Remove possible alias_IDdisable forced bugcheck.)  H               o  Prevent possible system crash in net$fwd_pkt_GetBuffer.           3.3.3 Aliasp  =               The following corrections have been made to the "               NET$ALIAS.EXE image:  @               o  Corrected incoming selection weight on objects.  C               o  Corrected object lock conversion for alias enable.t           3.4 Session Controls  =               The following corrections have been made to the ,               NET$SESSION_CONTROL.EXE image:  G               o  Corrected logic in the session I/O completion routineseD                  to allow session I/O to properly complete even whenI                  session is in the off state. Occasionally, the transportcH                  module would complete I/O after session had entered theF                  off state. Session control treated this as an invalid1                  condition and forced a bugcheck.o  H               o  Corrected a situation where session control could leaveF                  connections active even after VAX P.S.I. applicationsE                  (using GAP) properly disconnected during applicationrI                  termination. The application $CANCEL request was failingnG                  because the connection was already in the disconnected E                  state. The code has been modified to treat a $CANCELcE                  request in the disconnected state in the same mannerTF                  as it does for the running state. This replicates the,                  behavior found in Phase IV.  F               o  Conditionalize out SCL spinlock checking because this'                  check is now obsolete.   I                                  Corrections Included in This Release 3-7            (     Corrections Included in This Release     3.4 Session ControlS    ?           o  Prevent crash in NET$ACP from a bad DECdns and CDIo@              cache entry. A stale pointer in DNSResult[DNSREQ$A_?              Pointer] with ACP$CheckBackTransTask could cause a !              double deallocation.   B           o  Prevent SMP PGFIPLHI crash that could occur trying to6              access a port EIB that no longer existed.  D           o  Correctly include proxy information for use by LOGINOUT>              when SYSGEN parameter NET_CALLOUTS is set to 255.       3.5 QIO InterfaceD  9           The following corrections have been made to thee           NET$DRIVER.EXE image:b  A           o  Prevent possible application RWAST or network deviceP=              hangs with QIOUCB$V_closeassocdone. Double close C              associations precipitated this modification. Both QIO_ E              EXECUTE and QIO_COMPLETION were modified to check if the C              association has already been closed and if the channel %              can then be deallocated.   ?           o  Modified disconnect data counted string to emulate ?              Phase IV behavior of stepping on the first byte oftD              user data to make it a counted string (only if the user?              application does not supply this necessary count).   <           o  Corrected ExecuteDeaccess code latency when the?              connection was not yet in the run state and it was A              aborted. This allows the abort to happen immediately_@              if a) the channel type indicates that there is someA              semblance of a connection and b) the state indicatesoA              that the connection is not already in the process ofi              being torn down.   ?           o  Prevent IPCACP from trying to $ASSIGN a NET device 4              before the driver has been initialized.              ,     3-8 Corrections Included in This Release t  a      I                                      Corrections Included in This Release1I                                 3.6 Maintenance Operations Protocol (MOP)     1         3.6 Maintenance Operations Protocol (MOP)   I               The following corrections have been made to the NET$MOP.EXE                image:  E               o  Prevent a KRNSTAKNV crash with DECthreads changes in$                  V7.2-1.  H               o  The following MOP CCR protocol corrections are included!                  in this release:r  H                  -  MaxCommand from the SYSID now determines the maximumH                     CommandPoll data size. This prevents commands longerF                     than 16 bytes from being unnecessarily broken into&                     separate messages.  E                  -  If a RespAck is transmitted just as the thread is G                     timing out, MOP no longer gets stuck in "retransmitc                     mode".  D                  -  MOP no longer inappropriately reuses CommandPoll$                     message numbers.  A                  -  The retransmit count is now only cleared if a.B                     matching RespAck has been received and MOP has9                     finished processing any pending VCRP.r  A                  These problems had a very negative impact on SETtG                  HOST/MOP and TSM performance. They remained undetectedrF                  until the CCR timer was recently decreased to improveD                  performance for the TSM SHOW SERVER ALL command. AtC                  faster speeds, MOP was more likely to get stuck indE                  "retransmit mode", often leading to CCR-E-NORESOURCE$C                  or TSM-S-NO_RSP_DATA error messages. This occurrede;                  primarily when DECserver 200s were in use.r  F                  Now that these corrections have been implemented, theC                  CCR timer has been reduced to improve performance.iE                  (This timer is used by MOP to determine how long theaE                  thread should wait for a response.) The CCR timer isXE                  calculated using the mop circuit entity's retransmitNC                  timer attribute. The default for this attribute is.F                  4, but setting this attribute to 1 may provide better@                  performance (if there aren't any DECserver 200s                  present).  I                                  Corrections Included in This Release 3-9d n  s      (     Corrections Included in This Release+     3.7 Distributed Naming Service (DECdns)s    +     3.7 Distributed Naming Service (DECdns)t         3.7.1 Clerk Changesu  ?           The following corrections have been made to the clerk             (DNS$ADVER.EXE) image:  E           o  Corrected a situation where NSAP's with a prefix of %x49tA              were being inserted in the cache when the configured (              prefix was other than %x49.  ?           o  Corrected a situation where the STICKY bit was notiC              preserved in the cache (if it was previously set) when =              the address of an item in the cache was updated.L  D           o  Corrected a problem that caused the clerk to crash whenD              a "SHOW DNS CLERK REMOTE CLEARINGHOUSE ..." command wasE              issued. This problem sometimes appeared as a hang to theaC              user when a command similar to the one shown above wasc              issued.  C           o  Corrected the clerk (SYS$NAME_SERVICES.EXE) to preventnD              a crash. The symptom of this crash is that the variableB              CTL$GL_DNSPTR is zero when entering routine RECEIVED_              DISCONNECT_AST.  ?           o  Corrected the DNS$ADVER process to prevent it from A              aborting. The symptom of this aborting process is aneA              access violation on a call to the DECC$FREE routine.i  #     3.7.2 Server Changes (VAX Only)o  @           The following corrections have been made to the server"           (DNS$CONTROL.EXE) image:  B           o  Corrected the clerk treewalk algorithm to prevent theE              algorithm from failing to find the desired clearinghousee?              to satisfy the name lookup request. Typically, theaC              symptom of this problem was the return status of DNS$_SC              NOCOMMUNICATIONS on a "SHOW CLEARINGHOUSE ..." commandE@              when the clerk should have been able to connect the"              proper clearinghouse.    -     3-10 Corrections Included in This Releases s  i      I                                      Corrections Included in This ReleasenI                                   3.7 Distributed Naming Service (DECdns)i    <               o  Added the ability to detect a newly createdG                  clearinghouse object that is missing a valid DNA$TOWERrE                  and/or DNS$ADDRESS attribute. When this situation isnD                  detected by the BACK_GROUND thread (which runs on aI                  hourly basis), it is corrected by updating both of these 1                  attributes to the correct value.E  E                  Typically, this situation can occur when someone has$B                  accidentally deleted the clearinghouse object andE                  the clearinghouse object is manually recreated. ThisNH                  situation is discussed in the Section 12.10, "RestoringF                  a Missing Clearinghouse Object Entry", of the DECnet-(                  Plus DECdns Management.  H               o  Adjusted the server quota and timeout default values toG                  handle the average size configuration. The changes arey                  shown below:   I                  ________________________________________________________CI                  Quota/Timeout____Old_Value___New_Value__________________l  1                  idle_conn_       600         300g                  timeout  2                  null_port_       60          1800                  timeout  1                  maximum_         100         200U                  handlers_quotaA  1                  ta_conn_quota    100         200   I                  back_conn_quota__10__________20_________________________S  I                  However, if you have a large configuration, you may have,H                  to adjust some of the above quotas upward. For example,D                  if you have large directories the null_port_timeoutG                  should be adjusted upward. Another example would be torG                  adjust the ta_conn_quota upward, typically for a larget=                  number of users connected to the DNS server.M  A                  When quota or timeout adjustment is required thee?                  new quotas or timeouts can be specified in theaF                  SYS$SYSDEVICE:[DNS$SERVER]DNS.CONF file. This file isE                  only read at server startup time. The server must beL9                  restarted to make the changes effective.   I                                 Corrections Included in This Release 3-11n    e      (     Corrections Included in This Release+     3.7 Distributed Naming Service (DECdns)     D           o  Corrected for bugcheck 704 which caused a server crash.A              This problem only occurred when a connection did notLE              supply all the parameters that the server was expecting.uD              The code has been corrected to handle these connections              properly.  C           o  Corrected the clerk (SYS$NAME_SERVICES.EXE) to provide A              better handling for the expiration of the null_port_sA              timeout. This correction prevents the NEW EPOCH (SET =              DIRECTORY x TO NEW EPOCH ...) and CREATE REPLICA ?              commands from being retried if the link times out.   E              Previously, if the timeout occurred during the NEW EPOCHuD              command processing, you could experience one or more of$              the following symptoms:  D              o  "Directory replicas are not synchronized" message in#                 the DNS$SERVER.LOG.   D              o  "Insufficient local resources at the server" message4                 while using the DNS$CONTROL program.  6              o  Transaction log file (for example: MY_@                 CH.TLOG0000003907) growing to an unusually large                 size.l  B              If the timeout occurred during CREATE REPLICA command@              processing, you would receive the following message1              while using the DNS$CONTROL program:e  Q              Specified clearinghouse already contains a replica of that directoryi  E              The software has been corrected to report the timeout asmD              a communications error ("Unable to communicate with any              DECdns server").c  :              See additional information in Section 5.11.1.  ?           o  Corrected the procedure for counting the number ofnC              skulks initiated. Prior to this correction, if a skulk ?              was already in progress it could have been countedt              twice.k      -     3-12 Corrections Included in This Releasec           I                                      Corrections Included in This ReleaseRI                                     3.8 Distributed Time Service (DECdts)i    -         3.8 Distributed Time Service (DECdts)   =               The following corrections have been made to thea%               DTSS$SERVICE.EXE image:   E               o  Corrected handling of the CHANGE DTSS TIME directivefF                  to properly set up daylight savings time. Previously,E                  if this directive was issued, the change to daylightsH                  savings time did not occur at the specified time unlessI                  the system was rebooted before the daylight savings timet%                  switch was to occur.n  D               o  Corrected a PGFIPLHI crash on startup. The code wasH                  corrected to insure that any linkages which are touchedB                  at an elevated IPL are in a page which is locked.E                  Prevent possible crash on boot in read cluster time.   <               o  Corrected to prevent the clerk from sending9                  advertisements when the cache is purged.r  '         3.9 X.25 Native Mode (VAX Only)E  D               This section describes changes to the X.25 Native Mode6               software (formerly known as VAX P.S.I.).  I               The following change has been made to the PSI$CONFIGURE.EXE                image:  4               o  Provide support for DPGXET profile.  D               The following change has been made to the PSI$LLC2.EXE               image:  :               o  Modified response to DM while link is up.  D               The following change has been made to the PSI$L3CS.EXE               image:  I               o  Modified to no longer pass generated ISO extensions overr4                  GAP. Modified X.29 filter priority.          I                                 Corrections Included in This Release 3-13            (     Corrections Included in This Release;     3.10 Wide Area Network Device Driver Support (VAX Only)     ;     3.10 Wide Area Network Device Driver Support (VAX Only)   A           This section describes changes to the Wide Area Networkt/           Device Drivers (WAN driver) software.n  @           The following change has been made to the SLDRIVER.EXE           image:  A           o  Modified DSB receiver code following an auto-reload.e  7           The following correction has been made to theR!           WANDD$DEVICE.EXE image:o  A           o  Removed race condition in enable with auto-load true E              that prevented a subsequent load from completing on some               fast machines.w                                                          -     3-14 Corrections Included in This Releaset n  a                    I                                                                         4RI         _________________________________________________________________u  I                                                      Documentation Errata     >               This chapter contains corrections to the currentD               documentation set (Version 7.1) for Compaq DECnet-Plus               for OpenVMS.  &         4.1 Network Management and NCL    4         4.1.1 Routing Maximum Buffers Characteristic  C               In the DECnet-Plus Network Control Language Reference ?               manual, the documentation for the maximum bufferseA               characteristic of the routing entity indicates thateB               the characteristic's maximum value is 65535. This isE               incorrect. The maximum value is 500. The characteristic F               sets the number of buffers preallocated, not the maximum@               attainable value. The routing module automaticallyG               allocates additional buffers when all buffers are in use.oE               This was done to conserve on static memory requirements 7               (each buffer is over 4500 bytes in size).   ,         4.1.2 DTS/DTR and Phase V Node Names  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. Then/               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 PhasenH               V node name. To specify a Phase V node on OpenVMS systems,A               you can use a node synonym of 6 characters or less.         I                                                  Documentation Errata 4-1h o  h           Documentation Errata"     4.1 Network Management and NCL    D     4.1.3 Using the ADD Verb with OSI Transport CONS Filter Entities  B           Section 20.1 of the DECnet-Plus Network Control LanguageA           Reference, "osi transport", incorrectly states that thecC           cons filters attribute of the osi transport entity cannot >           be modified unless first disabled. This is partiallyC           correct. You can add filters using the ADD verb while the.E           entity is enabled. To use the REMOVE or SET verbs, you mustd1           first disable the osi transport entity.   $     4.1.4 NET$EXAMINE Right Required  D           Section 1.5.12 of the DECnet-Plus Network Control Language            Reference should read:  D           The NET$EXAMINE right is required to issue SET NCL DEFAULT5           ENTITY and SET NCL DEFAULT ACCESS commands.   .     4.1.5 Configuring Multiple Cluster Aliases  ?           Section 9.2.3, of the DECnet-Plus for OpenVMS Network5D           Management manual, "Configuring Multiple Cluster Aliases",           is incorrect.   B           If you want to set an outgoing alias for an application,$           use the following command:  A           ncl> set session control application application-name -a-           _ncl> outgoingalias name alias-nameh  .     4.1.6 Supplying Access Control Information  >           When supplying access information, both the usernameA           and password should be provided in a single command. IntE           addition, the command should include a default node entity. A           Here are a few recommended forms of the SET NCL DEFAULT            command:  &           NCL>SET NCL DEFAULT ENTITY -I           _NCL>NODE nodename"username password" [subentity | subentities]   O           NCL>SET NCL DEFAULT ENTITY NODE nodename [subentity | subentities], -o9           _NCL>ACCESS BY USER=username, PASSWORD=passwordo  K           NCL>SET NCL DEFAULT ACCESS BY USER=username, PASSWORD=password, -n=           _NCL>ENTITY NODE nodename [subentity | subentities]        4-2 Documentation Errata a  o      I                                                      Documentation Errata I                                            4.1 Network Management and NCLN    A               Once established, default entity and access control C               information remains in effect for the duration of the G               NCL session or until it is modified by subsequent SET NCL                DEFAULT commands..  @               When a SET NCL DEFAULT command contains new accessB               information but lacks a default node entity, the newA               access information is stored, but is not used until D               some subsequent SET NCL DEFAULT ENTITY NODE command isH               issued. For example, the following commands set new accessC               information but do not specify a default entity node:   L               NCL>SET NCL DEFAULT ACCESS BY USER=username, PASSWORD=password  E               NCL>SET NCL DEFAULT ENTITY [subentity | subentities], - =               _NCL>ACCESS BY USER=username, PASSWORD=password   O               NCL>SET NCL DEFAULT ACCESS BY USER=username, PASSWORD=password, -e3               _NCL>ENTITY [subentity | subentities]o  G               The following example shows the result of using a command                of this type.n  "               NCL>SHOW NCL DEFAULT  0               No NCL Default Access has been set#               NCL Default Entity ()   M               NCL>SET NCL DEFAULT ACCESS BY USER=user1, PASSWORD=goodpasswordP"               NCL>SHOW NCL DEFAULT  <               NCL Default Access by User user1, Password xxx#               NCL Default Entity ()   E               Note that the access control information created in the F               preceding commands remains unused until the default nodeF               entity is modified. The following SET command would thenH               result in the establishment of a connection to node remnod&               using the user1 account:  4               NCL>SET NCL DEFAULT ENTITY NODE remnod"               NCL>SHOW NCL DEFAULT<               NCL Default Access by User user1, Password xxx  E               Once you have set a default node entity, all subsequenteG               SET NCL DEFAULT ENTITY [subentity | subentities] commands I               apply to that node until the user modifies the default node F               entity. For example, with the default node entity set to  I                                                  Documentation Errata 4-3     m           Documentation Errata"     4.1 Network Management and NCL    C           remnod, you can set the default entity to Session Controlr?           on node remnod without re-specifying the node entity:e  4           NCL>SET NCL DEFAULT ENTITY Session Control           NCL>SHOW NCL DEFAULT8           NCL Default Access by User user1, Password xxx8           NCL Default Entity Node remnod Session Control  @           To change to another subentity on the remote node, youB           must include (or re-specify) any subentities beneath theE           node entity. Even though the current default entity in thiseE           example is Node remnod Session Control, you must re-specify B           the Session Control subentity if you want to set defaultB           to a lower subentity on that node. For example, NCL doesE           not parse the following command because the Session Control $           entity is not respecified:  4           NCL>SET NCL DEFAULT ENTITY Application fal5           %NCL-E-INVALIDCOMMAND, unrecognized commanda2           SET NCL DEFAULT ENTITY \Application\ fal           NCL>SHOW NCL DEFAULT8           NCL Default Access by User user1, Password xxx8           NCL Default Entity Node remnod Session Control  A           Since the command could not be parsed, the NCL defaultsIB           remained unchanged. Instead, the following command wouldD           be necessary to change the default to a lower subentity on           node remnod:  D           NCL>SET NCL DEFAULT ENTITY Session Control Application fal           NCL>SHOW NCL DEFAULT8           NCL Default Access by User user1, Password xxxH           NCL Default Entity Node remnod Session Control Application fal  ?           Note that in the preceding example the "fal" instancecA           identifier specified a particular instance of a Sessiong?           Control Application. But it is also acceptable to useeA           wildcards to specify the default entity. In the exampleaC           below, the wildcard "*" is used as an instance identifieryE           to refer to all session control applications on the defaultN           node.   B           NCL>SET NCL DEFAULT ENTITY Session Control Application *           NCL>SHOW NCL DEFAULT8           NCL Default Access by User user1, Password xxxF           NCL Default Entity Node remnod Session Control Application *       4-4 Documentation Errata e  o      I                                                      Documentation ErrataaI                                            4.1 Network Management and NCLn    E               Note that if the default access control information and D               the default entity is now modified, but no node entityE               is specified, the old default access control remains inh               effect.   M               NCL>SET NCL DEFAULT ACCESS BY USER=user2, PASSWORD=badpassword,a)               _NCL>ENTITY Session Control "               NCL>SHOW NCL DEFAULT<               NCL Default Access by User user2, Password xxxJ               NCL Default Entity Node remnod Session Control Application *  >               In the preceding example, the new default accessG               information is stored, but contrary to the default accesshG               information displayed by SHOW NCL DEFAULT, the connectionnI               to node remnod through the user1 account will remain in use 7               until the default node entity is changed.n  F               This next command would request a new connection to nodeI               remnod using the latest default access information (throughoG               the user2 account), but the connection would fail because E               the password information provided earlier for the user2 $               account was incorrect:  4               NCL>SET NCL DEFAULT ENTITY NODE remnod:               %NCL-E-REQUESTFAILED, command failed due to:B               -CML-E-SESSPROB, error returned from session control6               -IPC-E-BADUSER, access control rejectionJ               -NET-F-REMOTEDISCONN, connection disconnected by remote userR               %NCL-E-NOCONNECTION, cannot establish CMIP connection to remote node0               set ncl default entity node remnod  C               Whenever a connection to a default entity node fails,t@               the default entity node is reset to the local nodeF               entity. Default subentity information is cleared as wellG               because subentities are node-specific. The default accessmH               information is left as is, but it remains unused until theH               default node entity is reset. For example, after the aboveI               failure to modify the default node entity, the NCL defaultsu#               would look like this:   "               NCL>SHOW NCL DEFAULT<               NCL Default Access by User user2, Password xxx#               NCL Default Entity ()     I                                                  Documentation Errata 4-5                 Documentation Errata"     4.1 Network Management and NCL         4.1.7 NCL Snapshot Command  @           Snapshot information is only retained for the duration@           of an NCL session. Therefore, the snapshot command and=           subsequent show commands must be issued at the NCL> B           prompt rather than at the DCL prompt. To gather snapshotD           information from a remote node, you can either set the NCLC           default to the remote node entity or include the nodename A           in each NCL command, as long as the commands are issuedc&           within the same NCL session.       4.2 OSAK Programming  E           The following sections provide information that updates them%           current OSAK documentation.n  !     4.2.1 Using OSAK over RFC1006i  C           On the initiator side, to make a connection over RFC1006,d?           specify as the NSAP the IP address as a 6-byte nibble A           packed hex value including the port number in the first E           two bytes. For example, the address of 16.36.12.142 on porto*           102 would be encoded as follows:  !                102  16.36.112.142u                  |   |  |   |   |                0066  10 24  70 8E  =           In this case, the NSAP would be 00661024708E (hex).yD           Specify the NSAP type as OSAK_C_RFC1006. For the transportC           template, specify either the pseudo-template "1006" or nocD           template at all. OSAK uses a default template of "1006" if*           the NSAP type is OSAK_C_RFC1006.  C           On the responder side, to listen for RFC1006 connections, ?           specify as the transport template the pseudo-templatet           "1006"..  /     4.2.2 New OSAK API Routine: osak_tc_no_sc()t  :           OSAK now contains a new API routine which allowsA           application programs to query OSAK to determine whether D           a transport connection has been established on a port, but'           a session connection has not.              Syntax:   -           status = osak_tc_no_sc(port, state)e       4-6 Documentation Errata           I                                                      Documentation ErrataiI                                                      4.2 OSAK Programmingh                   C Binding:  +                  osak_tc_no_sc(port, state)l                   osak_port port;                  int *state;           Arguments:                 port  3               The OSAK port that you wish to query.c                 state   H               A pointer to an integer where OSAK should return the stateD               information. If the port is connected at the transportF               layer, but not at the session layer, OSAK returns a non-H               zero value (true). If the port is connected at the session7               layer, OSAK returns a zero value (false).a                 Description:  @               Call this routine to determine whether the port isF               connected at the transport layer, but not at the sessionG               layer. This information can be useful when interoperatingrF               with some other OSI implementations that may incorrectlyB               terminate the transport connection, or may establishC               a transport connection but never complete the sessioneG               connection. Use of this routine can assist an application D               in determining if the OSAK port is hung. An equivalentH               routine also exists for the SPI interface: spi_tc_no_sc().                 Return Values:  F               OSAK_S_NORMAL    The routine has finished without error.  >               OSAK_S_INVPORT   The port identifier is invalid.  0         4.2.3 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,vE               they should also appear in the Parameters Used table asg               follows:  I                                                  Documentation Errata 4-7w    n           Documentation Errata     4.2 OSAK Programming  E           ___________________________________________________________            ParametersE           Used_________Data_Type____Access___________________________   -           [user_       Address      read onlya           context]  E           port_id______osak_port____write_only_______________________   ?           The preceding parameters should be listed for all SPI ?           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       4.3 DECdns  A           The information given in the following DECnet-Plus V7.1 !           manuals is not correct:n  D           o  Installation and Basic Configuration - Section 7.1.2.1,(              "Creating a New Namespace."  >           o  Installation and Advanced Configuration - Section1              2.1.2.1, "Creating a New Namespace."   B           These sections direct you to use DECNET_REGISTER (option?           10, Manage the directory service) to create namespace A           directories and then to use NET$CONFIGURE.COM to create 5           the new namespace. This order is incorrect..  @           The correct order is to first use NET$CONFIGURE.COM to>           create the new namespace. This procedure creates allA           of the directories needed for a single clearinghouse tooD           function correctly. Then, if you need to create additionalA           directories, use DECNET_REGISTER (option 10, Manage thesB           directory service) to create the additional directories.           4-8 Documentation Errata T  n                    I                                                                         5 I         _________________________________________________________________   I                                                         Operational Notes     F               This chapter contains operational notes for DECnet-Plus.G               Topics discussed here expand and amplify material present 3               in the DECnet-Plus documentation set.n  -         5.1 NSP Characteristics for X.25 PVCso  F               If a node has routing circuits of type x25 permanent youI               should set the NSP flow control policy characteristic to no G               flow control. In addition, if the call packet window sizeEH               is 8 or less, the NSP maximum window characteristic shouldG               be set to 8. This lowers the number of NSP unacknowledgedlI               transmits and thus prevents the NSP out-of-order cache froma               filling.           5.2 OSI Transportc  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 erroreD                  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$NAMESMI                  logical name table, you must put a quotation mark aroundL%                  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 thetD                     same in both transport partners if the packet isI                     traversing a backbone containing Phase IV routers (asa7                     opposed to routing vector domains).r  I                                                     Operational Notes 5-1     n           Operational Notes      5.2 OSI Transportt    E              -  Although the cluster alias uses two ranges of network A                 transport selector fields to reduce the risk of a C                 collision, Compaq recommends that you do not choose E                 values from those ranges, or at least that you do not :                 choose the first few values in each range.  A           o  The osi transport entity does not support a value ofsC              0 for the maximum remote NSAPs (network service accessW              points) attribute.E  A           o  The osi transport template entity does not support aoD              value of any for the network service attribute. If thisD              attribute is set to any, it is treated by OSI transport              as clns.n  ?     5.3 Transport Precedence in Predominantly Phase IV Networksa  B           When using DECnet over IP on a Phase V node, the defaultC           for session control's transport precedence characteristicsA           is {TP4,NSP}. This causes session control to attempt an A           OSI connection first, followed by an NSP connection. If C           you have a predominantly Phase IV network, this causes ancE           unnecessary delay when connecting to Phase IV nodes. If thesE           precedence is causing the delay, the delay will not be seen C           when connecting in the reverse. To change the precedence,oB           insert the following line at the end of the NET$SESSION_           STARTUP.NCL file:   E           set node 0 session control transport precedence = {NSP,TP4}I  B           Remember to reinsert this line if you run NET$CONFIGURE.  E     5.4 Upgrading to DECnet-Plus with Systems Running DEC X.25 (Alpha 
         Only)P  B           If you are upgrading to DECnet-Plus from DECnet Phase IV@           and have the DEC X.25 Client for OpenVMS Alpha Systems=           product installed, be aware that there are two X.25C-           products for OpenVMS Alpha systems:u  C           o  X.25 client software, for DECnet Phase IV systems only   >           o  Compaq X.25 for OpenVMS software, for DECnet-Plus              systems onlyW       5-2 Operational Notes     a      I                                                         Operational Notes I   5.4 Upgrading to DECnet-Plus with Systems Running DEC X.25 (Alpha Only)     H               If you upgrade to DECnet-Plus and want to retain access toF               X.25, remove the DEC X.25 Client product and install theI               Compaq X.25 for OpenVMS product, which provides both client ,               and native X.25 functionality.  E               For details about installing and configuring the Compaq @               X.25 for OpenVMS product, refer to the DECnet-Plus@               for OpenVMS Applications Installation and AdvancedB               Configuration and the X.25 for OpenVMS Configuration               manuals.  E         5.5 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.6 Decimal Syntax DSPs Not Supportedt  E               Compaq DECnet-Plus for OpenVMS supports only those IDPstC               (initial domain parts) that specify the use of binary D               syntax DSPs (domain-specific parts). IDPs that specify4               decimal syntax DSPs are not supported.  %         5.7 FDDI Large Packet Support.  G               Phase IV nodes do not support FDDI large packets. If yourhB               node has an FDDI controller that uses large packets,A               routing selects a smaller segment size for Phase IVLG               adjacencies. To communicate with Phase IV nodes, Phase IVcG               addressing must be enabled on the routing circuit. VerifybF               that the enable phaseiv address attribute is set to trueD               on one FDDI circuit in the sys$management:net$routing_               startup.ncl file.u        I                                                     Operational Notes 5-3e f  t           Operational Notes ;     5.8 Startup Procedure Change: NCL Information Minimizeds    ;     5.8 Startup Procedure Change: NCL Information Minimized   @           The startup procedure now displays a minimum amount of5           Network Control Language (NCL) information.f  9           If you want to view the complete NCL output fori@           troubleshooting purposes, you can define the following7           logical name in sys$manager:net$logicals.com:   ;           $ define/system/nolog net$startup_quiet_ncl falsee  =           If the net$logicals.com file does not exist on your A           system, you can create one by copying the file from theo,           sys$manager:net$logicals.template.  '     5.9 Setting Alias Selection WeightsS  E           The DECnet-Plus Network Control Language Reference suggestsCB           that the alias selection weight characteristic be set toD           values between 0 and 10. Setting the selection weight to aB           very low non-zero number, such as 1, encourages needless>           connection delay because each incoming connection is@           treated in a round-robin fashion. That is, as each newD           connection comes in, it must be passed to the next clusterD           member. In general, Compaq now recommends that values of 5E           to 10 be used. Zero should still be used when it is desired &           to exclude a cluster member.  A     5.10 Configuring X.25 Access Filters for Use by OSI TransportL          (VAX Only)o  A           To create X.25 Access filters with the X.25 Native ModeeE           software (formerly VAX P.S.I.) configuration procedure, usee>           the Declaring a Network Process section, as follows:  >           1. On the introduction screen to Declaring a Network9              Process section, answer YES to the question:   I              Do you want X.25 or X.29 programs to specify filter names inn(              $QIO(IO$_ACPCONTROL) calls?  ;           2. On the next screen, answer NO to the question:c  H              Do you want IO$_ACPCONTROL calls issued by your programs to&              name any dynamic filters?       5-4 Operational Notesi (  o      I                                                         Operational Notes I  5.10 Configuring X.25 Access Filters for Use by OSI Transport (VAX Only)     @               3. On the next screen, answer YES to the question:  L                  Do you want IO$_ACPCONTROL calls issued by your programs to)                  name any static filters?   A               4. On the following two screens, you can set up thejH                  attributes for the X.25 Access filter. You are promptedF                  to enter network process filter information. You must/                  complete the following fields:l  .                  o  Filter Name: OSI Transport  <                  o  Call Data Value: for example, %X03010100  ;                  o  Call Data Mask: for example, %XFFFFFFFFi  F                  You can set the filter name to any name. However, theI                  name you use must match the name you entered as the X.25tG                  Access template name and as the OSI Transport template I                  CONS template name. The OSI transport template attributeoG                  cons template is case sensitive and must match the OSIo:                  transport attribute cons filters exactly.  I                  Modification of the OSI transport cons filters attributeaI                  while OSI transport is enabled is permitted with the addnF                  command. The set and remove commands can only be usedE                  to modify the CONS filters when the OSI transport is                   disabled.  H                  The Call Data Value and Call Data Mask entries are usedB                  by X.25 Native Mode software to determine whetherC                  an inbound network connect should be passed to OSIe                  transport.t  B                  For other fields, use the default value provided.  G                  You can set up a security filter corresponding to thisoH                  X.25 Access filter in the Incoming Security for NetworkH                  Processes section of the X.25 Native Mode configuration                  procedure.e           5.11 DECdnsn      I                                                     Operational Notes 5-5i i  r           Operational Notesv     5.11 DECdns     2     5.11.1 Adjusting null_port_timeout in DNS.CONF  C           If you receive the message Unable to communicate with any E           DECdns server during a NEW EPOCH or CREATE REPLICA command,oA           you should increase the value for the null_port_timeout E           parameter on the server. For example, to set the timeout to0C           3600 seconds (60 minutes), add the following line to your(2           SYS$SYSDEVICE:[DNS$SERVER]DNS.CONF file:  *           dns.dnsd.null_port_timeout: 3600  @           It is CRITICAL that you increase the null_port_timeoutB           parameter on all servers that are in the replica set for?           the directory that had the problem. The timeout value B           should be the same on all servers in the replica set. IfE           you fail to do this, any changes that you make will have noK           effect.t  C              ________________________ Note ________________________s  C              This release of DECdns has increased the default value B              of the null_port_timeout parameter from 20 seconds to@              60 seconds. However, this default value will not be&              sufficient for all cases.  C              ______________________________________________________   2     5.11.2 Providing Adequate Resources for DECdns  D           It is important to provide the DECdns server with adequateA           resources because the DECdns server uses an "in memory"_E           database. Compaq strongly recommends that users be generoust?           with system quotas, especially the working set quota.   C           Autogen does not correctly calculate the working set size E           required by the DECdns Server. The working set size depends >           on the size of your checkpoint file. The size of theD           working set typically varies from 50,000 to 250,000. UsingE           working set sizes below 50000 is generally not recommended.e  E           If you need help on setting the quotas, contact your Compaq A           representative to obtain the tools to monitor the quotai           utilization.         5-6 Operational Notest s  t      I                                                         Operational NotesuI                                                               5.11 DECdnsh    4         5.11.3 Using the DNS.CONF Configuration File  @               Proper configuration of the server may be required?               if the default server quotas and timeouts are nottH               sufficient for your particular situation. These parameters@               are specified in the file DNS.CONF which is in the3               SYS$SYSDEVICE:[DNS$SERVER] directory.   6               An example DNS.CONF file is shown below:  +               ! all parameters in lowercase &               dns.dnsd.acs_override: 1+               dns.dnsd.node_verification: 0e.               !dns.dnsd.idle_conn_timeout: 500/               !dns.dnsd.null_port_timeout: 5400 3               dns.dnsd.maximum_handlers_quota: 1000m1               dns.dnsd.standby_handlers_quota: 10i2               dns.dnsd.maximum_buffers_quota: 1000)               dns.dnsd.ta_conn_quota: 600 ,               !dns.dnsd.back_conn_quota: 1007               dns.dnsd.dormancy_evaluation_interval: 30 1               !dns.dnsd.db_version_to_prune: 1236   ?               Parameter lines may be commented out by placing aoE               exclamation character (!) at the beginning of the line._H               The meaning of these parameters and the default values are               discussed below:  I               o  dns.dnsd.acs_override: Disables access control if set to H                  1. The default setting is zero (access control checking                  on).   G                 _______________________ Caution _______________________t  @                 While access control checking is overridden, anyE                 privileged or non-privileged user on your network hasiD                 complete read, write, delete, and control privilegesE                 to any object, directory, or clearinghouse managed onl                 this server.  F                 ______________________________________________________  G               o  dns.dnsd.node_verification: Disables node verification ?                  if set to zero. The default setting is 1 (node '                  verification enabled).c  I                                                     Operational Notes 5-7                 Operational Notesi     5.11 DECdnse    =              If you set this option to 0, the server does notcB              backtranslate the incoming address to verify that theB              incoming connection is actually coming from where the?              incoming connection claims it is coming from. With A              this disabled, servers are vulnerable to intentional @              or unintentional "node spoofing" where systems makeD              updates to the namespace for which their node names are4              authorized but their addresses are not.  @           o  dns.dnsd.idle_conn_timeout: Time in seconds to waitB              while link is idle before disconnecting the link. TheD              default value is 300 seconds (5 minutes). If this valueD              is set too low, it results in excessive processing timeD              to recreate links every time a request is processed. IfB              set too high, it ties up resources for links that are              not being used.  @           o  dns.dnsd.null_port_timeout: Time in seconds to wait?              before unconditionally disconnecting the link. Thea8              default value is 1800 seconds (30 minutes).  =              The value should be set high enough to allow theoB              longest command to complete execution. Typically, theC              longest command is "SET DIR .X TO NEW EPOCH ..." whichtB              includes a skulk as the final part of its processing.@              Values for this parameter can range anywhere from aB              couple of minutes to 90 minutes depending on the size@              of the directory involved and delays present in theA              network. (See Section "Problems Corrected in ECO 71"d@              for a description of the symptoms of the null_port_D              timeout being incorrectly set too low.) If you get a noE              communications error (DNS$_NOCOMMUNICATIONS) this can beO?              caused by the null_port_timeout being set too low.T  =              However, if the time for long commands starts to @              approach 2 hours this may indicate a hung link or a              hung server.   ?           o  dns.dnsd.maximum_handlers_quota: Maximum number ofaA              request handlers to allocate for request processing.0C              The default value is 200. In most cases, the number ofsB              request handlers needed is approximately equal to the7              number of clerks connecting to the server.n  ?           o  dns.dnsd.standby_handlers_quota: Maximum number ofn?              request handlers to keep ready to process incomingo)              requests. The default is 10.        5-8 Operational Notesc    a      I                                                         Operational Notes-I                                                               5.11 DECdns     B               o  dns.dnsd.maximum_buffers_quota: Maximum number ofH                  buffers available for request handlers from the requestF                  pool (rpool). The default is 200. Normally, the valueF                  for this parameter should be the same as the MAXIMUM_                   HANDLERS_QUOTA.  F               o  dns.dnsd.ta_conn_quota: Maximum number of connectionsG                  for front end operations (lookups, modify operations).sB                  The default is 200. Typically, the value for thisE                  parameter can be same or somewhat less than MAXIMUM_hG                  HANDLERS_QUOTA AND MAXIMUM_BUFFER_QUOTA. Both MAXIMUM_yH                  HANDLERS_QUOTA and MAXIMUM_BUFFERS_QUOTA may include anB                  additional allowance for the back end operations.  H               o  dns.dnsd.back_conn_quota: Maximum number of connectionsC                  for back end operations (skulks, other back ground}0                  activities). The default is 20.  F                  Note that the sum of these two quotas (TA_CONN_QUOTA,D                  BACK_CONN_QUOTA) should be below the values for NCLA                  characteristics for either OSI TRANSPORT MAXIMUM @                  TRANSPORT CONNECTIONS, or NSP MAXIMUM TRANSPORT@                  CONNECTIONS. Compaq recommends that the maximumI                  transport connections characteristics be set so that the G                  system never reaches the maximum number of connectionstB                  specified. Increase maximum transport connectionsD                  characteristics for NSP and OSI if required to meetH                  this requirement. In addition, increase NET$ACP process                  defaults.  @               o  dns.dnsd.dormancy_evaluation_interval: The timeH                  (seconds) to keep resources used by a request availableC                  in pool so that they may be reused. The default is2D                  60. Decreasing the value from the default may allowI                  resources to be released earlier. However, decreasing itWG                  too much results in a delay in starting the processing E                  of a new request. Consequently, if it is changed, ite/                  should be done very carefully.   C               o  dns.dnsd.db_version_to_prune: Sequence number of acD                  checkpoint file. All dying replicas will be removed?                  from this file. The default is 0 (turned off).o      I                                                     Operational Notes 5-9     a           Operational Notesi     5.11 DECdns     D              The sequence number can be determined by typing out theB              clearinghouse version file (the file which has a fileA              extension of .VERSION). Next, restart the server and C              then shut it down again. The server should write out aTD              new checkpoint file with the dying replicas eliminated.C              Finally, remove the above line from the DNS.CONF file,n@              and restart the server. Only one prune operation is(              allowed per server session.  C              ________________________ Note ________________________   C              If you choose to leave the line in the file you should =              change the value to 0 (zero) to avoid accidental               pruning.n  C              ______________________________________________________i  ?              To display the results of a prune operation in the.A              DNS$SERVER.LOG file, insert the "db_checkpoint_info"-E              event into the SYS$SYSDEVICE:[DNS$SERVER]DNSD.EVENT filei2              before beginning the prune operation.  8     5.11.4 Limitation on Size of Checkpoint File Records  D           The checkpoint file has a limitation of 500 blocks maximumB           on the size of individual records. To detect any recordsD           over this limit or approaching this limit, run the SURGEONC           "-scanrx" option. You will need to take corrective action B           if you see a line indicating greater than 500 blocks andC           the number of records is one (RECS: 1) because the servera?           may bugcheck with a 902 error in the DB_COMPRESSION.Cl           module.t  A           Records that exceed the 500 block maximum can be causedmD           by an application that is writing records larger than thisC           limit or the garbage collector mechanism (removes deletede"           records) is not running.  E           To correct the problem, apply one of the following actions:   <           o  Use the SURGEON "-exciser" option to remove the              offending records  <           o  Use the RECREATE OBJECT command (if the garbage'              collector is not running).w  B           If you have any questions about doing this, consult your            Compaq representative.       5-10 Operational Notes $  a      I                                                         Operational NotesaI                                                               5.11 DECdns     H               Avoid the situation with the garbage collector not runningD               by making sure all your directories skulk to a success=               status and that the DNS$ALLUPTO date is recent.r  I               Use the following command in DNS$CONTROL to check the skulke9               status of all directories in the namespace:i  *               SHOW DIR ... DNS$SKULKSTATUS  C               Use the following command in DNS$CONTROL to check theeC               DNS$ALLUPTO date on all directories in the namespace:i  &               SHOW DIR ... DNS$ALLUPTO  *         5.11.5 Using the NEW EPOCH Command  C               When issuing the NEW EPOCH command in the DNS$CONTROL ?               program, do not assume that the command completediE               successfully if you do not get any errors reported. YouiB               must check the skulk status on the master replica toH               determine if the NEW EPOCH command completed successfully.E               To check the skulk status, use a command similar to the                 following command:  >               SHOW REPLICA .directory CLEARINGHOUSE .master_ch               DNS$SKULKSTATUS   F                 ________________________ Note ________________________  D                 Specify the name of your clearinghouse that contains?                 the master replica, as the skulk status is only,0                 available on the master replica.  F                 ______________________________________________________  4         5.11.6 Configuring a Node as a DECdns Server  G               When you configure your system as a DECdns server, DECdnsaH               must be the primary name service. To specify DECdns as theE               primary name service, execute NET$CONFIGURE and specifyqC               DECdns as the first name service in the ordered list.b        I                                                    Operational Notes 5-11O h  o           Operational Notess     5.11 DECdns     %     5.11.6.1 Creating A New Namespacei  <           If your system is to be the first server for a new<           namespace, first configure the system in the LocalC           namespace. After you finish configuring the system in the B           Local namespace, configure the system with DECdns as the           primary name service.   ;           Remove the Local namespace later, if appropriate.l  B     5.11.7 Default Parameters for Process Limits on DECdns Servers  D           This note describes several default parameters for process+           limits on NET$ACP and DNS$SERVER.   B           o  The default value of 100 for FILLM on a DECdns serverA              limits the number of DECdns clerks that can connect. =              This limitation causes the DECdns clerk to log acC              USERREJECT error into the DNS$CHFAIL.LOG file when therE              limit of 100 connections is exceeded. You can raise thistC              limit by modifying the line in SYS$STARTUP:DNS$SERVER_d3              STARTUP.COM that specifies /FILLM=100.N  E           o  The default value of 100 for ASTLM on NET$ACP limits the B              number of connections that NET$ACP can process at one              time.  ?           o  When NET$ACP runs out of ASTs (asynchronous system D              traps), FILLM on the NET$ACP is closely following ASTLM?              toward 0. Both parameters must be raised together.l  C           o  The VIRTUALPAGECNT limit for nodes with DECdns serverss<              that have a small number of connections must be@              approximately 10,000 blocks greater than the DECdnsB              checkpoint file size. For DECdns servers with a largeE              number of connections, you should set the VIRTUALPAGECNT B              limit to a value at least three times the size of the@              DECdns checkpoint file. You must also size the pageB              files on the node accordingly. If the system has moreB              than one page file, the individual page files must beC              at least as large as the checkpoint file. Because eachuC              OpenVMS process is assigned to a single page file, thes@              total combined size of the page files is not useful?              to DECdns, because it can only use the capacity ofO?              one of them when it reads the entire clearinghouse B              checkpoint file into memory. Note also that DECdns is       5-12 Operational Notes    t      I                                                         Operational NotesuI                                                               5.11 DECdns     G                  not guaranteed to use the larger page file if one page ?                  file is sufficiently large and others are not._  4         5.11.8 PAGEDYN Resources: Clerks and Servers  D               DECdns clerk and server systems can require additional7               paged dynamic memory resources (PAGEDYN).v  G               For DECdns clerk systems, consider increasing the PAGEDYN I               resource on the node if you see either the RESOURCEERROR or :               NONSRESOURCES error during skulk operations.  E               Before you configure a system as a DECdns server, checkeE               that the system has at least 50,000 free bytes of pagedaB               dynamic memory. Insufficient paged dynamic memory onI               servers can cause configuration errors, skulk failures, andoG               in some cases normal clerk operations can fail, returningh>               either the RESOURCEERROR or NONSRESOURCES error.  I               The DNS$SERVER.LOG file can also contain messages regardingl/               failures caused by this resource.   F               Servers holding master replicas of directories that haveG               many read-only replicas can also require additional pagede               dynamic memory.s  G         5.11.9 Use the Outgoing Alias When Connecting to DECdns Serverse  E               Because of a change in DECnet-Plus Session Control, all B               DECdns requests from nodes in an OpenVMS Cluster canG               send the cluster alias address as the source address. TherF               current behavior is to send the individual node address.  6               To use this functionality, edit the fileF               SYS$MANAGER:DNS$CLERK_CLUSTER.NCL and set outgoing alias               = true.   I               To affect the running system, use the following NCL command$+               on all nodes in your cluster:   Q               NCL> set session control application dnsclerk outgoing alias = trueo  F                 ________________________ Note ________________________  =                 Implementing this functionality might require5C                 nontrivial changes to the current access control innB                 your namespace because you are changing the source1                 address of DECdns clerk requests.m  F                 ______________________________________________________  I                                                    Operational Notes 5-13i i  r           Operational Notesd     5.11 DECdns_             5.12 DECdts       <     5.12.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.c       5.13 OSAK Programmingr  B           The following sections discuss operational notes for the           OSAK interface.   1     5.13.1 User Data Size Restriction for Tracings  E           OSAK does not support tracing with user data buffers larger            than 32765 bytes.   .     5.13.2 OSAK Version 1.1 No Longer Supplied  C           Compaq no longer provides the OSAK Version 1.1 interface.D  =           If you use the OSAK Version 1.1 interface, you mustdB           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.1  B           For detailed information about the OSAK Version 3.0 SPI,D           see the DECnet-Plus OSAK SPI Programming Reference manual.  A     5.13.3 Migrating Applications from Version 2.0 to Version 3.0t            OSAK API Interfacec  C           Version 3.0 of OSAK includes a programming interface thatrB           is backwards compatible with the Version 2.0 programming=           interface. As a result of more rigorous conformanceeB           testing, some additional problems have been uncovered in$           the Version 2.0 interface.       5-14 Operational Notes    s      I                                                         Operational NoteseI                                                     5.13 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 applicationc               problems.   G         5.13.4 Misleading OSAK Error Message: SPM Congestion at Connectv                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 andoC               password specified in the request are correct. If therE               user name is correct but the password is incorrect, theeG               OPCOM message %LOGIN-F-INVPWD is logged. If the user name 7               is incorrect, no OPCOM message is logged.1           5.14 DECnet Programmingo  D               The following sections discuss programming issues that8               apply to the DECnet programming interface.  2         5.14.1 64-Bit Virtual Address Restrictions  A               You can use 64-bit virtual addresses only with $QIO C               operations on the NET: devices; you cannot use 64-bitpH               virtual addresses with $QIO operations on the OS: devices.  E               For transparent task-to-task communication, the $ASSIGN E               system service accepts only 32-bit addresses and 32-bit F               descriptors for the DEVNAM parameter when it describes aF               network connect block (NCB). You can use non-transparentE               task-to-task operations when you want 64-bit descriptortA               addresses and 64-bit descriptors to specify an NCB.l  .         5.14.2 Backtranslation of IP Addresses  E               For IP addresses, session control returns the full name G               if the synonym is not available regardless of the SessionoF               Control Application Node Synonym setting. If neither theD               full name nor synonym is available, the IP$aa.bb.cc.dd!               format is returned.s  I                                                    Operational Notes 5-15l T  d           Operational Notesv     5.14 DECnet Programmingi    E           If the system is configured to use IP addresses, you shouldUC           prepare the application to receive a node name or addressnE           string longer than six characters in length even if SessioneB           Control Application Node Synonym = TRUE is specified for           the application.  .     5.14.3 Applications Connection Requirement  >           With DECnet-Plus, your application must wait for theC           completion of the $QIO system service call used to acceptTA           the connection before attempting to use the connection.k  ;     5.15 FTAM, Virtual Terminal, and OSI Application KernelM       5.15.1 FTAMn  A           This section discusses issues related to FTAM software.k  6     5.15.1.1 Downstream Processing Support in OSIF$FAL  >           This version of FTAM includes additional support forB           downstream file processing when using the FTAM responder           (OSIF$FAL.EXE).   ?           OSIF$FAL creates the OSIF$FILEINFO logical name. When B           translated, this logical name provides information about?           all files that were opened via an FTAM F-OPEN-REQUESTt@           during the FTAM association. The information currentlyA           available includes the local RMS file name and the FTAM D           processing mode for the file. Each piece of information is#           delimited by a slash (/).a             For example:  &           $ show logical osif$fileinfoX              "osif$fileinfo" [SUPER] = "dka500:[tmp]file1.txt;1/48"  (lnm$process_table).                   = "dka500:[tmp]tmp.tmp;9/48"  D           The OSIF$RESPONDER.COM procedure located in SYS$SYSTEM hasB           been enhanced with sample DCL code that demonstrates how2           this information can be parsed and used.             5-16 Operational Notes s         I                                                         Operational NotesnI                   5.15 FTAM, Virtual Terminal, and OSI Application Kerneln    )         5.15.1.2 COPY Command Enhancement   F               In older versions of DECnet-Plus, when you copied a fileH               from a local file to a remote alias, the following commandC               automatically created the output file name "." on thef               target system:  6               copy/app=ftam file.ext alias"user pwd"::  ?               This command now uses the name you specify on theDH               initiating system to create the file on the target system.           5.15.1.3 DAP/Gateway  @               Support now exists for the DAP/FTAM gateway append               function.t  8         5.15.1.4 RMS Record I/O Performance Enhancements  @               This version of FTAM includes changes that enhanceB               performance with RMS when doing record-oriented I/O.D               In addition to internal changes, two logical names nowF               allow some control over initial file creation and extendI               sizes. These logical names are most useful when you know in I               advance that a typical file will exceed a certain size, and :               that FTAM is acting as the receiver of data.  $               The logical names are:  I               ___________________________________________________________hI               Logical_Name________Action_________________________________n  G               OSIF_FILE_ALQ       Controls initial file allocation sizeD-                                   (in blocks)   I               OSIF_FILE_DEQ_______Controls_extension_size_(in_blocks)____   F                 ________________________ Note ________________________  A                 If a future_filesize parameter is supplied in they@                 F-CREATE-REQUEST, the logical names are ignored.  F                 ______________________________________________________  A               You can define the logical names in any appropriatecE               location, such as in SYS$SYSTEM:OSIF$RESPONDER.COM. Forr               example:  T               $ define OSIF_FILE_ALQ 1000   ! allocate files initially @ 1000 blocksN               $ define OSIF_FILE_DEQ  500   ! extend by 500 blocks when needed  I                                                    Operational Notes 5-17t m  a           Operational Notes ;     5.15 FTAM, Virtual Terminal, and OSI Application Kernell    E           Limited performance testing has been done with FTAM-1 fixedeA           files. Increases in performance ranges are dependent on @           the platform and other variables. Because many factors7           influence performance, actual increases vary.        5.15.2 Virtual Terminal   C           This section discusses issues related to Virtual TerminalN           (VT) software.       5.15.2.1 CTRL-@   B           A previous release note item incorrectly stated that theB           SET command in Local Command Mode would not accept CTRL-B           @ as a valid value for the break, command, or disconnectC           characters. You may specify CTRL-@ as the break, command, C           or disconnect character by using the circumflex-character A           notation (by typing the circumflex (^), followed by the            "at-sign" (@)).i       5.15.2.2 Amode Repertoire   :           The SEND command in Local Command Mode no longerE           incorrectly indicates that a character is not in the Amode-L           default repertoire.n       5.15.2.3 Responder  B           The Virtual Terminal responder no longer stops acceptingE           connections after several connections have been established$           and aborted.       5.15.2.4 VT/LAT Gateway   >           The VT/LAT gateway no longer hangs if an unknown LAT=           service is provided at the LAT service name prompt.a                       5-18 Operational Notes m                       I                                                                         6aI         _________________________________________________________________   I                                                            Known ProblemsU    D               This chapter discusses known problems and restrictionsG               present in the Compaq DECnet-Plus for OpenVMS Version 7.3s               product.  -         6.1 NET$SHUTDOWN May Fail to Complete   D               NET$SHUTDOWN may fail to complete if there are network@               applications that issue new connections during the               shutdown.n  G               A solution is to invoke the application shutdown prior to,I               the network shutdown by use of the NET$AUX_CONTROL logical. I               Define NET$AUX_CONTROL to point to an auxiliary applicationf-               shutdown DCL command procedure.i  I         6.2 Receive Buffers Attribute on HDLC LINK Entity Not Implemented              (Alpha Only)  F               The receive buffers attribute of the hdlc link entity isG               not implemented in DECnet-Plus. If you attempt to set theiH               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-0r4               at 1994-04-28-09:51:10.780-04:00I0.113  $               Command failed due to:               set list error                 Characteristics 7               no such attribute ID: Receive Buffers = 8p  I               HDLC (High-level Data Link Control) allocates the number ofuG               receive buffers that it requires; you cannot specify thisb               setting.  I                                                        Known Problems 6-1c                Known Problems     6.3 DECdns         6.3 DECdns    '     6.3.1 Error Creating New Namespacesc  A           An error can occur when creating a new namespace if theiB           directory SYS$SYSDEVICE:[DNS$SERVER] is missing. CorrectE           this error by issuing the following command from the SYSTEMA           account:  7           $ CREATE/DIRECTORY SYS$SYSDEVICE:[DNS$SERVER]o  A           Use the above command before attempting to create a new(           namespace.  .     6.3.2 System Hangs at Startup in DNS Clerk  9           The system may hang at startup in the DNS clerksB           initialization procedures. This problem can occur when aA           system with three or more LAN adapters fails on startupfC           of the DECdns clerk. The startup fails because the DECdnsrB           Clerk Buffer Limit has been reached. To work around this?           problem, define the logical DNS$ADVER_BUFFER_LIMIT ins$           SYLOGICALS>COM as follows:  7           $ DEFINE/SYSTEM DNS$ADVER_BUFFER_LIMIT 300000   D     6.3.3 Server Software Is Not Available for OpenVMS Alpha Systems  E           DECdns server software is not available to use with OpenVMS A           Alpha systems. All references to DECdns servers (and toeD           their resident clearinghouses) apply to the DECdns serversE           in your namespace that are running on ULTRIX, DIGITAL UNIX,c!           or OpenVMS VAX systems.o  -     6.3.4 Startup Error Message: DECdns Clerko  C           The DECdns clerk startup might output the following errort           message:  4           Create Node 0 DNS Clerk Known Namespace CZ              command failed due to:           process failure   B           A Known Namespace with this name or NSCTS already exists       6-2 Known Problems           I                                                            Known ProblemseI                                                                6.3 DECdnsa    >               You can disregard this message. The DECdns clerkC               configuration procedure puts a create dns clerk knownuI               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.  %         6.3.5 General DECdns Problems   @               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 doeslH                  not modify it properly. Use the decnet_register tool to5                  modify DECnet data stored in DECdns.n  I               o  Re-created entries retain the case of the original entry                   name.  E               o  On OpenVMS VAX systems, if you have trouble creatingnF                  a clearinghouse, make sure that either the dns$serverG                  account (user authorization file entry) does not exist 5                  or its default directory does exist.-  3         6.3.6 Handling Clerk Cache Startup Problemst  G               The DECdns clerk resizes the clerk cache file only when asF               sizing calculation determines that the file is less thanA               whichever is smaller: 1000 blocks or .5% of memory.u  D               If the amount of physical memory available to a systemB               has changed or if the GBLPAGFIL system parameter hasF               been modified, check the SYS$MANAGER:DNS$ADVER_ERROR.LOGE               file. The DECdns clerk indicates in this file if it hasn6               calculated a new recommended cache size.  ?               When you see the following message, fewer than 10 A               GBLPAGFILs are available and the cache file was not                created:  <               Insufficient Global Page File Limit - no cache  ?               When this situation happens, increase the size ofrE               GBLPAGFIL, run AUTOGEN, and reboot your system to get a_'               functioning DECdns clerk.   I                                                        Known Problems 6-3                 Known Problems     6.3 DECdns    D           If the cache file size exceeds 75 percent of the available@           GBLPAGFIL, it is set to that figure (75 percent of the?           available GBLPAGFIL) so it does not use up all of theoD           available GBLPAGFIL. For OpenVMS systems, the maximum size'           of the clerk cache is 512 MB.i  D           If the recommended change in the size of the cache file isD           substantial and you want DECdns to use the new cache size,#           take the following steps:k             1. Shut down DECdns.  ,           2. Delete the existing cache files&              (SYS$SYSTEM:DNS$CACHE.*).  E           3. Reboot the system (do not start DECdns before rebooting-eC              the cache sizing algorithm must run on a fresh boot ofh              OpenVMS).  :           4. Start DECdns during the reboot or at any time              thereafter.  3           The first time DECdns Version 2 runs on ai7           system (or if DECdns runs and finds the cachen8           file missing), the advertiser creates the file=           SYS$SYSTEM:DNS$CACHE.0000000001) (again, only if itrA           does not already exist). This file is the backing storeV<           file for the DECdns clerk cache. The backing store>           update interval is 30 minutes. The extension part of;           the file name (0000000001) is incremented by 1 atA=           each interval and is updated in the associated filePA           SYS$SYSTEM:DNS$CACHE.VERSION. If you want to start withgE           an empty cache, delete both files by entering the following0-           command before you start the clerk:o  )           $ delete sys$system:dns$cache.*n  +     6.3.7 Removing Obsolete DNS$CACHE Files   <           Multiple obsolete copies of the DECdns clerk cache>           backing store file (SYS$SYSTEM:DNS$CACHE.000000000n)@           can, under unusual circumstances, accumulate and causeA           disk space problems on the system. DECdns uses only ther?           DNS$CACHE.VERSION file and the one or two most recent E           DNS$CACHE.000000000n files referenced in DNS$CACHE.VERSION.kD           DECdns normally deletes prior unreferenced versions of the           file.a       6-4 Known Problems c  o      I                                                            Known Problems I                                                                6.3 DECdnse    C               If you check the contents of the SYS$SYSTEM directoryt@               and see more than one backing store file, type the?               DNS$CACHE.VERSION file to see which backing storeiB               files DECdns is currently using and delete all prior<               DNS$CACHE.000000000n files from the directory.                                                                                I                                                        Known Problems 6-5o