DIGITAL Software Product Description ___________________________________________________________________ PRODUCT NAME: DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 DESCRIPTION DECnet-Plus for DIGITAL UNIX (DECnet-Plus) software is an implemen- tation of the DIGITAL Network Architecture (DNA) for the DIGITAL UNIX Operating System. This software supports DNA Phase V, the integration of DECnet, OSI, and TCP/IP protocols. This allows the different net- work protocol stacks to be available to upper layers as discrete trans- port services. Upper layers have been implemented as separate "tow- ers", enabling existing DECnet and OSI applications to share the in- tegrated Transport Layer. DECnet-Plus software offers the following features: 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 o network-wide resource sharing and management as defined by the DNA protocols o a graphical user interface to the network management facility known as Network Control Language o expanded naming options, allowing the use of a large local names- pace, DECdns, and/or DNS/BIND as naming services 10-September-1997 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 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. Existing programs run- ning over TCP/IP can be modified to run over DECnet-Plus software. Mod- ifying DECnet programs to run directly over TCP/IP can be done, but only if they do not make use of operations that are specific to DEC- net. Similarly, both OSI and DECnet applications or user-written soft- ware using the X/Open Transport Interface (XTI) can operate over a TCP/IP backbone network using RFC 1006. Depending on the network configuration, networks combining DECnet-Plus systems with other DECnet software may limit certain functions if all products do not support equal features. Compare Software Product De- scriptions to determine function availability. DECnet-Plus is available in two forms: End System and Extended Func- tion. See SOFTWARE LICENSING for details of each license form. DECnet-Plus software supports the features described below. 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 V2.0 packet formats on CSMA/CD devices. For FDDI devices, ISO 9314 FDDI Token Ring Media Access Control is supported. 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 to be interconnected to other lo- cal 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 2 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 DECnet-Plus license and installed from the X.25 for DIGITAL UNIX Sys- tems software. Please refer to the Software Product Description (SPD 42.47.xx) for a list of supported devices. 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 CLNP header support, DECnet-Plus software supports the inactive subset (null internet) spec- ified 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 datalink. The OSI Ping function enables a network entity to generate a message that is echoed back to the sender when received by its tar- get 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. 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), any router conforming to the DIGITAL Network Architecture can be used. The net- work layer is able to cache information about the paths that are used to reach remote nodes. Segregated Routing Mode is a settable attribute. It will direct rout- ing to choose a DNA Phase IV router for those packets having a des- tination address that can be translated to the Phase IV format. All other packets will be sent to a DNA Phase V 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 increases network reliability and data throughput. 3 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 Multihomed end systems allow a system to have up to three unique ad- dresses. This allows an end system to have both a DECnet Phase IV com- patible address and a DECnet-Plus extended address. The network layer supports ISO 8878 Use of X.25 to Provide the OSI Connection- mode Network Service (CONS). OSI Transport classes 0, 2, and 4 can be configured 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 subnets. This function- ality is included as part of the DECnet-Plus license and installed from the X.25 for DIGITAL UNIX Systems software. The DECnet-Plus software can be used to provide LLC2 services, ISO 8881 Use of X.25 Packet Level Protocol in Local Area Networks. This pro- vides connection-oriented network services over a LAN to another suit- ably configured X.25 end system on the LAN. It also allows X.25 log- ical connections to be made through a relay system using LLC2. This LLC2 functionality is included as part of the DECnet-Plus license and installed from the X.25 for DIGITAL UNIX Systems software. An X.25 for DIGITAL UNIX Systems software license is required when di- rectly connecting a system to a Packet Switch Data Network (PSDN) us- ing the X.25 and Link Access Procedure B (LAPB) protocols. For more information, please refer to the 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 three classes: Class 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 DECnet transport protocol supported is the Network Services Pro- tocol (NSP). NSP offers communications between DECnet systems and pro- vides backward compatibility with DNA Phase IV systems. 4 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 DECnet and OSI Applications over TCP/IP The DECnet-Plus software supports OSI applications over TCP/IP (In- ternet RFC1006). Internet RFC1006 defines a specification for running OSI applications over TCP/IP. Operation of FTAM and Virtual Terminal over a TCP/IP network is supported. Implementation of the RFC1006 Extensions (Internet Draft) allows DEC- net applications to run over TCP/IP. The supported applications in- clude all licensed DECnet applications as well as layered products and user-written applications that conform to the documented DECnet pro- gramming interfaces. DECnet-Plus for OpenVMS (V6.0 and later) also pro- vides this functionality, enabling interoperation of OpenVMS and DIG- ITAL UNIX DECnet applications over a TCP/IP backbone. OSI Upper Layers DECnet-Plus software supports session, presentation, and the appli- cation layer. The application layer provides Association Control Ser- vice Elements (ACSE); File Transfer, Access and Management (FTAM); and Virtual Terminal (VT). 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 RFC1006. OSI Application Programming Interfaces The OSI Application Programming Interfaces enable users to write dis- tributed applications that communicate over open networks and use the OSI services provided by DECnet-Plus. The Interfaces are provided under the Extended Function License and include: o an interface to FTAM (File Transfer, Access and Management) o interfaces to the ACSE (Association Control Service Element) and Presentation layers 5 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 o an interface to ROSE (Remote Operations Service Element) and permits the application writers to use the services of the OSI up- per layers in their applications. The APIs allow for the development of applications on DECnet-Plus sys- tems. Source code must be compiled and linked with the APIs. The APIs are required on the development system and the compile/link system. The resulting application can be run on any DECnet-Plus system with the appropriate Operating System. The APIs are not required on these target systems. For more information, see OSI APIs appendix. Network Management The DECnet-Plus network management software allows: o System or network managers to control and monitor the operation of a network o Configuration of network operating parameters o Modification and display of directory service name templates and search paths o Startup and shutdown of network components as needed o Network monitoring, related to network traffic and performance o Detection, isolation, and repair of network problems In addition, network management can provide information warning net- work managers of faulty or failing network components, both hardware and software. NCL, Network Command Language, is provided as a utility to the net- work manager to perform the operations described above. NCL can be ac- cessed through either a command line interface or a Graphical User In- terface (GUI). The GUI allows network managers to view the status of network components and control those components from a Motif-based win- dow interface. 6 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 NCL can also be used to test specific components of the network. NCL enables transmission and reception of test messages either between sys- tems or through controller loopback arrangements. The messages can then be compared for possible errors. NCL aids in isolating network prob- lems. DECnet-Plus software provides network event logging to a terminal de- vice, disk file, or remote system. NCL can be used to enable and dis- able the event logging facility as well as to optionally filter spe- cific events. Problem solving is facilitated by the provision of the Common Trace Facility (CTF). CTF enables the user to trace and analyze frames pass- ing between the network and the DECnet-Plus system through the inter- faces and protocols of the DECnet and OSI stacks. NSP, OSI Transport, Routing, and RFC1006 can be traced. Additionally DECnet-Plus software supports installation, management, and down loading via IEEE802.3/Ethernet and FDDI using the MOP pro- tocol to DIGITAL servers, routers, portals, and gateways. Please re- fer to the specific product's Software Product Description to deter- mine if it supports DECnet-Plus software. MOP (Maintenance Operations Protocol) is a management protocol used for low-level communications with a system which either is not fully operational or is being tested. MOP can be configured and run stan- dalone without installing all of DECnet-Plus. A DECnet-Plus license is not required for such operation of MOP. Directory Services DECnet-Plus provides simple access to the node name and addressing in- formation stored in one or more directory services. Three directory service options are supported: o Local - Stores names and address information locally in database files o DECdns - Stores names and address information in DIGITAL's Distributed Name Service, a global directory service (both clerk and server con- figurations are supported) 7 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 o Domain/BIND - Retrieves TCP/IP naming and addressing information from a DNS/BIND name server DECdns is no longer a requirement for DECnet-Plus. When configuring a node, the system administrator can elect to use a Local Directory Service, DECdns, or DNS/BIND. DECnet-Plus provides access to the Lo- cal Directory Service or to a DECdns server running on an OpenVMS VAX, DIGITAL UNIX, or ULTRIX system. 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 and search path information dur- ing DECnet-Plus configuration, decnet_register is used by the system administrator to transfer information between namespaces, manually reg- ister, de-register, and modify node registration information. Both com- mand line and forms interfaces, as well as online help information, are provided. The Local file stores name and addressing information in separate database files, one file on each node that is configured to use a Local names- pace. It can support up to 100,000 names and does not require or use DECdns. This functionality replaces the Local Naming Option (LNO) that was limited to 150 names. Existing LNO entries can be converted into a Local namespace file using the decnet_register_lno tool provided. The full DECdns service maintains a consistent, network-wide direc- tory of network resources, called the namespace. Resources may be con- structed without including location information, thus permitting users to reference these network resources independent of their physical lo- cation. A single DECdns server system can provide a network-wide name service. DECdns servers can be installed on additional systems in a network to provide availability and performance benefits. As a general rule DECdns servers should be placed on two systems in each LAN. This should pro- vide adequate service and redundancy for most networks. 8 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 The following is a summary of features available with the DIGITAL Dis- tributed Name Service (DECdns) provided by DECnet-Plus for DIGITAL UNIX: o DECdns provides a networkwide, name-to-attribute mapping service which allows selected DIGITAL applications to create, read, mod- ify, and delete names in the namespace; o DECdns stores and manages a large number of names using a hierar- chical structure; o Overall availability and performance of the name service can be en- hanced by installing DECdns servers on multiple systems. DECdns au- tomatically maintains consistency of the namespace. o DECdns provides access control to each name in the namespace. This set of access control rights consists of read, write, delete, test, and control. o Network event logging using the standard DECnet-Plus for DIGITAL UNIX facility is provided. NCL can be used to enable and disable DECdns events. Note: The DECdns server provided with DECnet-Plus for DIGITAL UNIX will interoperate with other integrated DECnet-Plus DECdns implementations (ULTRIX and OpenVMS VAX). However, there is no support for interop- erability with any DECdns V1.0 or V1.1 server (obsolete standalone prod- uct offering). Problems related to the presence of DECdns V1.0 or V1.1 servers in the same namespace as the DECnet-Plus DECdns server will not be supported. DECdts - DIGITAL Distributed Time Service DECdts is a software-based service that provides precise, fault-tolerant clock synchronization for systems in LANs and WANs. DECdts also en- ables the coordination of other distributed computing applications. Distributed applications use the time service to determine event se- quencing, duration, and scheduling. 9 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 The following is a summary of DECdts features for networks running dis- tributed applications: o DECdts provides a NCL management interface for controlling and mon- itoring the software; o DECdts provides coordinated Universal Time (UTC) support, measur- ing 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 which allows remote login between DECnet systems. CTERM supports users on DECnet conformant im- plementations. The OSI application, Virtual Terminal, allows you to connect to open systems, and other open systems to connect to yours, using the OSI pro- tocols for terminal access. Virtual Terminal provides remote login ca- pabilities between OSI systems and DECnet-Plus systems. For more information, see Virtual Terminal appendix. Remote File Transfer DECnet-Plus software supports DAP (Data Access Protocol) for remote file transfers. DECnet-Plus software provides the "dcp" utility for network file transfers using the DAP protocol. The commands supported are: dcp (copy), dls (list or directory), drm (remove), and dcat (con- catenate and display). They operate on files on any other DECnet con- formant systems. FTAM software performs the communications for file operations between open systems, using the OSI protocols. These operation are: o Copying files between open systems o Appending, deleting, or renaming files on open systems 10 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 o Displaying information about files on open systems For more information, see File Transfer, Access and Management appendix. 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. 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 (Mail-11) extends the existing DIGITAL UNIX Operating System mail system to include support for DECnet-Plus software. Both the DECnet- Plus mail utility and the current DIGITAL UNIX Operating System mail systems share the same user interface. 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 Class 0, 2, and 4, in addition to TCP/IP and UDP. This allows software de- velopers and applications to use multiple network transport protocols through a single interface. The XTI programming interface has been en- hanced to support writing applications to run over Internet RFC1006, 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, 11 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 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. 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 the amount of concurrent local processing at that system. When con- figuring a DECnet-Plus system, the following factors should be con- sidered: o CPU type o Message size and frequency of transmission by all network appli- cations o ``Local'' applications Standards Conformance DECnet-Plus software has been designed and implemented to be confor- mant to 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 - 8473: Protocol for Providing Connectionless-mode Network Ser- vice - 8571: File Transfer, Access and Management - 8602: Connectionless Transport Service 12 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 - 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 US GOSIP Version 2.0 o UK GOSIP Version 4.0 o NIST OIW Stable Implementor's Agreements, Version 5, edition 1 Since certification and registration of this software must take place after the software ships, contact your local DIGITAL office for the most recent conformance certificates. 13 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 INSTALLATION If, during DIGITAL UNIX Operating System installation, the X/Open Trans- port Interface option is selected as a desired kernel option, DECnet- Plus for DIGITAL UNIX can load its kernel modules dynamically. No re- build of the kernel and reboot will be necessary. 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. HARDWARE REQUIREMENTS Processors Supported DECnet-Plus is supported on all valid DIGITAL UNIX Alpha configura- tions. Refer to the configuration charts listed in the DIGITAL UNIX Operating System Software Product Description (SPD 41.61.xx) for ad- ditional information. 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, please refer to the Software Product Description for X.25 for DIGITAL UNIX Systems (SPD 42.47.xx). For general device or controller descriptions, please consult your lo- cal hardware support provider. Memory Requirements: A typical DECnet-Plus system will require a minimum of 2 MB of addi- tional memory. Consult the DIGITAL UNIX Operating System Software Prod- uct Description (SPD 41.61.xx) for further memory configuration guide- lines. Disk Space Requirements 14 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 Minimum Disk space required for installation/use: 10 MB in / (root) file system if kernel rebuild re- quired 20 MB in /usr 20 MB /var 81 MB total SOFTWARE REQUIREMENTS DIGITAL UNIX Operating System V3.2c or later OPTIONAL SOFTWARE X.25 V1.3 for DIGITAL UNIX Systems Note: The DECdns server provided with DECnet-Plus for DIGITAL UNIX will interoperate with other integrated DECnet-Plus DECdns implementations (ULTRIX and OpenVMS VAX). However, there is no support for interop- erability with any DECdns V1.0 or V1.1 server (obsolete standalone prod- uct offering). Problems related to the presence of DECdns V1.0 or V1.1 servers in the same namespace as the DECnet-Plus DECdns server will not be supported. 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 DIGITAL CD- ROM Software Library. Documentation in hardcopy format may be ordered separately. 15 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 ORDERING INFORMATION The DECnet-Plus for DIGITAL UNIX software and documentation are shipped as part of the DIGITAL UNIX Layered Products CD-ROM. 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**-** *Denotes variant fields. For additional information on available li- censes, services and media refer to the appropriate price book. The above information is valid at time of release. Please contact your lo- cal DIGITAL office for the most up-to-date information. SOFTWARE LICENSING The DECnet-Plus license gives the users the right to use the software on a single CPU and includes the delivery of a License Product Autho- rization Key (PAK) to enable the DECnet-Plus for DIGITAL UNIX soft- ware. The End System license grants the right to use all the DECnet-Plus fea- tures (except the DECdns Server and Application Gateways), DECnet-Plus over HDLC point-to-point devices, and DECnet-Plus over X.25 using the LLC2 protocol. The Extended Function license grants the right to use all the DECnet- Plus features of the End System license, the DECdns Server, OSI Ap- plication Programming Interfaces, FTAM/FTP gateway, and Virtual Ter- minal gateways (VT/TELNET, VT/CTERM, LAT to VT). To obtain a license for direct connections to a PSDN using the X.25 and LAPB protocols, refer to the OPTIONAL SOFTWARE section. 16 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 This software is furnished only under a license. For more information about DIGITAL's licensing terms and policies, contact your local DIG- ITAL office. 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 of this Software Product Description. [TM] The DIGITAL Logo, Alpha AXP, AXP, DEC, DECnet, DIGITAL, DNA, OpenVMS, ULTRIX, and VAX are trademarks of Digital Equipment Corporation. ©1995 Digital Equipment Corporation. All rights reserved. 17 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 Appendix A - Virtual Terminal DECnet-Plus Virtual Terminal is Digital Equipment Corporation's im- plementation of the ISO Virtual Terminal Basic Class standard, which is comprised of the service definition (ISO 9040) and the protocol (ISO 9041). The DECnet-Plus Virtual Terminal software adheres to these stan- dards, thereby providing interactive access between DECnet-Plus sys- tems and other multivendor terminal systems and host systems that also adhere to the ISO Virtual Terminal Basic Class standard. Virtual Terminal is implemented as an Application Service Element (ASE) of the OSI Application layer. DECnet-Plus Virtual Terminal can run over Transport Layer Classes 0, 2 or 4 over CONS, and TP4 over CLNS. DECnet-Plus Virtual Terminal can also run over TCP/IP networks using RFC1006. Virtual Terminal 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 Virtual Terminal 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 Virtual Terminal Features Virtual Terminal supports the following features: o Class of Service Basic class (character cell terminals) o Mode of Operation Asynchronous Mode (A-Mode) 18 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 o Profile Support Default A-mode (as per 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 Address Lookup OSI Application Address Lookup in X.500. The Virtual Terminal soft- ware is capable of retrieving network addresses from the X.500 direc- tory. This functionality may be used in conjunction with or instead of retrieving addresses from a local repository. Command Mode Command Mode allows the user to execute commands that can modify the characteristics of the Virtual Terminal association with the remote application. 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. 19 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 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. 20 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 Appendix B - File Transfer, Access and Management FTAM software provides communications for performing file operations between open systems. These operations are: o Copying files between local and remote systems o Appending, deleting, or renaming files on open systems o Displaying information about files on open systems 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 File Transfer, Access and Management (FTAM) service element and the Association Con- trol Service Element (ACSE) of the Application layer, the Presenta- tion 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 provides a comparison of the supported implemen- tation profiles for different standards bodies and their relationship to each other. 21 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 ___________________________________________________________________ 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) - Po- sitional ENV 41 206 sitional File File Transfer Ser- Transfer vice (Flat)[1] Part 5: AFT3 M1 - A/13 - (DISP) - File Manage- ENV 41 205 Management ment Service ___________________________________________________________________ [1]AFT12_is_not_supported_by_DECnet-Plus___________________________ DISP indicates a draft ISP. 22 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 FTAM Component Software The component software includes the user facilities (initiators), re- sponders, management tools, and problem determination tools. FTAM User Facilities The FTAM user facilities are accessed by DIGITAL UNIX Operating Sys- tem commands. These commands are ocat (concatenate and display), ocp (copy), ols (list or directory), omv (move or rename), and orm (re- move). They operate on files stored on any FTAM system whose imple- mentations are compatible with FTAM. These commands cannot be used for manipulating 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 UFS (DIGITAL UNIX Operating System) format for file specifications and a comparable style of file-specification for- mat that accommodates non-UFS file designations. 23 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 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 DIGITAL UNIX Op- erating System file system treats them. 24 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 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. This command also allows you to append one or more files to a single 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 do not have to estab- lish accounts on the gateway system to use its capabilities. File Deletion The FTAM orm command can delete 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 pathname or file name of an existing file. For remote files, you must specify whatever type of information the re- mote 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/time of last modification of file name. 25 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 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 Class 1, Class 2, and Class 3 type 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 the re-establishment of the se- lect and open regimes, and also allows for the retransmission of file data beginning at a negotiated checkpoint within the data trans- fer 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 will then restart the data transfer regime by retransmit- ting 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. 26 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 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. 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), 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. 27 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 Appendix C - OSI Application Programming Interfaces FTAM API The FTAM API supports the OSI standard ISO 8571-Information Process- ing Systems-Open Systems Interconnection-File Transfer, Access and Man- agement. 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 API supports the following functions o Abort o Begin-Group o Cancel o Change-Attributes o Create o Close o Data o Data-End o Delete o Deselect o End-Group o Initialize o Open o Read-Attributes o Read o Select o Terminate o Transfer-End 28 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 o Write ACSE The Association Control Service Entity (ACSE) API supports the OSI stan- dards o ISO 8650-Information Processing Systems-Open Systems Interconnection- Protocol Specification for the Association Control Service Element. o ISO 8649-Information Processing Systems-Open Systems Interconnection- Service Definition for the Association Control Service Element. The ACSE API provides the interface to the Associate and Release ser- vices. The services provided are o Associate o Release o Abort o Redirect The Redirect service is not an ACSE service. It allows applications to redirect an incoming association to another process on the local system. Presentation Layer API The implementation of the Presentation layer in the Toolkit supports the OSI standards o ISO 8823-Information Processing Systems-Open Systems Interconnection- Connection Oriented Presentation Protocol Specification o ISO 8822-Information Processing Systems-Open Systems Interconnection- Connection Oriented Presentation Service Definition o ISO 8327-Information Processing Systems-Open Systems Interconnection- Basic Connection Oriented Session Protocol Specification 29 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 o ISO 8326-Information Processing Systems-Open Systems Interconnection- Basic Connection Oriented Session Service Definition. The Presentation API provides the interface to the Presentation layer services and, by pass through, to the equivalent Session layer ser- vices. The API supports the following services o Alter-Context o Data o Capability-Data o Expedited-Data o Typed-Data o Token-Please o Token-Give o Control-Give o Sync-Major o Sync-Minor o Resynchronize o Exception-Report o Activity-Start o Activity-Interrupt o Activity-Resume o Activity-Discard o Activity-End o Abort 30 DECnet/OSI V3.2a for DIGITAL UNIX SPD 41.92.07 The Session layer supports ISO Session version 1 and version 2. Ses- sion version 1 allows up to 512 octets of user data on a service. Ses- sion version 2 supports the restrictions imposed by the National In- stitute of Standards and Technology allowing up to 10,240 octets of data on a service. ROSE API The Remote Operations Service Element (ROSE) supports the OSI stan- dard o ISO 9072 - Information Processing Systems - Text Communication - 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 which allows for the en- coding and decoding of the Remote Operations Protocol Control Infor- mation, as defined in ISO 9072, for the following services: o Invoke o Result o Error o Reject 31