DIGITAL Software Product Description ___________________________________________________________________ PRODUCT NAME: DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 DESCRIPTION DECnet-Plus for DIGITAL UNIX software (formerly DECnet/OSI for Dig- ital UNIX) is an implementation of the DIGITAL Network Architecture (DNA) for the DIGITAL UNIX operating system. This software supports DNA Phase V, which is the integration of DECnet, OSI, and TCP/IP pro- tocols. This support allows the different network protocol stacks to be available to upper layers as discrete transport services. Upper lay- ers have been implemented as separate towers, enabling existing DEC- net and OSI applications to share available network services. DECnet-Plus software offers the following features: o DECnet for Small Configurations (DNALITE400) o A graphical user interface (GUI) for basic and advanced configu- ration o An OSI Session Programming Interface (SPI) o Remote file transfer o Network virtual terminal o Task-to-task communications o Mail o Coexistence and interoperation with the Internet protocols (TCP/IP based), including the ability to run DECnet and OSI applications over the TCP/IP transport September 1997 AE-Q6ANF-TE DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 o Networkwide resource sharing and management as defined by the DNA protocols o A GUI to the network management facility known as the Network Con- trol Language (NCL) o Expanded naming options, allowing the use of a large local names- pace, DECdns, and/or DNS/BIND as naming services o Network services access point (NSAP) addresses in DECdns and BIND o A configurable routing option (segregated mode) that allows the rout- ing layer to choose a Phase IV router for packets having a Phase IV compatible address DECnet-Plus software and TCP/IP software can share system resources such as local area network (LAN) interfaces. You can modify existing programs running over TCP/IP to run over DECnet-Plus software. You can modify DECnet programs to run directly over TCP/IP if the programs do not make use of operations that are specific to DECnet. Similarly, OSI and DECnet applications or user-written software using the X/Open Trans- port Interface (XTI) can operate over a TCP/IP backbone network us- ing RFC 1006 (for OSI) and RFC 1859 (for DECnet). Depending on the network configuration, networks combining DECnet-Plus systems with other DECnet software might limit certain functions if all products do not support the same features. To determine function availability, compare the products' Software Product Descriptions. DECnet-Plus is available in two forms: End System and Extended Func- tion. See the Software Licensing section for details about each form of license. DECnet-Plus software supports the features described in the follow- ing sections. 2 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 Data Link Layer DECnet-Plus software supports ISO 8802-2 Logical Link Control Type 1 connectionless service over ISO 8802-3 CSMA/CD. DECnet-Plus software also supports Ethernet Version 2.0 packet formats on CSMA/CD devices. For FDDI devices, ISO 9314 FDDI Token Ring Media Access Control is sup- ported. For 802.5/Token Ring devices, ISO 8802-5 Token Ring Access Method is supported. Use of FDDI packets larger than 1500 bytes is supported but requires a DNA Phase V router if the LAN is interconnected to other local area networks. Wide area network (WAN) connectivity is provided using the High-Level Data Link Control (HDLC) protocol and device drivers for point-to-point full-duplex connections. This functionality is included as part of the DECnet-Plus license and installed from the Wide Area Networking Sup- port for DIGITAL UNIX (X.25) software. For a list of supported devices, refer to the Software Product Description (SPD 42.47.xx). Network Layer DECnet-Plus software supports end-system routing only. The network layer supports ISO 8473 Protocol for Providing Connectionless- Mode Network Service (CLNS). In addition to full Connectionless Net- work Protocol (CLNP) header support, DECnet-Plus software supports the inactive subset (null Internet) specified in ISO 8473 as well as the OSI ping function (ISO 8473/PDAMx). Null Internet is the operation of OSI transport directly over a LAN data link. The OSI ping function en- ables a network entity to generate a message that is echoed back to the sender when received by its target destination. Exchange of routing information between end systems and routers uses the ISO 9542 End System to Intermediate System Routing Protocol (ES- IS). Addresses adhere to the ISO 8348 Network Service Definition Ad- dendum 2 specification, allowing the support of large network topolo- gies. 3 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 As long as the network address stays within the addressing range of DNA Phase IV systems (up to 1023 systems per area and up to 63 areas per network) and uses the same initial domain part (IDP), you can use any router that conforms to the DIGITAL Network Architecture. The Net- work layer is able to cache information about the paths that are used to reach remote nodes. You can set the Segregated Routing Mode attribute, which determines a DNA Phase IV router for those packets having a destination address that can be translated to the Phase IV format. All other packets are sent to a DNA Phase V or OSI router, if available. The Network layer supports multicircuit and multihomed end systems. Multicircuit end systems allow up to four circuits to be active si- multaneously. This support increases network reliability and data through- put. Multihomed end systems allow a system to have up to three unique addresses. This functionality allows an end system to have both a DEC- net Phase IV compatible address and a DECnet-Plus extended address. The Network layer supports ISO 8878 Use of X.25 to Provide the OSI Connection- Oriented Network Service (CONS). You can configure OSI Transport classes 0, 2, and 4 to run over a CONS network. In addition to CONS support, DECnet-Plus software allows a properly configured DECnet-Plus system to use CCITT X.25 compliant networks as OSI Connectionless-Mode Net- work Service (CLNS) subnetworks. This functionality is included as part of the DECnet-Plus license and is installed from the Wide Area Net- working Support for DIGITAL UNIX software. The DECnet-Plus software can be used in conjunction with X.25 connec- tivity over LLC2 services (ISO 8881 Use of X.25 Packet Level Proto- col in Local Area Networks). This functionality provides connection- oriented network services over a LAN to another suitably configured X.25 end system on the LAN. It also allows X.25 logical connections to be made through a relay system using LLC2. The LLC2 functionality is included as part of the DECnet-Plus license and is installed from the Wide Area Networking Support for DIGITAL UNIX software. 4 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 A Wide Area Networking Support for DIGITAL UNIX software license is required when you connect a system directly to a packet switch data network (PSDN) using the X.25 and Link Access Protocol Balanced (LAPB) protocols. For more information, see the Wide Area Networking Support for DIGITAL UNIX Software Product Description (SPD 42.47.xx). Transport Layer The Transport layer supports OSI and DECnet protocols. The DECnet-Plus software supports the OSI transport protocol as specified in ISO 8073 Connection-Oriented Transport Protocol. The OSI transport supports classes 0, 2, and 4 (also known as TP0, TP2, and TP4). Classes 0 and 2 work only on CONS. Class 4 works with either CONS or CLNS. The DECnet-Plus software also supports ISO 8602 Connectionless Trans- port Service (CLTS). CLTS provides a datagram transport service. The Network Services Protocol (NSP) is the supported DECnet transport protocol. NSP offers communications between DECnet systems and pro- vides backward compatibility with DNA Phase IV systems. DECnet and OSI Applications over TCP/IP The DECnet-Plus software supports OSI applications over TCP/IP (In- ternet RFC 1006). RFC 1006 defines a specification for running OSI ap- plications over TCP/IP. Operation of FTAM and Virtual Terminal over a TCP/IP network is supported. Implementation of RFC 1859 allows DECnet applications to run over TCP /IP. The supported applications include all licensed DECnet applica- tions as well as layered products and user-written applications that conform to the documented DECnet programming interfaces. DECnet-Plus for OpenVMS (Version 6.0 and later) also provides this functionality, enabling interoperation of OpenVMS and DIGITAL UNIX DECnet applica- tions over a TCP/IP backbone. 5 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 OSI Upper Layers DECnet-Plus software supports the Session, Presentation, and Appli- cation layers. The Application layer provides Association Control Ser- vice Elements (ACSE) and Remote Operations Service Element (ROSE) ser- vices. DECnet-Plus software also includes the DIGITAL implementation of OSI File Transfer, Access, and Management (FTAM) and Virtual Ter- minal (VT) protocols. OSI applications can run over Transport layer classes 0, 2, or 4 over CONS and TP4 over CLNS. OSI applications can also run over TCP/IP net- works using RFC 1006. OSI Application Programming Interfaces The OSI application programming interfaces (APIs) enable users to write distributed applications that communicate over open networks and use the OSI services provided by DECnet-Plus. The following APIs are provided under the Extended Function license and permit application writers to use the services of the OSI upper layers in their applications: o An interface to FTAM (File Transfer, Access, and Management) o Interfaces to the ACSE (Association Control Service Element) and Presentation layers o An interface to ROSE (Remote Operations Service Element) o A direct interface to the services provided by the Session layer. This interface is called the session programming interface (SPI). The APIs allow for the development of customer and third-party OSI ap- plications on DECnet-Plus systems. An application's source code must be compiled with the API header files and linked against the appro- priate API shareable library. You can run the resulting application image on any DECnet-Plus for DIGITAL UNIX system with the appropri- ate API library installed. The API header files are shipped through DECnet-Plus programming tools, which is an optional subset in the DECnet-Plus software kit. 6 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 For more information about the APIs, see Appendix C. Network Management The DECnet-Plus network management software allows system or network managers to: o Control and monitor the operation of a network o Configure network operating parameters o Modify and display directory service name templates and search paths o Start up and shut down network components as needed o Monitor network traffic and performance o Detect, isolate, and repair network problems In addition, the network management software can provide information that warns network managers of faulty or failing network components, both hardware and software. NCL (Network Command Language) is the utility provided for managing management operations. Network managers can access NCL through either the command line interface or the graphical user interface (GUI). The GUI allows network managers to view the status of network components and control those components from a Motif-based window interface. Network managers can also use NCL to test specific components of the network and to isolate network problems. NCL enables transmission and reception of test messages either between systems or through controller loopback arrangements. They can then compare the messages for possi- ble errors. DECnet-Plus software provides network event logging to a terminal de- vice, disk file, or remote system. Network managers can use NCL to en- able and disable the event logging facility as well as to optionally filter specific events. 7 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 Problem-solving is facilitated by the Common Trace Facility (CTF). CTF enables network managers to trace and analyze frames passing between the network and the DECnet-Plus system through the interfaces and pro- tocols of the DECnet and OSI stacks. Network managers can trace NSP, OSI Transport, Routing, and RFC 1006. DECnet-Plus software supports installation, management, and down load- ing by way of ISO 8802-3 CSMA/CD, Ethernet, and FDDI using the Main- tenance Operation Protocol (MOP) to DIGITAL servers, routers, portals, and gateways. To determine if a product supports DECnet-Plus software, refer to that product's Software Product Description. MOP is a management protocol used for lower-level communications with a system that is either not fully operational or being tested. You can configure MOP or run it standalone without installing all of DECnet- Plus. A DECnet-Plus license is not required for standalone MOP oper- ation. Name Services DECnet-Plus provides simple access to the node name and addressing in- formation stored in one or more directory services. Three name ser- vice options are supported: o Local namespace-Stores names and address information locally in database files o DECdns distributed namespace-Stores names and address information in the DIGITAL Distributed Name Service (DECdns), a global name ser- vice (includes both clerk and server configurations) o DNS/BIND-Retrieves names and Internet or NSAP addresses from a DNS /BIND name server When configuring a node, the system administrator can elect to use any combination of the Local namespace, the DECdns distributed namespace, and DNS/BIND. DECnet-Plus provides access to the Local namespace or to a DECdns server running on an OpenVMS VAX, DIGITAL UNIX, or ULTRIX system. 8 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 The decnet_register namespace management tool centralizes and simpli- fies namespace management tasks by replacing functionality previously provided by decnet_dns_register and decnet_loc_register. After set- ting up one or more directory services along with search path infor- mation during DECnet-Plus configuration, the system administrator uses decnet_register to transfer information between namespaces and to man- ually register, de-register, and modify node registration information. Both command line and forms interfaces are provided as well as online help information. The Local namespace stores name and addressing information on each node that is configured appropriately. The service can support up to 100,000 names and does not require or use DECdns. The DECdns distributed service maintains a consistent, networkwide di- rectory of network resources, called the namespace. You can construct the network resources without including location information, thereby permitting users to reference the network resources independent of their physical locations. A single DECdns server system can provide a networkwide name service. You can install DECdns servers on additional systems in a network to provide availability and performance benefits. As a general rule, you should place DECdns servers on two systems in each LAN. This config- uration provides adequate service and redundancy for most networks. Note: The DECdns server provided with DECnet-Plus for DIGITAL UNIX op- erates with other integrated DECdns implementations for DECnet (UL- TRIX and OpenVMS VAX). However, there is no support for interoperabil- ity with any DECdns Version 1.0 or Version 1.1 server, which is an ob- solete standalone product. Be aware that DIGITAL will not solve prob- lems related to the presence of DECdns Version 1.0 or Version 1.1 servers in the same namespace as the DECnet-Plus DECdns server. 9 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 DECdts-DIGITAL Distributed Time Service DECdts is a software-based service that provides precise, fault-tolerant clock synchronization for systems in LANs and WANs. The DECdts ser- vice also enables the coordination of other distributed computing ap- plications. Distributed applications use the time service to deter- mine event sequencing, duration, and scheduling. The following is a summary of DECdts features for networks running dis- tributed applications: o DECdts provides an NCL management interface for controlling and mon- itoring the software. o DECdts provides C Coordinated Universal Time (UTC) support, mea- suring and supplying time using this internationally recognized time standard. o DECdts supports a callable interface for applications to obtain UTC. Network Virtual Terminal DECnet-Plus software supports CTERM, the DIGITAL defined protocol for terminal access. CTERM is the DNA protocol that allows remote login between DECnet systems. CTERM supports users on DECnet conformant im- plementations. DECnet-Plus also supports the OSI Virtual Terminal (VT) application. VT allows you to connect to open systems, and open systems to connect to your system, using the OSI protocols for terminal access. VT pro- vides remote login capabilities between OSI systems and DECnet-Plus systems. For detailed information about VT, see Appendix A. 10 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 Remote File Transfer DECnet-Plus software supports DAP (Data Access Protocol) for remote file transfers. DECnet-Plus software provides the dcp utility for net- work file transfers using the DAP protocol. The commands supported are: dcp (copy), dls (list or directory), drm (remove), and dcat (concate- nate and display). The commands operate with files on any other DEC- net conformant systems. Using the OSI protocols, FTAM software performs the communications for the following file operations between open systems: o Copying files o Appending, deleting, or renaming files o Displaying information about files For detailed information about FTAM, see Appendix B. Network File Access Remote file access from other DIGITAL systems is supported. User pro- grams on other DECnet conformant systems can perform directory oper- ations as well as sequentially read, write, create, delete, and print files on a DECnet conformant system. Network file access is also sup- ported from OSI-conformant remote systems using the FTAM protocols. Mail The DECnet-Plus software allows users to send and receive mail to and from users on other DECnet conformant systems. The DECnet-Plus Mail utility extends the existing DIGITAL UNIX operating system mail sys- tem to include support for DECnet-Plus software. Both the DECnet-Plus mail utility and the current DIGITAL UNIX mail systems share the same user interface. 11 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 Task-to-Task Communications Task-to-task communications let DECnet-Plus applications communicate with remote DECnet conforming applications through a programming li- brary interface. XTI (X/Open Transport Interface) supports ISO transport protocol classes 0, 2, and 4, in addition to TCP/IP and User Datagram Protocol (UDP). This support allows software developers and applications to use mul- tiple network transport protocols through a single interface. The XTI programming interface now supports writing applications to run over Internet RFC 1006, thereby allowing OSI applications to run over TCP/IP. DECnet-Internet Gateway The DECnet-Internet Gateway, based on the 4.3 BSD TCP/IP, provides bidi- rectional network access between DECnet systems and Internet systems. It allows DECnet and Internet system users to communicate and coop- erate through their respective file transfer, remote login, and mail capabilities. An Internet system user can use the FTP, Telnet, and SMTP protocols to communicate with a DECnet system user who uses the DAP, CTERM, Mail-11 protocols, and vice versa. The DECnet-Internet Gate- way does not require special software on systems that use its service, nor does it require accounts for remote users on the gateway system. Standards Conformance DECnet-Plus software has been designed and implemented to comply with the following standards: o ISO - 4335: High Level Data Link Control Procedures - 7809: High Level Data Link Control Elements of Procedures - 8073: Connection-Oriented Transport Protocol - 8327: Connection-Oriented Session Protocol - 8348: Network Service Definition 12 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 - 8473: Protocol for Providing Connectionless-mode Network Ser- vice - 8571: File Transfer, Access, and Management - 8602: Connectionless Transport Service - 8650: Association Control Service Element - 8802-2: Logical Link Control Type 1 - 8802-3: CSMA/CD - 8802-5: Token Ring Access Method - 8823: Connection-Oriented Presentation Protocol - 8878: Use of X.25 to Provide the OSI Connection-mode Network Ser- vice - 8881: Use of X.25 Packet Level Protocol in Local Area Networks - 9041: Virtual Terminal - 9314: FDDI Token Ring Media Access Control - 9542: End System to Intermediate System Routing Protocol o EN - EN/ENV 41 204 FTAM: Simple File Transfer (unstructured) - EN/ENV 41 205 FTAM: File Management - EN/ENV 41 206 FTAM: Position File Transfer (flat) - EN/ENV 41 207 FTAM: Positional File Transfer (flat) o UK GOSIP Version 4.0 o NIST OIW Stable Implementor's Agreements, Version 5, Edition 1 o Internet Standards RFC 1006 and RFC 1859. 13 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 INSTALLATION DECnet-Plus software is customer installable. However, installation services are available for those customers who desire installation of this software by an experienced DIGITAL software specialist. DECnet-Plus Configuration and Performance Configuring a DECnet-Plus system to satisfy a user's application re- quirements involves making trade-offs of cost, performance, and func- tionality. The performance of a given DECnet-Plus system depends not only on the expected network traffic and resultant processing but also on the amount of concurrent local processing at that system. When you configure a DECnet-Plus system, you should consider the following fac- tors: o CPU type o Message size and frequency of transmission by all network appli- cations o Local applications HARDWARE REQUIREMENTS Processors Supported DECnet-Plus is supported on all valid DIGITAL UNIX Alpha configura- tions. For additional hardware information, refer to the configura- tion charts listed in the DIGITAL UNIX operating system Software Prod- uct Description (SPD 41.61.xx). DECnet-Plus for DIGITAL UNIX (DECnet-Plus) supports the Ethernet, FDDI, and 802.5/Token Ring controllers listed in the DIGITAL UNIX operat- ing system Software Product Description (SPD 41.61.xx). At least one controller is required on a DECnet-Plus system. For a list of valid configurations using serial synchronous communications interfaces, re- fer to the Software Product Description for Wide Area Networking Sup- port for DIGITAL UNIX (SPD 42.47.xx). 14 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 For general device or controller descriptions, consult your local hard- ware support provider. Memory Requirements A typical DECnet-Plus system uses an additional 2 MB of memory. For further memory configuration guidelines, consult the DIGITAL UNIX op- erating system Software Product Description (SPD 41.61.xx). Disk Space Requirements The entire installation kit requires approximately 65 MB of total disk space, including: o 20 KB maximum required in the / (root file system) for all subsets o 50 MB in /usr for subsets o 5 MB in /var for database files Disk Space Requirements for the Full-Capability DECnet-Plus Instal- lation The minimum full-capability DECnet-Plus installation requires approx- imately 34 MB of total disk space including: o 20 KB in the / (root file system) for all subsets o 20 MB in /usr for subsets o 4 MB in /var for data files Note also that if you load a large number of nodes in the local node database, the disk space requirements for /var increase. Disk Space Requirements for a DECnet For Small Configurations (DNALITE) Installation The DNALITE installation requires approximately 13 MB of total disk space including: o 11 MB in /usr for the required subsets 15 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 o 2 MB in /var for data files Note that the requirements and limitations for a DNALITE installation also reflect many of the requirements and limitations for a DIGITAL UNIX installation for small configurations. If you load a large num- ber of nodes in the local node database, the disk space requirements for /var increase. SOFTWARE REQUIREMENTS DIGITAL UNIX operating system Version 4.0. OPTIONAL SOFTWARE Wide Area Networking Support for DIGITAL UNIX (X.25). Consult the Soft- ware Product Description (SPD 42.47.xx) for product information. GROWTH CONSIDERATIONS The minimum hardware and software requirements for any future version of this product may be different from the requirements of the current version. DISTRIBUTION MEDIA Media and documentation for this product are available on the DIGI- TAL CD-ROM Software Library. You can order hardcopy documentation sep- arately. ORDERING INFORMATION The DECnet-Plus for DIGITAL UNIX software and documentation are shipped as part of the DIGITAL UNIX Layered Products CD-ROM. The current order numbers are as follows, where an asterisk (*) de- notes variant fields: 16 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 Software Li- QL-MTJA*-AA (End System), censes: QL-MTKA*-AA (Extended Function) Software Media: QA-054AA-H8 Software Documen- QA-MTJAA-GZ tation: Software Product QT-MTJ**-**, Services: QT-MTK**-** For additional information on available licenses, services, and me- dia, refer to the appropriate DIGITAL price book. SOFTWARE LICENSING The DECnet-Plus license gives users the right to use the software on a single system and includes the delivery of a License Product Autho- rization Key (PAK) to enable the DECnet-Plus for DIGITAL UNIX soft- ware. The DECnet-Plus end system license provides the right to use all DECnet- Plus features (except OSI application gateways and the DECdns server), DECnet-Plus over HDLC point-to-point devices, and DECnet-Plus over X.25 using the LLC2 protocol. The DECnet-Plus extended function license provides the right to use all the DECnet-Plus components of the end system license as well as OSI application gateways and the DECdns server. To obtain a license for direct connections to a PSDN using the X.25 and LAPB protocols, refer to the product information listed in the Optional Software section. This software is furnished only under a license. For more information about DIGITAL's licensing terms and policies, contact your local DIG- ITAL office. 17 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 License Management Facility Support This software supports the DIGITAL UNIX operating system License Man- agement Facility. For more information on the License Management Facility, refer to the DIGITAL UNIX operating system Software Product Description (SPD 41.61.xx) or documentation set. SOFTWARE PRODUCT SERVICES A variety of service options are available from DIGITAL. For more in- formation, contact your local DIGITAL office. SOFTWARE WARRANTY Warranty for this software is provided by DIGITAL with the purchase of a license for the software as defined in the Software Warranty Ad- dendum to this Software Product Description. 18 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 APPENDIX A-Virtual Terminal (VT) DECnet-Plus Virtual Terminal (VT) is Digital Equipment Corporation's implementation of the ISO Virtual Terminal Basic Class standard, which consists of the service definition (ISO 9040) and the protocol (ISO 9041). The VT software adheres to these standards, thereby providing interactive access between DECnet-Plus systems and other multivendor terminal systems and host systems that also adhere to the ISO Virtual Terminal Basic Class standard. VT is implemented as an application service element (ASE) of the OSI Application layer. VT can run over Transport layer class 0, 2, or 4 over CONS, and TP4 over CLNS. VT can also run over TCP/IP networks using RFC 1006. VT provides terminal/initiator (for a local user) and host/responder (for the remote user) capabilities. Terminal/responder and host/initiator are not supported. Supported Standards VT conforms to the following OSI standards: o ISO 9041: Virtual Terminal protocol-basic class o ISO 8650: ACSE protocol o ISO 8823: Presentation protocol o ISO 8327: Session protocol VT Features VT supports the following features: o Class of Service - Basic class (character cell terminals) o Mode of Operation - Asynchronous mode (A-Mode) 19 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 o Profile Support - Default A-mode (adheres to ISO 9040) - A-mode Generalized Telnet (adheres to OIW Stable Agreements) - A-mode Transparent (adheres to OIW Stable Agreements) - A-mode Telnet 1988 (adheres to OIW Stable Agreements) o Functional Units - destructiveBreak - structuredCOs - urgentData o Supported Gateways - Bidirectional VT/Telnet - Bidirectional VT/CTERM - LAT to VT o Online Help X.500 Address Lookup The VT software is capable of retrieving network addresses from the X.500 Directory. This functionality can be used in conjunction with or instead of retrieving addresses from a local repository. For de- tailed information, see the X.500 product documentation. Command Mode Command Mode allows the user to execute commands that can modify the characteristics of the VT association with the remote application. 20 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 Trace Utility The Virtual Terminal tracing utility (ositrace) is a tool for iden- tifying problems in protocol exchanges between your local system and any remote system. The utility captures protocol exchanges and tran- scribes them into easily read text. The tracing utility monitors data exchanges for individual associa- tions. The utility can trace data originating from the VT, ACSE, pre- sentation, and session components. 21 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 APPENDIX B-File Transfer, Access, and Management File Transfer, Access, and Management (FTAM) software provides com- munications for performing the following file operations between open systems: o Copying files between local and remote systems o Appending, deleting, or renaming files o Displaying information about files An open system is a computer system that implements the standards for each of the seven layers of the Open Systems Interconnection (OSI) Ref- erence Model for communications as defined by the International Or- ganization for Standardization. An FTAM system is any open system con- taining an FTAM implementation that conforms to the FTAM standard and includes the implementations of the necessary underlying OSI services. FTAM implements several standards that define the following components of these layers of the OSI basic reference model: the FTAM service el- ement and the Association Control Service Element (ACSE) of the Ap- plication layer, the Presentation layer, and the Session layer. Supported Standards FTAM conforms to the following OSI standards: o ISO 8571: File Transfer, Access, and Management service and pro- tocol o ISO 8650: ACSE protocol o ISO 8823: Presentation protocol o ISO 8327: Session protocol The following table compares the supported implementation profiles for different standards bodies and their relationship to each other. 22 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 ___________________________________________________________________ International Standardized Profiles (ISP) ISO_10607_________NIST________CEN/CENELEC_and_EWOS_________________ Part 1: Spec- - - ification of ACSE, pre- sentation and session proto- cols for use by FTAM Part 2: Def- - - inition of document types, con- straint sets, and syntaxes Part 3: AFT11 T1 - A/111 - - Simple Simple ENV 41 204 File Trans- File fer Service Transfer (Unstructured) Part 4: AFT12 T2 - Po- A/112 - (DISP)[1] - sitional ENV 41 206 Positional File File Trans- Transfer fer Service (Flat)[2] Part 5: AFT3 M1 - A/13 - (DISP)[1] - Manage- ENV 41 205 File Manage- ment ment Service ___________________________________________________________________ [1]Draft ISP [2]AFT12_is_not_supported_by_DECnet-Plus___________________________ 23 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 FTAM Component Software The component software includes the user facilities (initiators), re- sponders, management tools, and problem-determination tools. FTAM User Facilities You access the FTAM user facilities by entering DIGITAL UNIX operat- ing system commands. These commands are ocat (concatenate and display), ocp (copy), ols (list or directory), omv (move or rename), and orm (re- move). The commands operate on files stored on any FTAM system whose implementations are compatible with FTAM. You cannot use these com- mands to directly manipulate files on your local system. Support for any File Naming Convention A file designation is system-specific information that identifies a file to its storage system. FTAM software lets users specify files us- ing the naming conventions of the systems where the files reside. FTAM supports the standard POSIX (DIGITAL UNIX operating system) format for file specifications and a comparable style of file-specification for- mat. 24 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 Support for Several File Types FTAM software can access and transfer files containing both binary and ASCII data. FTAM-1, FTAM-2, FTAM-3, and NBS-9 document types are sup- ported. FTAM-1 files are unstructured text files, FTAM-2 files are sequential text files, and FTAM-3 files are unstructured binary files. The FTAM- 1, FTAM-2, and FTAM-3 document types support the following parameters: ___________________________________________________________________ String Document Signifi- Universal Type______cance_______Class_______Maximum_String_Length____________ FTAM-1 Not sig- IA5String Presence and absence of parame- nificant ter GeneralString Fixed VisibleStrinPresence of parameter GraphicString Variable VisibleStrinPresence and absence of parame- ter GraphicString FTAM-2 Not sig- VisibleStrinPresence or absence of parameter nificant GraphicString FTAM-3 Not sig- Presence or absence of parameter nificant __________Fixed___________________Presence_of_parameter____________ NBS-9 files are NBS file directories. Flexible and Transparent Access for Local Files FTAM software treats local files the same way that the DIGITAL UNIX operating system file system treats them. 25 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 File Transfers The FTAM ocp command transfers files between compatible FTAM systems without modifying the source file. The facility can transfer files in either direction between the local system and a remote FTAM system. The ocp command can also transfer files between two remote FTAM sys- tems for a local FTAM user. The ocp command also allows you to append one or more files to a sin- gle output file within or between FTAM systems. FTAM-FTP Gateway The FTAM-FTP Gateway lets you perform file operations between OSI and Internet Systems. Remote users of the gateway need not establish ac- counts on the gateway system to use its capabilities. File Deletion The FTAM orm command deletes one or more files on any combination of FTAM systems provided that the user has delete access to those files on the specific FTAM system. Renaming Requests The FTAM omv command allows you to rename files. The command works on files stored on remote FTAM systems (remote files). The command en- ables you to change the path name or file name of an existing file. For remote files, you must specify the type of information the remote FTAM system requires for specifying files. Directory Requests The FTAM ols command displays the complete set of FTAM file attributes. Specific options allow users to vary the display of attributes that are meaningful in a DIGITAL UNIX operating system environment: for ex- ample, date and time of the last modification to the file name. 26 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 FTAM File Error Recovery FTAM provides file error recovery functionality both in the ocp ini- tiator command and in the FTAM responder. File error recovery is pro- vided for classes 1, 2, and 3 errors as detailed in ISO 8571-4. Class 1 file error recovery provides only the restart functionality, while classes 2 and 3 file error recovery provide both the restart and recovery functionality as follows: o If an internal error is detected in the data transfer regime, class 1 recovery restarts the data transfer regime by retransmitting the file data beginning at the negotiated checkpoint within the data transfer regime. o Class 2 error recovery provides for re-establishment of the select and open regimes, and also allows for retransmission of file data beginning at a negotiated checkpoint within the data transfer regime. o Class 3 error recovery provides full recovery by re-establishing a lost FTAM association and its select and open regimes. Class 3 recovery then restarts the data transfer regime by retransmitting the file data beginning at the negotiated checkpoint within the data transfer regime. All restart and recovery operations and procedures are completely trans- parent to the user. Management and Problem Determination Tools FTAM software supplies a number of management tools, including an in- stallation verification procedure (IVP), a tracing utility, event log- ging, and informational and error messages. FTAM Installation Verification Procedure (IVP) The FTAM IVP sets up outbound and inbound application associations. A connection is made to your local system (as a loopback test). The FTAM IVP checks that your installation is able to set up and release presentation and session connections. It tests the FTAM software by starting a responder and reading the attributes of a file with the ols command. 27 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 FTAM Tracing Utility The FTAM tracing utility (ositrace) is a tool for identifying prob- lems in protocol exchanges between your local system and any remote FTAM system. The tracing utility captures protocol exchanges and tran- scribes them into easily read text. The FTAM tracing utility monitors data exchanges for individual as- sociations. The tracing utility can trace data originating from the following components: FTAM (data, protocol, and structuring), the As- sociation Control Service Entity (ACSE), presentation, and session. FTAM Event Logging For event logging, the FTAM listener writes records in the syslog file (/usr/spool/mqueue/syslog) and the responder writes records to the wtmp file (/usr/adm/wtmp). Requirements for Compatibility with FTAM FTAM lets an open system perform a specific set of file transfer, ac- cess, and management activities with any open system having a compat- ible FTAM implementation. The Protocol Implementation Conformance Statement (PICS) provides more information about DIGITAL's FTAM implementation. 28 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 APPENDIX C-OSI Application Programming Interfaces (APIs) FTAM API The FTAM API supports the OSI standard ISO 8571: Information Process- ing Systems, Open Systems Interconnection, and File Transfer, Access, and Management. The FTAM API provides the interface to the FTAM protocol machine pro- vided in DECnet-Plus. Communications between the application code and the FTAM protocol machine are carried out using ASN.1 encoded data struc- tures. The FTAM API supports the following functions: Abort Begin-Group Cancel Change-Attributes Create Close Data Data-End Delete Deselect End-Group Initialize Open Read-Attributes Read Select Terminate Transfer-End Write OSI Applications Kernel (OSAK) API The OSAK API provides a direct interface to services at ACSE and Pre- sentation layer services. 29 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 The OSAK API supports the following OSI standards for the ACSE layer: o ISO 8650: Information Processing Systems, Open Systems Intercon- nection, and Protocol Specification for the Association Control Ser- vice Element o ISO 8649: Information Processing Systems, Open Systems Intercon- nection, and Service Definition for the Association Control Ser- vice Element The OSAK API provides the interface to the ACSE associate and release services. The following services are provided: Associate Release Abort Redirect The redirect service is not an ACSE service. It allows applications to redirect an incoming association to another process on the local system. The OSAK API also includes support for the OSI Presentation layer with support for the following OSI standards: o ISO 8823: Information Processing Systems, Open Systems Intercon- nection, and Connection-Oriented Presentation Protocol Specifica- tion o ISO 8822: Information Processing Systems, Open Systems Intercon- nection, and Connection-Oriented Presentation Service Definition o ISO 8327: Information Processing Systems, Open Systems Intercon- nection, and Basic Connection-Oriented Session Protocol Specifi- cation o ISO 8326: Information Processing Systems, Open Systems Intercon- nection, and Basic Connection-Oriented Session Service Definition The Presentation layer services supported by the OSAK API are: Alter-Context 30 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 Data Capability-Data Expedited-Data Typed-Data Token-Please Token-Give Control-Give Sync-Major Sync-Minor Resynchronize Exception-Report Activity-Start Activity-Interrupt Activity-Resume Activity-Discard Activity-End Abort The OSAK API also supports (by pass through) the OSI Session layer ser- vices. Session Layer API The Session layer API, called the OSAK Session Programming Interface (SPI), supports the following OSI standards: o ISO 8327: Information Processing Systems, Open Systems Intercon- nection, Basic Connection-Oriented Session Protocol Specification o ISO 8326: Information Processing Systems, Open Systems Intercon- nection, Basic Connection-Oriented Session Service Definition The Session layer supports ISO Session Versions 1 and 2. Version 1 al- lows up to 512 octets of user data on a service. Version 2 supports the restrictions imposed by the National Institute of Standards and Technology, allowing up to 10,240 octets of data on a service. 31 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 The OSAK SPI provides the interface to the following connect and re- lease services: o Connect o Release o Abort o Redirect The redirect service is not a session service. It allows applications to redirect an incoming connected to another process on the local sys- tem. The Session layer services supported by the OSAK API are: Data Capability-Data Expedited-Data Typed-Data Token-Please Token-Give Control-Give Sync-Major Sync-Minor Resynchronize Exception-Report Activity-Start Activity-Interrupt Activity-Resume Activity-Discard Activity-End 32 DECnet-Plus for DIGITAL UNIX Version 4.0 SPD 41.92.09 ROSE API The Remote Operations Service Element (ROSE) supports the OSI stan- dard ISO 9072: Information Processing Systems, Text Communication, and Remote Operations. ROSE supports interactive applications in a distributed open systems environment. It is a service for multivendor distributed processing. The ROSE functionality provides a mechanism that allows for encoding and decoding the remote operations protocol control information, as defined in ISO 9072, for the following services: Invoke Result Error Reject © 1996 Digital Equipment Corporation. All rights reserved. [R] UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. [R] OSI is a registered trademark of CA Management, Inc. [R] POSIX is a registered trademark of IEEE. [TM] The DIGITAL logo, DEC, DECnet, DIGITAL, DNA, OpenVMS, ULTRIX, and VAX are trademarks of Digital Equipment Corporation. 33