DECnet-Plus for DIGITAL UNIX Release Notes August 1997 Revision/Update Information: This document supersedes the release notes for Version 4.0 and V4.0A. Operating System: DIGITAL UNIX Operating System V4.0 Software Version: DECnet-Plus V4.0B for DIGITAL UNIX © Digital Equipment Corporation 1997. All Rights Reserved. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from DIGITAL or an authorized sublicensor. Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. The following are trademarks of Digital Equipment Corporation: DDCMP, DEC, DECnet, DECNIS, DECserver, DECsystem, DEC WANrouter, DECwindows, DIGITAL, DNA, OpenVMS, PATHWORKS, POLYCENTER, ULTRIX, VAX, VAXstation, VMS, VMScluster, and the DIGITAL logo. The following are third-party trademarks: Macintosh is a registered trademark of Apple Computer, Inc. MS-DOS is a registered trademark of Microsoft Corporation. OS/2 is a registered trademark of International Business Machines Corporation. OSF/1 is a registered trademark of Open Software Foundation, Inc. SCO is a trademark of Santa Cruz Operations, Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Co. Ltd. All other trademarks and registered trademarks are the property of their respective holders. ________________________________________________________________ Contents 1 Introduction 1.1 Problems Resolved............................... 1-1 1.1.1 Problems Resolved in V4.0A ................... 1-1 1.1.2 Problems Resolved in V4.0B ................... 1-2 1.2 V4.0B and Year 2000 Compliance.................. 1-4 1.3 New Features for V4.0........................... 1-4 1.3.1 DECnet for Small Configurations (DNALITE400) Installation.................................. 1-4 1.3.2 Graphical User Interface for DECnet-Plus Configuration................................. 1-6 1.3.2.1 Invoking the Graphical User Interface for Configuring DECnet-Plus.................... 1-7 1.3.2.2 Summary of Graphical Interface Features.... 1-8 1.3.3 DNS/BIND Support for NSAP Addresses .......... 1-8 1.4 Configuration Notes for DECnet-Plus for DIGITAL UNIX Systems Version 4.0 Release................ 1-9 2 Installation Notes 2.1 Using DECnet with Enhanced Security............. 2-1 2.2 DECnet for Small Configurations Installation.... 2-1 2.3 New Subsets..................................... 2-1 2.4 Dynamic Kernel and SMP Support.................. 2-2 2.5 Installation Message............................ 2-2 2.6 Before Re-Installing the DIGITAL UNIX Operating System.......................................... 2-2 2.7 RIS Installation Issues......................... 2-3 2.8 Graphical User Interface for Basic and Advanced Configuration................................... 2-4 2.9 Restart X Server to Display X Window System Applications.................................... 2-4 iii 2.10 Removing the DECnet-Plus Software............... 2-4 2.11 Shutting Down DECnet-Plus While the CTF Collector Daemon (ctfd) Is Running.............. 2-5 3 Network Management 3.1 Event Logging-Disabling the Event Dispatcher.... 3-1 3.2 Using Wildcards to Display Subentities May Cause NCL to Hang..................................... 3-1 3.3 Documentation Corrections for the DECnet-Plus Network Control Language Reference Manual....... 3-1 4 General Software Notes 4.1 New Functionality of DECnet-Plus Mail-11 (OpenVMS Mail) Agents........................... 4-1 4.2 REMUSER Environment Variable.................... 4-2 4.3 OBJECT Environment Variable..................... 4-2 4.4 No Default Object............................... 4-2 4.5 Problems with the DECwindows Session Manager.... 4-3 4.6 Using the DECnet-Internet Gateway............... 4-3 4.6.1 PWD and XPWD Commands Not Implemented ........ 4-3 4.6.2 Telnet ....................................... 4-3 4.6.3 Using the Gateway for Remote Login ........... 4-3 5 Programming Issues 5.1 Using the getnodename Subroutine................ 5-1 5.2 XTI Known Problems.............................. 5-1 5.3 DECnet-Plus Libraries........................... 5-2 6 Unsupported Utilities 6.1 Unsupported Utilities Subset.................... 6-1 6.2 WWW (World Wide Web) Gateway to DEC Notes....... 6-1 6.2.1 Configuring webnotesd ........................ 6-1 6.2.2 Using webnotesd .............................. 6-2 6.3 tell............................................ 6-3 6.4 nfi............................................. 6-4 6.5 gatewayd........................................ 6-5 6.6 DEC Notes Clients............................... 6-6 6.7 Poor Man's Routing (PMR) for Mail-11/CTERM/DAP.. 6-7 6.7.1 Mail-11 ...................................... 6-7 iv 6.7.2 CTERM ........................................ 6-7 6.7.3 DAP .......................................... 6-7 6.8 Converting node::user to user@fullname.dnet..... 6-8 7 DECdns 7.1 DECdns Changes for Version 4.0B................. 7-1 7.1.1 DECdns Server Changes for Version V4.0B ...... 7-1 7.1.2 DECdns Clerk Changes for Version V4.0B ....... 7-2 7.2 Creating and Initializing a New Namespace ...... 7-3 7.2.1 Creating a Namespace on DECnet-Plus for DIGITAL UNIX Systems.......................... 7-3 7.2.1.1 Example Creating Namespaces and Directories................................ 7-5 7.3 DECdns Server Joining Existing Namespace........ 7-9 7.4 Limitation for Number of Members in a Single Group........................................... 7-10 7.5 Location of DECdns Sockets...................... 7-10 7.6 Location of DECdns Clerk Backing File........... 7-11 7.7 DECdns Clerk Software on Nodes with Extended Addresses....................................... 7-11 7.8 Problem with dump dns clerk cache Command....... 7-11 7.9 High Convergence Directories Not Recommended.... 7-12 7.10 Replicating the DECnet-Plus Directories......... 7-12 7.11 Clarification of "World" Access in DNS and DECdns.......................................... 7-13 7.12 Clerk Not Enabled Error Message................. 7-13 7.13 Clear Clearinghouse Command Gives Spurious Error........................................... 7-13 7.14 Show Clearinghouse Command Can Produce Errors... 7-13 7.15 Documentation Correction to Deleting a Clearinghouse................................... 7-14 7.16 Documentation Correction to Name Resolution Operations...................................... 7-14 7.17 Documentation Correction to "Adding Group Access" Procedure............................... 7-15 7.18 Documentation Correction to "Denying Group Access" Example................................. 7-15 7.19 Documentation Additions to Clearinghouse Creation Procedure.............................. 7-15 7.20 Documentation Correction to delete child Command Example......................................... 7-16 v 8 DECdts 8.1 Changing the Time Differential Factor (TDF)..... 8-1 8.2 Time-Provider Interface (TPI) Advisory.......... 8-2 8.3 Starting a Time-Provider........................ 8-2 8.4 Update to List of Supported Radio Receivers..... 8-2 9 FTAM and Virtual Terminal 9.1 FTAM............................................ 9-1 9.1.1 Property List Support ........................ 9-1 9.1.2 Responder Logging Support .................... 9-2 9.2 Virtual Terminal................................ 9-3 10 OSAK 10.1 New features.................................... 10-1 10.1.1 OSAK Application Programming Interface (API)......................................... 10-1 10.1.2 New OSI Session Programming Interface ........ 10-1 10.1.3 Listen on Both RFC1006 and OSI Transport ..... 10-1 10.2 Programming Interface Changes................... 10-2 10.2.1 Called_aei Parameter on A-ASSOCIATE and S-CONNECT Indication Events................... 10-2 10.2.2 New Status Code .............................. 10-2 10.2.3 ROSE Minimum Workspace Increased ............. 10-2 10.3 Problems Resolved............................... 10-3 10.3.1 Wrong NSAP No Longer Output to OSAKtrace File.......................................... 10-3 10.3.2 Transport Template Settings Honored .......... 10-3 10.3.3 Transport Congestion Problems Relieved ....... 10-3 10.4 Known Problems and Restrictions................. 10-3 10.4.1 Incorrect Information May Be Logged To OSAKtrace..................................... 10-4 10.4.2 Closing Port After a Redirect Request ........ 10-4 10.5 Documentation Corrections....................... 10-4 10.5.1 Using OSAK over RFC1006 ...................... 10-4 10.5.2 Compiling API, ROSE, and SPI Applications .... 10-5 10.5.3 Linking API, ROSE, and SPI Applications ...... 10-5 vi Index Tables 1-1 Choosing the Installation Type ............... 1-6 vii 1 ________________________________________________________________ Introduction The DECnet-Plus (formerly DECnet/OSI) Version 4.0 for DIGITAL UNIX software product is an end-node implementation of the DIGITAL Network Architecture (DNA) for the DIGITAL UNIX operating system. The following sections provide release notes for mandatory update (MUP) Version 4.0A: - Section 1.1.1 for problems resolved and general changes - Section 2.1 for enhanced security installations - Section 7.1 for DECdns changes - Chapter 9 for FTAM changes The following sections provide release notes for mandatory update (MUP) Version 4.0B: - Section 1.1.2 for problems resolved - Section 1.2 for Year 2000 issues 1.1 Problems Resolved The following sections list the problems corrected in Version 4.0A and Version 4.0B. 1.1.1 Problems Resolved in V4.0A o RFC 1006 There was a memory corruption problem that would have caused system crashes. The typical stack trace had some mbuf manipulation on the stack. There was a memory leak that led to large amounts of system memory to be tied up in mbufs. Introduction 1-1 Certain other implementations of RFC 1006 could not consistently connect to a DIGITAL UNIX system. The success or failure depended on how the packet fragmentation was done. o DOTI (DECnet over TCP/IP) There was a problem during the system boot related to the timing of certain kernel events. o OSI Transport The system could crash if DECnet were shut down and restarted while X.25 was running. The system could crash while attempting to log connection-refusal events from CONS (X.25). This crash was indicated by the routine tp_log_refused_ cons_connection being on the stack. The system could crash while trying to log an rsp deleted event. This crash would be marked by the routine tposi_event_deleted_rsp being on the stack. o DTSS A problem with DTSS has been corrected to allow dtssd to run on TruCluster systems. 1.1.2 Problems Resolved in V4.0B o RFC 1006 The subroutine xti_ipgetaddr returned random values for the peer port number. It now returns the actual value. Multiprocessor systems could crash with a "kernel memory fault" when using RFC 1006. o OSI Transport A system crash (in tposi_dotimeout) when running over X.25 has been corrected. A system memory leak has been eliminated. When multiplexing multiple TP2 connections over X.25 there would sometimes be unnecessary delays in the transfer of data. 1-2 Introduction Data corruption sometimes occurred during data transfer. (This problem has only been seen when communicating with a particular specialized piece of hardware which made unusual use of zero-credit acks). The maximum number of connections has been increased from 1024 to 65535. o DECdns The DECdns clerk was able to connect only to servers that had at least one nsap starting with 49: DECdns would not work, or would work sporadically, when servers were located off the LAN. The severity of the problem depended on the amount of delay in reaching the servers. The dnsadv log file is now in /var/dss/dns rather than in /tmp. o Network Management Multiprocessor systems could crash with a "kernel memory fault" if a user cancelled an ncl command (using ^C) which was generating a large amount of output. NCL now accepts INET addresses (as well as names) when using TCP/IP as the transport (for example: ncl> show node 16.20.16.1). Counter values reported by CSMA-CD entities were corrected. o Event Logging Changing the sink type of an event dispatcher sink while the sink is active could cause dnaevld to core dump. dnaevld would core dump when creating a second outbound stream The event dispatcher was not accepting inbound streams from remote DECnis routers. o MOP Introduction 1-3 Up-line dumps could sometimes fail with the following error in the syslog file: "MOP[xxx]: Dump for 08-00-2b-a1-12-93 failed, open file ()" Down-line loads of the WANrouter 90 would sometimes fail. 1.2 V4.0B and Year 2000 Compliance DECnet-Plus for DIGITAL UNIX Version 4.0B is year-2000 compliant. The changes required to achieve this compliance were minimal. The only visible change was with the dls command when using the -l switch. The dls command now displays the date with a four-digit year instead of a two-digit year. You can force dls back to the previous behavior by defining an environmental variable named DLS_ 2DIGIT_YEAR. 1.3 New Features for V4.0 New functionality in V4.0 includes: o DECnet for Small Configurations (DNALITE400) installa- tion option o Graphical user interface for the basic and advanced configuration procedures o Network services access point (NSAP) addresses in DNS /BIND 1.3.1 DECnet for Small Configurations (DNALITE400) Installation With this release, you can choose to install DECnet for Small Configurations (DNALITE400). Thus, you can now choose from four types of installations: o DECnet for Small Configurations (DNALITE400)-For installation on systems with limited disk space and memory (32 MB of memory or less), or requiring only basic DECnet Phase IV functionality (mail, file transfer, and remote login). This installation requires installation of the DECnet-Plus Kernel Components (DNAKBIN400) subset as well. The only other subsets that can be installed in addition to DNALITE400 are the 1-4 Introduction DECnet-Plus Reference Pages (DNAMAN400) and DECnet-Plus Miscellaneous Software (DNAUTIL400) subsets. (Note that DECnet for Small Configurations also supports use of DECnet over TCP/IP.) o Full-capability DECnet-Plus-For systems requiring full DECnet-Plus functionality, such as OSI, RFC 1006 (supporting OSI over TCP/IP), DECnet over TCP/IP (RFC 1859), or Wide Area Networking Support for DIGITAL UNIX software (X.25). (The full-capability DECnet-Plus installation requires installation of the following subsets: DECnet-Plus Base Components, DECnet-Plus Kernel Components, DECnet-Plus Network Management. In addition, you can install any of several other optional subsets.) o RFC 1006-only- For systems only requiring the RFC 1006 feature to run OSI applications over TCP/IP. The RFC 1006-only installation requires the DECnet-Plus Kernel Components (DNAKBIN400) and DECnet-Plus Network Management (DNANETMAN400) subsets. o MOP-standalone-For systems only requiring Maintenance Operations Protocol (MOP) downline load and upline dump operations without DECnet-Plus software. The MOP-standalone installation requires the DECnet-Plus Kernel Components (DNAKBIN400), DECnet-Plus Network Management (DNANETMAN400), and DECnet-Plus MOP Utilities (DNAMOP400) subsets. The setld script menu of subsets includes the DECnet for Small Configurations (DNALITE400) subset as a choice. However, this choice will not appear if certain subsets are already installed on your system. The DECnet functionality required for DECnet for Small Configurations is contained in one subset, DNALITE400. You also need the DECnet-Plus Kernel Components subset (DNAKBIN400). If you install DNALITE400, you cannot install many of the other subsets that come with a normal (full-capability) DECnet-Plus installation. The subsets that you can install optionally in addition to the DNALITE400 subset are: o DECnet-Plus Reference Pages (DNAMAN400) Introduction 1-5 o DECnet-Plus Miscellaneous Software (DNAUTIL400) Table 1-1 provides guidelines for choosing the appropriate installation for your system and needs. Table 1-1 Choosing the Installation Type ___________________________________________________ If your system has... Use... ___________________________________________________ 32 MB of memory or less DNALITE Limited free disk space DNALITE Requirements for only basic DECnet DNALITE Phase IV functionality such as mail, file transfer, and remote login Requirements for DECnet over TCP/IP DNALITE Full-capability DECnet-Plus Requirements for OSI or RFC 1006 Full-capability over TCP/IP DECnet-Plus Requirements for DECdns server, Full-capability DECdts clerk or server, wide- DECnet-Plus area networking/X.25 services, OSI applications or gateways software, DECnet-Internet Gateway Requirements only for the RFC 1006 RFC 1006-only feature to run OSI applications over TCP/IP Requirements for MOP without MOP-standalone DECnet-Plus ___________________________________________________ 1.3.2 Graphical User Interface for DECnet-Plus Configuration You can now use a graphical user interface as an alternative to the terminal-based interface (decnetsetup) for either the basic or advanced configuration procedure. Your DIGITAL UNIX system must have a graphics capability, Motif Version 1.2 software, and at least 32 MB of main memory. The interface is available by command and is also integrated into the Common Desktop Environment (CDE), the default Windows manager for DIGITAL UNIX Version 4.0. 1-6 Introduction The graphical interface displays a Setup window that lets you point and click on fields to enter your responses. The screen prompts you for information in the same order as the script, but you can supply information in any order. The interface provides pointer-sensitive help. 1.3.2.1 Invoking the Graphical User Interface for Configuring DECnet-Plus The interface is available by command and is also integrated into the Common Desktop Environment (CDE), the default Windows manager for DIGITAL UNIX Version 4.0. The graphical interface then lets you select the basic or advanced configuration. To invoke the graphical interface from the command line, use the following command: # /usr/sbin/dxdecnetsetup To invoke the graphical interface from the CDE front panel, follow these steps: 1. Select the Application Manager 2. Select System Admin 3. Select the Configuration folder 4. Select the DECnet-Plus icon _______________________ Note _________________________ If your system is operating under Enhanced Security, to use privileged functions, first become a root user (super user) before you start the graphical interface (that is, at the system prompt, enter the su command to switch to root, then start the graphical interface). _____________________________________________________ Introduction 1-7 1.3.2.2 Summary of Graphical Interface Features The features of the graphical interface include: o Easy to use o Pointer-sensitive help o Highlighting of invalid responses o You can modify the appearance of the interface and specify defaults in a customized file. You can modify and store such settings as colors used for invalid highlighting, fonts used for displayed text, language used for displayed text, and names of menus and windows. 1.3.3 DNS/BIND Support for NSAP Addresses DECnet-Plus includes DNS/BIND support for network service access point (NSAP) records, as defined in RFC 1706. An NSAP is a global network address that defines the point at which a network entity provides a network service to a network user. It identifies both the particular network system and the transport module on the system that is to receive the data. RFC 1706 defines the record format so addresses can be assigned to a host name. In addition, to support inverse address lookups (that is, a backtranslation function), the RFC defines the storage of NSAP addresses in a hierarchical directory structure. When a name is successfully resolved, a pointer (PTR) record is returned. This pointer record takes as its value the fully qualified domain name of the host that has this address. _______________________ Note ________________________ If you are using a DNS/BIND server supplied by another vendor, verify that it supports NSAP address records. _____________________________________________________ 1-8 Introduction 1.4 Configuration Notes for DECnet-Plus for DIGITAL UNIX Systems Version 4.0 Release If you want to configure the Wide Area Networking Support for DIGITAL UNIX software (X.25) for use with Version 4.0 of DECnet-Plus for DIGITAL UNIX, use the release of the Wide Area Networking Support for DIGITAL UNIX. See the latest Wide Area Networking Support for DIGITAL UNIX Software Product Description (SPD) for product release information. Introduction 1-9 2 ________________________________________________________________ Installation Notes This chapter describes some details you should be aware of before installing the DECnet-Plus for DIGITAL UNIX software. 2.1 Using DECnet with Enhanced Security If enhanced security is enabled on a system running DECnet, users may no longer be able to log into that system via dlogin . This is because enhanced security expires all accounts when it is enabled, including the daemon account, which is the default account used by DECnet for remote logins. To re-enable dlogin, either activate the daemon account by resetting the password or change the default account on the "session control application cterm" entity to an active account. 2.2 DECnet for Small Configurations Installation You can choose a DNALITE installation for systems with limited disk space and memory, or for systems requiring only basic DECnet Phase IV functionality (mail, file transfer, and remote login). Note that the requirements and limitations for a DNALITE installation reflect many of the requirements and limitations for a UNIX installation for small configurations. 2.3 New Subsets This release includes the following new subsets: o DECnet for Small Configurations (DNALITE400)-Provides the DECnet functionality described in Section 2.2. The DECnet functionality is contained in only one subset. The only other subset required is the Kernel Components subset (DNAKBIN400). Installation Notes 2-1 o DECnet-Plus Transition Tools (DNATRANSITION400)- Provides system and network managers with tools to ease the transition from DECnet Phase IV to DECnet-Plus. o DECnet-Plus Kernel Components (DNAKBIN400)-Provides the elements of the base components in the UNIX kernel required for DECnet functionality and maintainability. The following subsets have been removed or replaced in this release: o DECnet-Plus Datalink Components o DECnet-Plus RFC 1006 Components The DNANETMAN400 subset now includes the functionality that was provided by these subsets. Note that when installing the DECdns Server subset (DNADECDNSSRV400), you need to install the DECnet-Plus Transition Tools subset as well (DNATRANSITION400). 2.4 Dynamic Kernel and SMP Support DECnet-Plus for DIGITAL UNIX supports the DIGITAL UNIX features of symmetric multiprocessing (SMP) and the dynamic loading of kernel components. This dynamic loading capability eliminates the requirement to rebuild the kernel after installing a layered product such as DECnet- Plus. 2.5 Installation Message The following message may occur when configuring DECnet- Plus via decnetsetup and can be safely ignored: CTF: Error, another CTF Daemon is already running 2.6 Before Re-Installing the DIGITAL UNIX Operating System If you plan to re-install the DIGITAL UNIX operating system, first back up files in the /var directories. The following table describes the contents of the relevant /var directories: 2-2 Installation Notes __________________________________________________________ Directory Description __________________________________________________________ /var/dss/dns DECdns clerk and server data files /var/dna DECnet data files __________________________________________________________ _______________________ Note _________________________ Shut down DECnet-Plus before you run the backup procedure. _____________________________________________________ Also back up any customized DECnet initialization ncl scripts in the /var/dna/scripts directory. The standard initialization files are created by the decnetsetup utility when configuring DECnet. 2.7 RIS Installation Issues You should consider the following issues when using Remote Installation Services (RIS) to load DECnet-Plus for DIGITAL UNIX and related products onto RIS client systems. 1. There are dependencies among products that are handled correctly when installing from CD-ROM, but that can cause error messages when installing from a RIS server. When using CD-ROM, each product is installed separately; when using RIS, all available subsets of all available products are offered at once. The suggested workaround when loading these products from a RIS server is to explicitly list the subsets to be loaded, and to load only one product at a time. The suggested order of product loading is: DECnet-Plus for DIGITAL UNIX Wide Area Networking Support for DIGITAL UNIX 2. There is a restriction in the DIGITAL UNIX RIS software that occurs when two subsets with the same name, but different contents, are available to a RIS client. One subset is loaded onto the client system, but the individual files are verified against the second subset. This can occur with the DNANETMAN400 subset, which is shipped with two different DIGITAL UNIX layered products: DECnet-Plus and Wide Area Networking Installation Notes 2-3 Support for DIGITAL UNIX (X.25). The only available workaround is to not duplicate the subset. (If you want to configure the Wide Area Networking Support for DIGITAL UNIX software (X.25) for use with Version 4.0 of DECnet-Plus for DIGITAL UNIX, use the release of the Wide Area Networking Support for DIGITAL UNIX software that is currently available for DIGITAL UNIX Version 4.0. See the latest Wide Area Networking Support for DIGITAL UNIX Software Product Description (SPD) for product release information.) 2.8 Graphical User Interface for Basic and Advanced Configuration You can now use a graphical user interface for either the basic or advanced configuration procedure. The interface is available by command and is also integrated into the Common Desktop Environment (CDE), the default Windows manager for DIGITAL UNIX Version 4.0. 2.9 Restart X Server to Display X Window System Applications After installing DECnet-Plus on a workstation, you cannot display remote X Window system applications using DECnet- Plus until the X server is restarted. You can accomplish this by rebooting. 2.10 Removing the DECnet-Plus Software Be aware of the following considerations when deleting DECnet-Plus software from your system: o If you are removing more than one subset from your system, make sure that you specify the network management subset, DNANETMAN400, last. Without the network management subset still installed, you cannot delete other subsets. o Other DIGITAL software products require the DNANETMAN400 software subset. Before deleting DNANETMAN400, make sure that it is not needed by other products you have installed. For example, the Wide Area Networking Support for DIGITAL UNIX product (X.25 software) requires this subset. 2-4 Installation Notes See the other DIGITAL software products' documentation to determine if they require DNANETMAN400. 2.11 Shutting Down DECnet-Plus While the CTF Collector Daemon (ctfd) Is Running Running the DECnet-Plus shutdown script decnetshutdown while the Common Trace Facility (CTF) Collector Daemon (ctfd) is running causes ctfd to permanently stop listening for incoming DECnet connections. If DECnet is restarted, ctfd does not resume listening for DECnet connections. To make ctfd listen for DECnet connections, you must terminate ctfd (using the kill -KILL command), then restart it. Installation Notes 2-5 3 ________________________________________________________________ Network Management This chapter describes special considerations that network managers need to understand before installing DECnet-Plus for DIGITAL UNIX. Management issues for DECdns and DECdts are discussed in Chapters 4 and 5, respectively. 3.1 Event Logging-Disabling the Event Dispatcher To disable the event dispatcher entity using the disable event dispatcher command, first disable all the children /subentities (the outbound stream, phase IV relay, and sink subentities). If any of these subentities are enabled, the disable event dispatcher directive fails. An error message states that the outbound stream entities are still enabled. Other subentities might be enabled besides the outbound stream entity. 3.2 Using Wildcards to Display Subentities May Cause NCL to Hang NCL may hang if you use wildcards to display all subentities, and no subentities exist to be displayed. If this occurs, press Ctrl/C to return to the ncl> prompt. 3.3 Documentation Corrections for the DECnet-Plus Network Control Language Reference Manual Note the following corrections to the existing version of the DECnet-Plus Network Control Language Reference manual. For each section noted, replace the existing information with the corrected information. o Section 21.2.2-Routing Characteristic Attributes Network Management 3-1 probe rate Support: End Default: 20 Value for DIGITAL UNIX: 1-65535 Default: 1000 Value for OpenVMS: 1-65535 o Section 23.2.2-Token Ring Station Characteristic Attributes station address Default: Hardware ROM Value: None address The desired station address. The bits in each byte of an address must be reversed, for example, 08-00-2b- 11-22-33 becomes 10-00-d4-88-44-cc. This attribute can only be set in the off state. o Section 26.3-x25 protocol dte pvc Syntax create [node node-id] x25 protocol dte dte-name pvc channel integer pvc-name packet size integer window size integer delete [node node-id] x25 protocol dte dte-name pvc pvc-name set [node node-id] x25 protocol dte dte-name pvc acl access-control-list pvc-name channel integer packet size octets window size integer show [node node-id] x25 protocol dte dte-name pvc all [attributes] all characteristics pvc-name all counters all identifiers all status 3-2 Network Management Network Management 3-3 4 ________________________________________________________________ General Software Notes This chapter describes special considerations and undocumented software features. 4.1 New Functionality of DECnet-Plus Mail-11 (OpenVMS Mail) Agents Starting with Version 4.0 of DECnet-Plus for DIGITAL UNIX, the Mail-11 (OpenVMS Mail) agents distributed with DECnet- Plus are set up to automatically encode and decode 8-bit mail messages as Multipurpose Internet Mail Extension (MIME) messages using the quoted-printable content- transfer-encoding as established by RFC 1521. In addition, header fields (such as the subject field and the personal name) that contain 8-bit or illegal (in context) characters are encoded as defined by RFC 1522. To read these messages properly, you need a MIME-capable mail reader (for example, the CDE mail application dtmail, exmh, or Eudora). You can prevent mail11d (OpenVMS Mail-11 -- > SMTP) from encoding and decoding 8-bit mail messages as MIME messages by creating a /var/dna/defaults/Dnetrc.defaults file and adding the following line: mail11d.DoMIME: Off If you only want to prevent the OpenVMS Mail agents from converting the message body to quoted-printable encoding, add the following line instead: mail11d.DoQP: off General Software Notes 4-1 If an 8-bit character is detected, the OpenVMS Mail software assumes that it belongs to ISO-8859-1. To tell mail11d to use a different character set, add a line similar to the following (specifying, as an example, the ISO-2022-JP character set): mail11d.8BitCharset: ISO-2022-JP Likewise, you can prevent mail11 from doing any MIME processing by adding the following line: mail11.DoMIME: Off To disable the conversion of text/plain quote-printable messages back to normal text, add the following line instead: mail11.DoQP: Off 4.2 REMUSER Environment Variable The REMUSER environment variable used by the Session Control application spawner to pass information to the spawned application in DECnet-Plus has a different format from DECnet Phase IV. In DECnet-Plus, the environment variable is given as an end-user specification. For example: DECnet-ULTRIX Phase IV: karen DECnet-Plus for DIGITAL uic=[0,0]karen UNIX: 4.3 OBJECT Environment Variable The application spawner now sets the OBJECT environment variable to the name of the session control application subentity corresponding to the invoked application. For example, OBJECT=CTERM is the environment variable for a network terminal connection. 4.4 No Default Object The Session Control application spawner in DECnet-Plus does not support the notion of the default object. 4-2 General Software Notes 4.5 Problems with the DECwindows Session Manager When using the security dialog menu of the DECwindows session manager on DECnet-Plus, Phase IV addresses are accepted but ignored by the X server. In addition, the DECwindows session manager and xhost both assume that nodes have only one network address. When using xhost, be sure to specify each network address for the node, using %x; for example, %x49000caa000400503021. You can display the NSAP for a node by using the following command on that node: # nodename -n 4.6 Using the DECnet-Internet Gateway The following notes refer to the gateway. 4.6.1 PWD and XPWD Commands Not Implemented The PWD and XPWD FTP commands are not implemented for use through the FTP to DECnet part of the DECnet-Internet Gateway for this release. 4.6.2 Telnet If you are logged on to a DIGITAL UNIX system and you want to use the DECnet-Internet Gateway that is installed on another DIGITAL UNIX system, you must use the telnet -l option to specify the login name. You should specify the -l option after the host name. 4.6.3 Using the Gateway for Remote Login If you are using the DECnet-Internet Gateway for remote login from DECnet-Plus to Internet and if the remote Internet system is a DIGITAL UNIX or other telnetd implementation that accepts the USER environment variable, it attempts to log you in on the remote Internet system as user daemon. Simply press Return at the password: prompt to get a new login prompt. General Software Notes 4-3 5 ________________________________________________________________ Programming Issues This chapter describes special considerations for network application programming in the DECnet-Plus for DIGITAL UNIX environment. 5.1 Using the getnodename Subroutine The getnodename(3dn) subroutine uses getnodeent(3dn) internally; therefore, you must copy the node name into a local structure if it is to be preserved. Because DECnet-Plus for DIGITAL UNIX uses a distributed naming service instead of the local nodes database used for Phase IV, the getnodeent(3dn) subroutine call always returns NULL. The corresponding getnodebyname(3dn) and getnodebyaddr(3dn) calls still function as before. 5.2 XTI Known Problems This section lists known problems with xti. o If data cannot be sent on a non-blocking xti connection because TFLOW has been returned by the t_snd() call, a call to any xti routine other than t_rcv() or t_look() will never return. o If the xti end point is flow-controlled off, a call to t_snddis() will not complete until all data has been read by the remote side or until the remote side disconnects the connection. o t_getstate() does not always return the most current state. To ensure that the state is current, call t_ sync() before calling t_getstate(). Programming Issues 5-1 5.3 DECnet-Plus Libraries The libdna, libdns, and libutc libraries shipped on the distribution kit are re-entrant and thread safe. You do not have to link with the _r versions of these libraries. 5-2 Programming Issues 6 ________________________________________________________________ Unsupported Utilities This chapter describes utilities that Digital Equipment Corporation supplies on an "as-is" basis. These utilities are furnished for general customer use. However, DIGITAL does not offer support for these utilities, nor are they covered under any of DIGITAL's support contracts. 6.1 Unsupported Utilities Subset The unsupported utilities provided with DECnet-Plus for DIGITAL UNIX software are contained in their own subset, DNAUTIL400. 6.2 WWW (World Wide Web) Gateway to DEC Notes DECnet-Plus Version 4.0 for DIGITAL UNIX includes webnotesd, an unsupported application that allows WWW (World Wide Web) clients access to DEC Notes conferences on the same network as the DECnet-Plus system. 6.2.1 Configuring webnotesd To enable this gateway, choose a TCP/IP port for webnotesd. Because webnotesd is an HTTP server, a reasonable choice would be the HTTP port (port 80) unless that port is already being used by another HTTP server. Add the following line to /etc/services (we are using an example port of 8080): webnotesd 8080/tcp # WWW --> DECnotes gateway Then add the following line to /etc/inetd.conf: webnotesd stream tcp nowait guest /usr/lbin/webnotesd webnotesd Unsupported Utilities 6-1 Note that guest can be changed to another login. See the inetd.conf(4) reference page for more details. Then notify inetd.conf of the changed /etc/inetd.conf: # kill -HUP `cat /var/run/inetd.pid` At this point webnotesd should be enabled. 6.2.2 Using webnotesd All URLs understood by webnotesd have a common format. All such URLs are of the form http://hostname:port/local-part where hostname is the name of the system acting as the WWW to DEC Notes gateway, port is the port webnotesd is using, and local-part is the webnotesd specific string that tells it what action to perform. For example, if hostname is www-notes.acme.com and the port is 8080 (as used in the example above), then the URL (minus the local-part) would be http://www- notes.acme.com:8080/. The local part of the URL is composed of one or more tokens, each separated by a '/'. The most common forms are: Example Description anode Perform listing of conferences in NOTES$LIBRARY: on "anode". anode/notes%24sample Show summary of "notes$sample" conference on "anode". anode/notes%24sample/1.0 Show note 1.0 in "notes$sample" conference on "anode". Note that %24 is the URL represententation for the "$" in "notes$sample". The first token is always the DECnet-Plus node name or TCP/IP host name on which the conference resides. (If it refers to a TCP/IP host name, the first character of the name must be an @). The second token is always the conference name. By de- fault, the conference is assumed to be in NOTES$LIBRARY:. However, you may give a full file name, though you need to use the standard rules for special characters in URLs 6-2 Unsupported Utilities (including, but not limited to, any of the following characters: [, ], $, :, <, >). The third token must be either a note-id that refers to a single note (such as "1.0" or "last.0") or a range of notes ("1-last"). So after combining the example URL parts, you would have: http://www-notes.acme.com:8080/anode http://www-notes.acme.com:8080/anode/notes%24sample http://www-notes.acme.com:8080/anode/notes%24sample/1.0 Finally, when webnotesd displays a note, it makes any recognized URLs embedded in the text of the note active. 6.3 tell The tell utility lets you execute commands on a remote DECnet-Plus for DIGITAL UNIX or DECnet-Plus for OpenVMS node or any Phase IV or Phase V call supporting tell. If the remote DECnet-Plus for OpenVMS system does not have tell, copy the file /usr/examples/decnet/TELL.COM. (The user name and password give you the access and privileges you need to execute the remote command.) You can use the tell command in this format: tell node-id[/username/password] command where node-id is the DECnet node name or DECnet node address of the remote node at which you want to execute the command, username is the name for a remote user account, password is the password for a remote user account, and command is the remote command that executes on the remote node. In this example, the show time command executes on the OpenVMS node TUPELO: tell tupelo sho time 10-FEB-1996 10:25:15 To execute more than one command on a remote system, simply type tell. The tell utility prompts you for a node name or address and then for the commands that you want to execute. When you finish entering commands, press Ctrl/D to return to the local shell. Unsupported Utilities 6-3 You can enter a local command during a tell session by beginning the command with a tilde (~) and pressing Return, which puts you in local mode. You receive this prompt when you enter local mode (~LOCAL>) where LOCAL is the name of the local node. For a list of local commands, type a question mark (?). _______________________ Note ________________________ With tell, you can use only single line commands that generate output. The tell utility does not let you pass control to another program, such as mail. If you use tell to run a program and the program issues a read request, the request fails. Also, you cannot use tell to run cursor-manipulating programs. _____________________________________________________ 6.4 nfi The nfi utility tests network programs. This utility accepts commands that let you do the following: o Connect to a program on a remote system o Bind a name to a socket and wait for a connection o Build and send data and interrupt messages o Receive and display data and interrupt messages o Close the connection You can use nfi to debug pairs of programs that use a protocol; you can debug each end of the protocol separately. To display the nfi commands, enter nfi and type help: NFI (Network Functions Interface) V1.01 25-Apr-92 Local node: acme:.foo.bar (%x49000108002b2e2d2e20) 6-4 Unsupported Utilities nfi> help ***nfi (network functions interface) V1.01 *** ABORT [data {data}..] ACCEPT [DEFER] {wait_time} BIND "objnam" | objnum CONNECT node[["access"][::]] OBJECT {"objnam"|objnum} ... [data {data}..] CONNECT {REJECT | ACCEPT} [data {data}..] CONVERT data DISCONNECT [data {data}..] EXIT HELP | ? RECEIVE [WAIT seconds] SEND DATA [data..] SEND INTERRUPT data [data..] (16 bytes maximum) SET DISPLAY DECIMAL | OCTAL | HEXADECIMAL | BINARY ... | ASCII | RAD50 SET RECEIVE ON | OFF SET SOCKET socknum | OPTION |DOMAIN | TYPE | PROTOCOL| ... |BLOCKING | NONBLOCKING SHOW LAST SEND | RECEIVE SHOW RECEIVE | SOCKET | DISPLAY node: area.node | node_name @'filename' - command file data: decimal | .decimal | \octal | #binary | %rad50 ... | $hex | "ascii string" nfi> exit Exiting... % Note that nfi polls for both normal and out-of-band messages when you use the recv command. 6.5 gatewayd The gatewayd utility lets you use a DIGITAL UNIX system as a gateway to swap transports for an application protocol. For example, a client on a TCP/IP-only DIGITAL UNIX system might want to communicate with a server on a DECnet-only OpenVMS system. Even if client and server both use the same protocol (for example, X11), the lack of a common underlying transport prevents communication. However, if Unsupported Utilities 6-5 you insert a DIGITAL UNIX system with both DECnet-Plus and TCP/IP between the two, it can act as a gateway. The DIGITAL UNIX system acting as gateway must run some program that swaps application data from DECnet to Internet and vice versa. The gatewayd utility performs such a function. The gatewayd utility employs two sockets, one in the DECnet domain and one in the Internet domain. Once the necessary connections are established, gatewayd simply reads whatever is available on the DECnet socket and writes it to the Internet socket. Similarly, gatewayd reads whatever is available on the Internet socket and writes it to the DECnet socket. There are two types of connections, as follows: __________________________________________________________ Connection Client System Server System __________________________________________________________ OpenVMS to DIGITAL OpenVMS DIGITAL UNIX UNIX DIGITAL UNIX to DIGITAL UNIX OpenVMS OpenVMS __________________________________________________________ See the README file in /usr/examples/decnet/gatethru/README for further details. 6.6 DEC Notes Clients Two DEC Notes clients are provided. One is an OSF/Motif X-window-based client xnotes and the other is a video terminal cursor-based client decnotes. These programs provide interfaces to Notes files. DEC Notes has the same style as VAX Notes, but xnotes does not. Both are experimental and have numerous restrictions, but show the feasibility of Notes clients on DIGITAL UNIX systems. To use xnotes, see the file /usr/doc/xnotes.readme after installing the utility software subset. To use decnotes, see the file /usr/doc/decnotes.readme after installing that subset. 6-6 Unsupported Utilities 6.7 Poor Man's Routing (PMR) for Mail-11/CTERM/DAP The following sections explain support status for Poor Man's Routing (PMR). PMR allows you to go from a DECnet- Plus for DIGITAL UNIX node that does not have a Phase IV-compatible address to a Phase IV node and vice versa. 6.7.1 Mail-11 DECnet-Plus for DIGITAL UNIX now has Poor Man's Routing (PMR) support for Mail-11, for example: mail> send To: DECOSF::"user@nodename.dnet" -or- To: DECOSF::nodesynonym::user 6.7.2 CTERM DECnet-Plus for DIGITAL UNIX has Poor Man's Routing (PMR) support for DIGITAL's command terminal protocol (CTERM). To enable it, use the following command: touch /var/dna/PMRenabled Once enabled, this functionality is similar to CTERM-to- Telnet access. Simply use dlogin or SET HOST to access the PMR gateway. At the login prompt, type: login: nodename:: CTERM PMR support is enabled separately from the Internet Gateway. 6.7.3 DAP DECnet-Plus for DIGITAL UNIX has Poor Man's Routing (PMR) support for the Data Access Protocol (DAP). To enable it, use the following command: touch /var/dna/PMRenabled It is enabled whenever the Internet Gateway is enabled. The use is similar to the DAP-to-FTP mechanism. Instead of supplying a user name/password for access control, you supply a username@nodename/password. For example: $ DIR TIGGER"user@nodename.dnet password":: Unsupported Utilities 6-7 Note the use of .dnet to initiate the DAP-to-DAP mechanism instead of the DAP-to-FTP. Also, .dnet is the pseudodomain used by sendmail to indicate a DECnet host. You do not need to specify a user name/password if you are accessing the default DECnet account, for example: $ DIR TIGGER"@nodename.dnet":: In this implementation, the PMR gateway node simply forwards DAP messages between client and server unchanged. This helps avoid the same problems when going from OpenVMS to DIGITAL UNIX and back to OpenVMS as are experienced going from DIGITAL UNIX to OpenVMS and back to DIGITAL UNIX. The only message this gateway may not pass unchanged is the DAP configuration messages which contain the DAP buffer size being negotiated. If the client or server tries to negotiate a buffer size greater than the maximum TSDU size, the gateway lowers the requested buffer size. 6.8 Converting node::user to user@fullname.dnet A shell script exists that converts all occurrences of the form node::user in a file to the form user@fullname.dnet where node is a known node synonym and fullname is the corresponding full name. It is named /usr/field/caliases (for "Convert ALIASES") because if given no file name for arguments, it defaults to operating on /var/adm/sendmail /aliases. 6-8 Unsupported Utilities 7 ________________________________________________________________ DECdns This chapter discusses DECdns naming service considera- tions. 7.1 DECdns Changes for Version 4.0B This section describes changes to the DECdns server and clerk contained in the mandatory update (MUP) V4.0B. 7.1.1 DECdns Server Changes for Version V4.0B The DECdns server software includes the following changes: o All DECnet directories were created with insufficient rights access to be replicated later on another server. This problem has been corrected. o Removing the last record caused the server to crash. This problem has been corrected. o Background skulks caused the DECdns server to crash due to the stack being too small. This problem has been corrected. o For large namespaces, the server image used excessive amounts of memory over a period of a few days. This problem was caused by a memory leak in the link_handler and has been corrected. o Creating an additional clearinghouse/server for a namespace is now done through dnsconfigure instead of dna_decdns_createns. DECdns 7-1 7.1.2 DECdns Clerk Changes for Version V4.0B The DECdns clerk software includes the following changes: o The clerk was looping due to intermittent incorrect behavior of the dthread_get_expiration() call. This problem has been corrected. o Memory corrupted and the clerk or advertiser looped when attempting to insert or read an attribute. This problem has been corrected. o The clerk sometimes looped when there was a failed connection to DECdns servers. This problem has been corrected. o Connection handling by the DECdns clerk tended to use too much memory. This problem has been corrected, and the DECdns clerk now requires less memory. o Previously, if you specified in dnsclerk.events or dnsd.events that you wanted all events to be captured, event log files and clerk trace log files dnsclerk_pid_ *.trace would fill up the disk quickly. A new feature allows you to limit the size of these log files by specifying the number of records. When there are more than x number of records written to either of these files, they are purged of records for a fresh start. To limit the size of the file to contain no more than 10,000 records, put the following two lines in the file dnsclerk.events or dnsd.events. * 10000 The asterisk specifies that all events should be captured. The 10000 specifies the maximum number of records written before the event and trace log files are overwritten. o The clerk events log file is no longer placed in the /tmp directory. Instead, it is now placed in /var/dss /dns/dnsclerk. 7-2 DECdns 7.2 Creating and Initializing a New Namespace You only need to create a new DECdns namespace if you are configuring the first DECdns server for the network (no DECdns namespace exists) or if you are creating an additional namespace. When you create a namespace, you need a namespace nickname and clearinghouse name. The namespace nickname is part of the full name of every system subsequently configured in the network and should be unique to your network. The namespace nickname that you specify becomes the actual name of the namespace. On DIGITAL UNIX systems, you now create and initialize a namespace independently of the DECnet-Plus configu- ration procedure. The steps are described in detail in Section 7.2.1. The DECnet-Plus DECdns Management and DECnet-Plus Planning Guide will reflect this change in future releases. 7.2.1 Creating a Namespace on DECnet-Plus for DIGITAL UNIX Systems To create a namespace on a DECnet-Plus for DIGITAL UNIX system: o The DECdns Server subset (DNADECDNSSRVnnn) must be installed on your system. o Your system must be configured as a DECdns clerk. Before creating and initializing a new namespace, DIGITAL highly recommends that you at least read the section on "Basic DECdns Namespace Planning for DECnet-Plus" in the DECnet-Plus Planning Guide. Once you understand what is involved in creating a namespace, you can proceed by choosing option 5 in the configuration menu. Use option 5 in the dnsconfigure program to configure the DECdns server software with a new namespace. The program asks the following questions as part of creating and configuring a new namespace. o Whether you want to proceed with creating a new namespace. Do you wish to create a new namespace? (y/n) [n] DECdns 7-3 o The namespace nickname. What is your namespace nickname? [No Default]: For suggestions on choosing a namespace nickname, refer to the section in the DECnet-Plus Planning Guide called "Guidelines for Naming Namespaces." o The name of the clearinghouse. Enter the name for the clearinghouse: [root_ch] For suggestions on naming a clearinghouse, refer to the section in the DECnet-Plus Planning Guide called "Guidelines for Naming Clearinghouses." o Whether there will be Phase IV nodes participating in the network. * Will any Phase IV nodes participate in the network (y/n, Def=y): If this namespace is going to include Phase IV systems, answer yes and press Return. If the namespace will include only DECnet-Plus and OSI systems, answer no and press Return. If you answer no to this question, you are not prompted for any more Phase IV information and the configuration continues from this point. o Which Phase IV prefix value will you use for Phase IV compatible addresses? * Network IDP value (afi:idi:predsp, Def=49::): Enter the prefix value (IDP) you specified as part of your Phase IV compatible address and press Return. The default value for this question is the Phase IV prefix that you entered previously. o How many Phase IV areas will your network have? * Maximum Phase IV area to use (1-63, Def=63): This information is used for creating backtranslation directories that help establish communication between Phase IV and DECnet-Plus systems. Enter a number that corresponds to the highest number you plan to use for Phase IV areas in your network. For example, if your network will have only areas 1, 2, 3, and 5, enter the number 5 and press Return. Backtranslation directories can use considerable disk space, so create only as 7-4 DECdns many as you plan to use. The default answer for this question is 63. For more information on backtranslation directories, see the DECnet-Plus Planning Guide. The node should be properly configured in an existing DECdns namespace (or with the Local Naming Service) before attempting to create the new namespace. The process of creating the namespace may cause one or more DECnet-Plus events to be generated and displayed to the system console. These are a normal part of the namespace creation, and reflect the attempts of the DECnet software to interact with an incomplete DECdns namespace. For more information, see DECnet-Plus Network Management. 7.2.1.1 Example Creating Namespaces and Directories When you execute option 5 to create a namespace, dnsconfigure creates and initializes any directories you specify as part of the full name, as well as the DNA_Registrar, DNA_NodeSynonym, DNA_GlobalTimeServers, and DNA_BackTranslation directories. The time it takes to create directories varies depending on how many backtranslation directories you specify. The following example provides sample output from creating and initializing a namespace with dnsconfigure. # /usr/sbin/dnsconfigure DECdns Configuration [1] Set the default namespace [2] Establish communications with an off-LAN server [3] Configure server in an existing namespace [4] Show address information of this node [5] Create and initialize a new namespace [6] Exit At anytime, you can enter ? for help or ^D to quit the current operation Pick a number from the list: 5 There will be a pause while this procedure gathers some information from your system. DECdns 7-5 Do you wish to create a new namespace? (y/n) [n] y The namespace nickname is the name given to the collection of data stored among the distributed DECdns servers. Please enter the name of the DECdns namespace you wish to create. What is your namespace nickname? [No Default]: TRIX_12996_NS The clearinghouse contains all the data stored by the DECdns server. It must be given a name, and this name will itself be stored in the namespace as an object in the root directory. You may accept the default clearinghouse name offered below, or enter a name of your own choosing. Enter a name for the clearinghouse: [root_ch] Please review the following information which you have supplied, and if it is correct enter "Continue", which will invoke the DECdns server software and create the namespace. If there is incorrect information, or you wish to change a particular value, enter "Quit" and rerun this procedure. Namespace Nickname: TRIX_12996_NS Clearinghouse Name: root_ch Do you wish to complete this configuration? [continue] Creating the TRIX_12996_NS namespace. Your default namespace nickname is TRIX_12996_NS. Having created a new namespace, the initial directories will be created. You will be informed of any additional tasks to perform, which can be done after this procedure is completed. Create the initial namespace directories. Press Control-D at any question to cancel the initialization. * Will any Phase IV nodes participate in the network [y/n, Def=y]: * Phase IV prefix value [afi:idi:predsp, Def=49::]: * Maximum Phase IV area to use [1-63, Def=63]: 20 The DECdns namespace groups and directories will now be created. This might take up to 24 minutes or more, depending on the speed of the DECdns server system and the amount of traffic on the network. 7-6 DECdns Creating the TRIX_12996_NS:.DNA_Registrar group. Creating the TRIX_12996_NS:.DNA_BackTranslation directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49 directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X0001 directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X0002 directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X0003 directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X0004 directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X0005 directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X0006 directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X0007 directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X0008 directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X0009 directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X000A directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X000B directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X000C directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X000D directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X000E directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X000F directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X0010 directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X0011 directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X0012 directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X0013 directory. Creating the TRIX_12996_NS:.DNA_BackTranslation.%X49.%X0014 directory. Creating the TRIX_12996_NS:.DNA_NodeSynonym directory. Creating the TRIX_12996_NS:.DTSS_GlobalTimeServers directory. DECdns namespace initialization for DECnet use is complete. After the directories are created, you receive infor- mational messages about more namespace-related tasks to perform. These messages present several screens of information. You must press Return to advance to each series of screens, as in the following example. * Press RETURN to continue To do any further work on this newly created namespace, use decnet_register to: - Create an export file to automatically register previously defined Phase IV nodes. Do this function before you manually register any other nodes using decnet_register. DECdns 7-7 - Create any directories you need for node names that should be registered immediately, according to your transition plan. This includes the node you are currently running on. - Change the local node's registered name from its default name to its final full name. The local node will be registered as a Phase IV node with a default name when you execute the Phase IV node registration command file above. - Change the currently registered names of other nodes from their default names to their final full names when appropriate (for example, when they are upgraded to run DECnet-Plus software). * Press RETURN to continue In addition, you should use decnet_register to: - Create any additional directories you need for node names, as you add new nodes to the network according to your transition plan. - Register new nodes as they are brought up on the network. - Add members to the TRIX_12996_NS:.DNA_Registrar access control group. Additionally, you can use the DECdns control utility to: - Add specific access control to individual directories, objects, and soft links. - Create replicas of directories. * Press RETURN to continue The following were created: Group: TRIX_12996_NS:.DNA_Registrar Directory: TRIX_12996_NS:.DNA_BackTranslation Directory: TRIX_12996_NS:.DNA_BackTranslation.%X49 Directories: TRIX_12996_NS:.DNA_BackTranslation.%X49.* Directory: TRIX_12996_NS:.DNA_NodeSynonym Directory: TRIX_12996_NS:.DTSS_GlobalTimeServers * Press RETURN to continue Attempting to register this node in the namespace. Registering the node TRIX_12996_NS:.tricks Type is DECnet-Plus Synonym is trix 7-8 DECdns This node is registered in the TRIX_12996_NS namespace. Updating address towers for node object TRIX_12996_NS:.tricks ... done Adding this account (i.e. TRIX_12996_NS:.tricks.root) to DNA_Registrar group. Adding member TRIX_12996_NS:.tricks.root to TRIX_12996_NS:.DNA_Registrar. dna_decdns_createns completed successfully. If the newly created namespace will be used for storing the names and addresses of Phase IV nodes, you should use the update_nodes utility (see DECnet-Plus Network Management) to transfer a copy of the network's Phase IV node database to a database file on the local system. This database file can be used by decnet_register to create an export file, which you can use for adding the Phase IV nodes to the DECdns namespace. 7.3 DECdns Server Joining Existing Namespace To join an existing namespace, the new server system must be configured as a clerk in the namespace and the following items must be verified. o It has a node object registered in the namespace, for example use the following DECdns Control Program command: dnscp show obj ns:.newsrv o The node object has the correct addressing information, for example: dnscp show obj .newsrv dna$towers The output should match output of ncl show addr. o The DECdns server with the master replica of the directory to be joined should be registered in the namespace, should have correct addressing information, and each system should be able to connect to the other (for example, dlogin). Also, if the master replica is running on a DECnet-Plus system, the answer to the "directory version" question should be #2, V2.0.0. DECdns 7-9 7.4 Limitation for Number of Members in a Single Group DECdns has an internal limitation of 100 for the number of members (principals) that may be stored in a single group. If this limitation is exceeded, the server process can crash during the skulk procedure. This skulk does not have to happen immediately, and may occur up to 24 hours after the group size limit was exceeded. This can make diagnosis of the problem more difficult, due to the indirectness of the symptoms. This problem affects DECdns servers (OpenVMS, ULTRIX and DIGITAL UNIX) that use groups to control access to objects stored in their DECdns namespaces. The workaround for this problem is to limit the number of entries to less than 100. DIGITAL recommends that no group contain more than 75 members. A simple way to limit the number of members in any one group is to create subgroups that are members of the original group. For example, an administrator wants to create a group with 200 members who all have authorization to manage a certain directory in the namespace. The group will be called .dir_admin. Two possible solutions are: o Create three groups called .dir_admin_a_to_f, .dir_ admin_g_to_l, and .dir_admin_m_to_z. These three groups are entered as the only three members of the group .dir_admin. Each contains a part of the alphabetically sorted list of members. o Create subgroups that use some other partitioning algorithm, such as by site code, or group function instead of the alphabet as used in solution 1. 7.5 Location of DECdns Sockets DECdns sockets are located in /var/dss/dns. 7-10 DECdns 7.6 Location of DECdns Clerk Backing File The backing file on disk for the DECdns clerk cache is located in: /var/dss/dns/dns_cache To delete the cache and restart the clerk: # dnscp disable dns clerk # dnscp delete dns cache # rm /var/dss/dns/dns_cache # dnscp create dns clerk # dnscp enable dns clerk 7.7 DECdns Clerk Software on Nodes with Extended Addresses Clerks on nodes with extended addresses (without DECnet Phase IV-compatible addresses) can communicate only with DECdns Version 2 servers, not with DNS Version 1 servers (which are DECnet Phase IV nodes). You need a DECnet Phase IV-compatible address to communicate with a DECnet Phase IV node. 7.8 Problem with dump dns clerk cache Command You may not be able to use the dump dns clerk cache command more than once during an invocation of the DECdns control program: dns> dump dns clerk cache A symptom of this problem can be an error message indicating improper syntax, such as the following: dns> dump dns clerk cache usage: cadump -m Cacheid; or: cadump -n filename You can avoid this problem by entering the dump dns clerk cache command from the shell command line as follows: > dnscp dump dns clerk cache DECdns 7-11 7.9 High Convergence Directories Not Recommended If any of your DECdns directories are set to high convergence (DNS$Convergence = high), DIGITAL strongly recommends that you reset them to medium convergence. The high convergence setting is intended only for temporary use in limited, troubleshooting situations. Directories that are permanently set to high convergence can, in certain cases, cause excessive network and memory usage- possibly leading to a database corruption. Some elements of this behavior are defects that may be corrected in a future release of DECdns. Permanent use of the high convergence setting, however, will continue to be discouraged. To set a directory's convergence to medium, use the following dnscp command: dns> set directory DNS$Convergence = medium 7.10 Replicating the DECnet-Plus Directories The following are specific guidelines for replicating the directories that contain node object entries, node synonyms, and backtranslation soft links: o If a directory contains node object entries, locate at least one replica (preferably the master) on the same LAN as the nodes the entries describe. o Locate at least one replica of the .DNA_NodeSynonym directory on every LAN that includes DECnet-Plus nodes. o Locate the master replica of each .DNA_BackTranslation area directory in the area it is named after, if that area contains DECnet-Plus nodes. Also replicate an area directory in other areas likely to communicate most frequently with the nodes whose addresses it contains. o In a solely WAN environment, try to replicate every directory so that each can be reached reliably by any DECnet-Plus system that needs it. 7-12 DECdns 7.11 Clarification of "World" Access in DNS and DECdns The DNS Version 1 principal expression *::* and the DECdns Version 2 principal expression .*... permit access to any user on any node, but only within the particular namespace in which the access control entries (ACEs) containing these expressions were created. Because users are not required to enter a namespace nickname as part of a principal expression and, because DNS Version 1 does not display the namespace nickname associated with the principal expression of ACEs, many DNS Version 1 users have logically assumed that both *::* and .*... can be interpreted as any user, on any node, in any namespace. This is not the case. 7.12 Clerk Not Enabled Error Message If you delete the DECdns clerk shared memory segment (shared memory key is of the form 57xx), you receive clerk not enabled error messages when clerk operations are attempted. However, the command dnscp show dns clerk all shows that the clerk is enabled. To fix the problem, run /var/dna/scripts/stop_dns, and then /var/dna/scripts/start_dns. 7.13 Clear Clearinghouse Command Gives Spurious Error When you issue a clear dns server clearinghouse command on a system where only one clearinghouse exists, you receive a spurious data_corruption error even if the command works. 7.14 Show Clearinghouse Command Can Produce Errors The show dns server clearinghouse ch-name all command can return error 3216 on some or all attributes. The reason is probably that a network failure occurred after a clearinghouse was created but before it finished adding its attributes. To solve the problem, stop and restart the server on the system where the clearinghouse exists. DECdns 7-13 7.15 Documentation Correction to Deleting a Clearinghouse In explaining how to delete a clearinghouse, Section 9.6 of the DECnet-Plus DECdns Management should include the following: 1. Locate all directories that have their master replica in the clearinghouse you plan to delete (target clearinghouse). 2. For each of these directories, use the set dir to new epoch command to designate another directory as the master replica (in a clearinghouse other than the target clearinghouse). If no other replicas of the directory exist, create a read-only replica at another clearinghouse and then designate it as the directory's new master replica before you delete the original master replica from the clearinghouse. Avoid using the set dir to new epoch... exclude... command to exclude replicas. 3. Delete each replica until the last replica remaining is the one closest to the root (usually the replica that contains the name of the clearinghouse). 4. Delete the clearinghouse locally (from the server on which the clearinghouse is located). All database files for that clearinghouse will be deleted. 7.16 Documentation Correction to Name Resolution Operations Section 2.4.1, "How Node Synonyms Work," in the DECnet- Plus DECdns Management guide is incorrect. When DECnet- Plus Session Control receives a node name of six alphanumeric characters (one alphabetic character minimum) or fewer that does not contain a leading dot, it first uses local name mapping to resolve the name. If that method fails, Session Control tries to look up the name in the directory referenced by the attribute Session Control node synonym directory which is typically .DNA_ NodeSynonym. 7-14 DECdns 7.17 Documentation Correction to "Adding Group Access" Procedure In the DECnet-Plus DECdns Management guide, Section 5.3.2, "Adding Access for Your Namespace Administrator Group," the first and second examples under "To Add Full Access" are incorrect. You must specify the as group qualifier as shown in the following corrected examples: dns> add directory . access .DNS_Admin as group for r,w,d,t,c dns> add directory . default access .DNS_Admin as group for r,w,d,t,c 7.18 Documentation Correction to "Denying Group Access" Example In the DECnet-Plus DECdns Management guide, Section 5.2.4, "Using Null ACEs to Deny Access," the second example is incorrect. Null ACEs are only valid for explicit principals. They are not valid for implicit or explicit groups. While it is possible to add such an invalid ACE using the DECdns Control Program (dnscp), the ACS processing will ignore it. 7.19 Documentation Additions to Clearinghouse Creation Procedure The following information supplements the existing documentation in Section 10.4.2, "Configuring a Server," and Section E.3.2, "Allowing a Directory to Store Clearinghouse Object Entries," in the DECnet-Plus DECdns Management guide. If you specify an initial replica directory other than the parent directory of the clearinghouse name (the default), you must set the DNS$InCHName attribute to TRUE on that directory as well (even if you do not intend to store clearinghouse object entries in it). Details on clearinghouse creation failures can now be found in the DECdns server log file /usr/tmp/dnsd_ nnnn.log. DECdns 7-15 7.20 Documentation Correction to delete child Command Example The command example appearing on the reference page for the delete child command in Chapter 11 of the DECnet-Plus DECdns Management guide is incorrect and should read as follows: dns> delete child .sales.east Note that no error message is displayed. 7-16 DECdns 8 ________________________________________________________________ DECdts This chapter discusses considerations for the DECdts time service. 8.1 Changing the Time Differential Factor (TDF) The DECdts Network Control Language (NCL) management interface does not offer a command for modifying the time differential factor (TDF) information because the operating system performs this function. DIGITAL UNIX maintains all internal time values in Coordinated Universal Time (UTC); UTC values are converted to local time values for display or output. UTC-to-local-time conversions follow rules defined by the file /etc/zoneinfo/localtime. This file points to the database that maintains local time information for the system. For example, if the system is located on the east coast of the U.S.A., the file /etc/zoneinfo/localtime points to /etc/zoneinfo/US/Eastern; if the system is in Germany, /etc/zoneinfo/localtime points to /etc/zoneinfo /CET (Central Europe). To change the current TDF, modify the localtime file to point to the time zone file that matches the system location. If DTSS is running, delete and re-create DTSS for the change to become effective. DECdts 8-1 8.2 Time-Provider Interface (TPI) Advisory Future versions of DECdts that support additional protocols will use a new time-provider interface (TPI). To ease future porting of time-provider programs to new protocol versions, use the sample time-provider programs that are supplied with the kit, with as few modifications as possible. The sample time-provider programs are located in: /usr/examples/dtss. 8.3 Starting a Time-Provider A known problem in the DECdts time-provider interface (TPI) requires that you use the following procedure to start a time-provider program: 1. Stop DECdts by entering the following two commands: % ncl disable dtss % ncl delete dtss 2. Start DECdts manually by entering the following three commands: % dtssd & % ncl create dtss type server % ncl enable dtss set clock true 3. Start the appropriate time-provider program as shown in the following example command: % dtss_provider_spec -d/dev/tty02 & In this example, tty02 is the port to the external time provider source. 8.4 Update to List of Supported Radio Receivers The following note updates information contained in Appendix B, "Time-Providers and Time Services," in the DECnet-Plus DECdts Management guide. Table B-3, Radio Receiver Manufacturers, lists supported radio receivers by manufacturer. Update this list by replacing "Spectracom 8170" with "Spectracom Netclock /2." 8-2 DECdts 9 ________________________________________________________________ FTAM and Virtual Terminal This chapter indicates any issues specific to this release for FTAM and Virtual Terminal on DIGITAL UNIX systems. Please read these notes and the DECnet-Plus for DIGITAL UNIX Installation and Configuration manual completely before performing the installation. 9.1 FTAM This section indicates issues specific to FTAM for this release. 9.1.1 Property List Support This version of FTAM implements property lists to store information related to the FTAM document type. Because this information is now stored transparently rather than as part of the file data, it is no longer necessary to use the ftamconvert utility for files transferred with this version of FTAM. The ftamconvert utility has been modified to convert old format FTAM files into the property list format. Therefore, you should convert any old format FTAM files to the property list format. Failure to do this will result in FTAM sending the old file header as part of the file data. Property lists are not supported over NFS. Therefore, FTAM files copied to NFS mounted disks will not have associated property lists, and document structure information will be lost. In addition, the attempt to set the property list on an NFS mounted disk will cause the responder to log an unaligned access error, which may be ignored. FTAM and Virtual Terminal 9-1 9.1.2 Responder Logging Support This version of FTAM provides limited support for the logging of file transfer operations that involve the FTAM daemon. When acting as a responder, the FTAM daemon, ftamd, logs messages to daemon.log regarding file OPEN access and file CLOSE access. An example of an OPEN message is: Jul 30 10:55:52 bedrck ftamd[18029]: OPEN access (30) from , user=fred, directory=/usr/users/fred, filename=/usr/users/fred/barney.rubble The (30) is a hexadecimal representation of the FTAM processing mode used to open the specified file. In this case, the file was opened with Replace and Extend, which usually indicates that a new file was copied to the system. The following constants are taken from osif.h (which is supplied with the FTAM API) for the processing mode: #define OSIF_PM_READ 0x80 #define OSIF_PM_INSERT 0x40 #define OSIF_PM_REPLACE 0x20 #define OSIF_PM_EXTEND 0x10 #define OSIF_PM_ERASE 0x08 In addition to the OPEN access message, ftamd also generates a message when the file is closed. An example of a CLOSE message is: Jul 30 10:55:52 bedrck ftamd[18029]: CLOSE access (success) from , user=fred, directory=/usr/users/fred, filename=/usr/users/fred/barney.rubble For the CLOSE message, ftamd indicates whether the F- CLOSE-REQUEST had a status of success or failure. Note that a CLOSE message may not be generated for every OPEN message. For example, if the FTAM association is aborted during file transfer, a CLOSE message is not generated. The from field in both the OPEN and CLOSE messages is currently left empty. Support for from may be provided in a future release of FTAM. 9-2 FTAM and Virtual Terminal 9.2 Virtual Terminal There are no release notes for Virtual Terminal for this release. FTAM and Virtual Terminal 9-3 10 ________________________________________________________________ OSAK This chapter describes issues specific to this version of the DECnet[TM]/OSI[R] OSI Application Kernel (OSAK) software and API and SPI programming interfaces. 10.1 New features This section contains information about new features in the OSAK software and programming interfaces. 10.1.1 OSAK Application Programming Interface (API) This version of the DECnet[TM]/OSI[R] OSAK software includes support for the OSAK API, which previously shipped in the OSI Application Developer's Toolkit. 10.1.2 New OSI Session Programming Interface This version of the software includes a new programming interface to the OSI session layer (the SPI). This version of the software also includes SPI example programs, as follows: /usr/examples/osak/spi_example_init.c /usr/examples/osak/spi_example_resp.c More information about this the SPI interface is given in the books OSAK Programming and OSAK SPI Programming Reference. 10.1.3 Listen on Both RFC1006 and OSI Transport With this version of the OSAK software, an OSAK API or SPI application can listen for both RFC 1006 and OSI transport connections with one osak_open_responder or spi_open_ responder call. OSAK 10-1 In order to open a responder to listen for RFC1006 as well as an OSI transport type, set up the parameter block as usual on the osak_open_responder or spi_open_responder call to listen for OSI transport connections, plus specify the TCP port you want (usually 102) in the rfc1006_port parameter. If you want to listen for any type of connection requests, specify a template with transport type ANY and fill in the rfc1006_port parameter. The same application also runs on VMS since the rfc1006_port parameter is ignored on VMS. 10.2 Programming Interface Changes 10.2.1 Called_aei Parameter on A-ASSOCIATE and S-CONNECT Indication Events For A-ASSOCIATE indication events in the OSAK API, and S-CONNECT indication events in the SPI, the nsap field of the called_aei parameter is no longer filled in by OSAK. Previously, the called_aei.paddress.nsap structure contained the values specified in the local_ aei.paddress.nsap parameter on the osak_open_responder or spi_open_responder call. However, these values are not used by osak_open_responder or spi_open_responder and may not contain correct information about the received connection (for example, the transport type). 10.2.2 New Status Code The routines osak_send_more and spi_send_more can now return a status code of OSAK_S_NODATA which indicates that there is no data remaining. In previous versions the status code OSAK_S_INVFUNC may have been returned when this error occurred. 10.2.3 ROSE Minimum Workspace Increased The minimum required size for the parameter block workspace for ROSE has increased. If your ROSE application is using the old minimum workspace size, you will now get a bad parameter error. It is recommended that your application use the constant ROSE_WS_SIZE defined in osak_ api.h to get the correct minimum workspace size. 10-2 OSAK 10.3 Problems Resolved 10.3.1 Wrong NSAP No Longer Output to OSAKtrace File The OSAK software now correctly outputs to the OSAKtrace file the NSAP address which it successfully connected to when a list of NSAPs is given to osak_associate_req or spi_connect_req. 10.3.2 Transport Template Settings Honored All items set in the transport template are now honored by OSAK when establishing a connection. In particular, OSAK no longer always asks for expedited data. Instead, it uses whatever the transport template setting is. 10.3.3 Transport Congestion Problems Relieved OSAK applications may experience transport congestion problems. That is, the system may get the following errors logged: Event: Local Transport Disconnection Reason: Remote transport entity congestion at connect request time DNA error: Insufficient resources This version of the OSAK software has relieved most of this congestion. Most applications will now run without problems. If you are still experiencing problems with this version of OSAK, try increasing the value of one of the following kernel variables to a value of 20 or larger. tposi_info.tp_entity.ea_somaxconn somaxconn 10.4 Known Problems and Restrictions This section contains details of known problems and restrictions in the OSAK software and the OSAK programming interfaces. OSAK 10-3 10.4.1 Incorrect Information May Be Logged To OSAKtrace The OSAKtrace utility may output incorrect transport options on issuing a T_CONNECT request. Compare the information to that provided in the OSI transport traces. If there is any difference, use the output from the OSI transport trace. There is no corresponding problem with received T_CONNECT confirmation. 10.4.2 Closing Port After a Redirect Request After issuing a successful osak_redirect or spi_redirect call, an application can only close the port with the destructive_flag parameter set to OSAK_C_DESTRUCTIVE. 10.5 Documentation Corrections 10.5.1 Using OSAK over RFC1006 On the initiator side, to make a connection over RFC1006, specify as the NSAP the IP address as a 6-byte nibble packed hex value including the port number in the first 2 bytes. For example, the address of 16.36.112.142 on port 102 would be encoded as follows: 102 16.36.112.142 | | | | | 0066 10 24 70 8E In this case, the NSAP would be 00661024708E (hex). Specify the NSAP type as OSAK_C_RFC1006. For the transport template, specify either the pseudo-template "1006" or no template at all. OSAK uses a default template of "1006" if the NSAP type is OSAK_C_RFC1006. On the responder side, to listen for RFC1006 connections, specify as the transport template the pseudo-template "1006". 10-4 OSAK 10.5.2 Compiling API, ROSE, and SPI Applications When compiling your application code that makes calls to OSAK API, ROSE, or SPI routines, the cc command line requires the following: -I/usr/include/osi This is because the OSAK include files are in this directory. For example: /bin/cc -c -I/usr/include/osi -o osak_example_init.o osak_ example_init.c 10.5.3 Linking API, ROSE, and SPI Applications The information in the OSAK Programming book regarding linking OSAK API, ROSE API, and SPI applications on Digital UNIX systems has some errors in it. For all programming interfaces, the list of libraries to be linked against is incorrect. The documentation should read: o (Section 4.9) OSAK API applications should link with: /usr/shlib/libosak.so For example: /bin/cc -o osak_example_init osak_example_init.o -losak o (Section 5.4) ROSE applications should link with: /usr/shlib/libosak.so /usr/shlib/librose.so For example: /bin/cc -o rose_application rose_application.o -lrose -losak o (Section 6.9) SPI applications should link with: /usr/shlib/libosak.so For example: /bin/cc -o spi_example_init spi_example_init.o -losak OSAK 10-5