      Software Product  Description   C ___________________________________________________________________   C PRODUCT NAME:  Compaq DECnet-Plus Version 7.3 for OpenVMS Alpha SPD  50.45.14   Description   C Compaq DECnet-Plus Version 7.3 for OpenVMS Alpha (formerly known as F DECnet/OSI) is an implementation of Phase V of the DIGITAL Network Ar-8 chitecture (DNA) for the OpenVMS Alpha operating system.E Compaq DECnet-Plus integrates DECnet and Open Systems Interconnection F (OSI) network protocols, allowing both stacks to share integrated net-D work functions up to the Transport layer. Upper layers have been im-E plemented as separate towers, allowing existing DECnet and OSI appli- F cations to share the integrated Transport layer. Existing DECnet PhaseD IV and new DECnet and OSI applications are supported by DECnet-Plus.D In combination with TCP/IP protocol stacks, OpenVMS systems can par-E ticipate in multivendor, multiprotocol networks adhering to open net-  working standards.  0 Compaq DECnet-Plus for OpenVMS features include:  D o  The ability to run DECnet and OSI applications over TCP/IP trans-	    ports.   E o  Support for 64-bit addresses, allowing 64-bit network applications H    to take advantage of the P2 addressing of Alpha systems running Open-C    VMS Alpha Version 7.1 or later. Support for 64-bit addressing is -    limited to the DECnet-Plus $QIO interface.   5 o  Continued support for 32-bit network applications.   C o  Host-based routing, which includes communication with nodes run- G    ning DECnet Phase IV and OSI protocols, FDDI large packets, and X.25 +    switched and permanent virtual circuits.   G o  FAST configuration option, which allows quick configuration upgrades     from Phase IV to Phase V.  C                                                          April 2001        C o  X.25 network management interface, providing efficient wide area     network (WAN) management.  C o  The ability to configure all members of a cluster from any clus-     ter member.  1 o  OSI application programming interfaces (APIs).   E o  Expanded naming options, allowing the use of a larger Local names- F    pace, DECdns, and/or DNS/BIND as naming services. Note that the useD    of DECdns requires the presence of an OpenVMS VAX, Tru64 UNIX, orG    ULTRIX MIPS system to host the DECdns server. The server is not sup-     ported on Alpha systems.   G o  Routing segregated mode to allow the Routing layer to choose a Phase D    IV router for those packets having a Phase IV compatible address.C    (Packets having a Phase V extended address are sent to a Phase V 5    router by default.) This is a configurable option.   D o  Reverse path caching to capture path information for later use in    reaching remote systems.   C o  Increased network size, supported through the use of ISO OSI ad-     dressing.  5 o  Simplified installation and configuration process.   E o  The Network Control Language (NCL). Network management is based on C    DNA CMIP, Compaq's implementation of the OSI international stan- /    dard Common Management Information Protocol.   C o  A graphical network management user interface, net$mgmt, for im- (    proved network management, using NCL.  D o  An NCP (Network Control Program) emulator to facilitate installa-8    tion of layered products written for DECnet Phase IV.  C o  Installation using the POLYCENTER Software Installation utility.   F o  Support for topologies using multicircuit and multihomed end nodes.  "                                  2       * o  Dynamic connections over X.25 networks.  D Compaq DECnet-Plus for OpenVMS includes OSI implementation in accor-4 dance with current U.S. and U.K. GOSIP requirements:  0 o  Application, Presentation, and Session layers  >    -  File Transfer, Access, and Management (FTAM) application  "    -  Virtual Terminal application  E    -  Applicaton Service Elements (ASEs), including ACSE (Association        Control Service Element)  & o  Transport layer classes 0, 2, and 4   o  Lower layers   A    -  OSI addressing formats, supporting large network topologies   7    -  End system to intermediate system (ES-IS) routing   E    -  Connectionless Mode Network Service (CLNS) over local area net- 3       work (LAN), wide area network (WAN), and X.25   E    -  Logical Link Control type 2 (LLC2) for Connection-Oriented Net- "       work Service (CONS) over LAN  E    -  Data Link layer, supporting High-level Data Link Control (HDLC) E       for wide area communications, ISO 8802-3 (Ethernet CSMA/CD) and C       FDDI LANs. HDLC support includes the LAPB (Link Access Proto- 5       col Balanced) protocol for X.25 communications.   E    -  Physical layer, with CSMA/CD, HDLC, and FDDI devices supported.   G Compaq DECnet-Plus for OpenVMS offers task-to-task communications, file D management, downline system and task loading, network command termi-C nals, and network resource sharing capabilities using DNA, OSI, and D TCP/IP protocols. DECnet-Plus for OpenVMS communicates with adjacentD and non-adjacent DECnet Phase IV, PATHWORKS, DECnet-Plus implementa-G tions on other OpenVMS systems, ULTRIX, and Tru64 UNIX systems, as well F as systems running TCP/IP transports and on OSI-compliant systems from other vendors.  "                                  3       E OpenVMS programs written in native-mode programming languages can use % DECnet-Plus for OpenVMS capabilities.   H Depending on the system configuration, networks combining Compaq DECnet-D Plus for OpenVMS systems with other DECnet, OSI, and TCP/IP productsF may limit the functions available if all products do not support equal	 features.    Data Link Layer   D Compaq DECnet-Plus for OpenVMS uses Ethernet and FDDI communications2 controllers to interface with other network nodes.  D LAN connectivity is provided by the CSMA/CD and FDDI controllers andD drivers supporting ISO 8802-2 Logical Link Control (LLC) Type 1 con-C nectionless service. Compaq DECnet-Plus also supports Ethernet Ver- ) sion 2 packet formats on CSMA/CD devices.   D Use of FDDI packets larger than 1500 bytes requires a Phase V routerC on the FDDI LAN. The maximum Phase V FDDI packet size is 4352 bytes D for use with other Phase V network nodes. As with cluster alias sup-C port, you can configure the Phase V router to run the Phase IV dis- D tance vector routing protocol or the Phase V link state routing pro- tocol.  G WAN connectivity is provided by optional X.25 software supporting host- , based synchronous communications interfaces.  D All the synchronous devices support DIGITAL-HDLC and LAPB/E and dataE link protocols. X.25 for OpenVMS Alpha is required to establish host-  based wide area connections.  C Compaq DECnet-Plus for OpenVMS allows a maximum of 32 circuits on a D full routing node and up to four circuits defined and operational onD an end system. This capability allows a single end system to be con-F nected to up to four separate LANs or WANs. Compaq recommends that the/ circuits be equal in capacity and connectivity.       "                                  4        X.25  F The optional X.25 for OpenVMS Alpha software allows Compaq DECnet-PlusD for OpenVMS Alpha systems to connect to PSDNs (packet switching dataG networks) conforming to CCITT Recommendation X.25 (1980 or 1984) and/or E ISO 7776 and 8208, or through an X.25 relay system directly connected F to a PSDN, or through an X.25 connector node (X.25 gateway). The soft-D ware allows process-to-process as well as terminal-to-process commu-D nications between Alpha systems and remote DTE (data terminal equip- ment) over a PSDN.  I The X.25 software provides the Connection-Oriented Network Service (CONS) E to allow mapping between a destination NSAP address and a destination " DTE address according to ISO 8348.  E Direct access to a PSDN (using the supported device drivers) requires 3 an X.25 license. See the Optional Software section.   D For more details on the X.25 software for OpenVMS Alpha systems, re-C fer to the X.25 for OpenVMS Alpha Software Product Description (SPD 
 47.37.xx).  
 Network Layer   D Compaq DECnet-Plus for OpenVMS supports the Connectionless-Mode Net-G work Service (CLNS) and the Connection-Oriented Network Service (CONS).   D Exchange of routing information between end systems and routers usesE the ISO 9542 ES-IS routing protocol. This protocol allows DECnet-Plus I systems to autoconfigure as end systems with ISO 9542-conformant routers.   D Addresses conform to the ISO 8348 Addendum 2 specification, allowingF the support of large network topologies. As long as the system addressG stays within the addressing range of Phase IV systems (up to 1,023 sys- E tems per area and up to 63 areas per network), and uses the same ini- @ tial domain part (IDP), you can use Phase IV or Phase V routers.        "                                  5       E The Network layer supports the capability of an end system to be mul- E ticircuited and multihomed. Multicircuit support allows multiple cir- D cuits to be active simultaneously. This functionality increases net-C work reliability and data throughput. Multihomed end-system support : allows a system to have up to three network entity titles.  C Segregated routing mode is a settable attribute. It directs routing F to choose a Phase IV router for those packets having a destination ad-D dress that can be translated to the Phase IV format. All other pack-/ ets are sent to a Phase V router, if available.   C The Routing layer is able to cache information about the paths that  are used to reach remote nodes.    Transport Layer   4 Compaq DECnet-Plus for OpenVMS provides support for:  2 o  OSI Transport protocol as specified in ISO 8073  D o  RFC 1006 and RFC 1859 to allow DECnet and OSI applications to run    over TCP/IP  " o  Network Services Protocol (NSP)  E NSP, RFC 1006, and OSI transports support communications between DEC- F net, TCP/IP, and OSI systems. NSP provides backward compatibility with Phase IV DECnet systems.  D RFC 1859 support for DECnet applications is provided by a kernel in-E terface that is implemented on all TCP/IP stacks available for use on D the OpenVMS operating system. The supported applications include allI licensed DECnet applications as well as layered products and user-written E applications that conform to the documented DECnet programming inter-  faces.  I The RFC 1859 is a specification for running OSI applications over TCP/IP. E Operation of the FTAM and Virtual Terminal applications over a TCP/IP C network is supported along with other layered OSI applications such  as X.400 and X.500.   "                                  6       C A separate TCP/IP stack is required on the same system with DECnet- C Plus. See the Optional Software section of this SPD for information  on supported TCP/IP products.   C OSI transport supports transport classes 0, 2, and 4 on connection- 9 oriented networks and class 4 on connectionless networks.   0 OSI transport uses two types of network service:  D o  The Connectionless-Mode Network Service (CLNS) using the InternetC    protocol (ISO 8473) and ES-IS protocol (ISO 9542) to communicate C    across linked subnetworks. The inactive subset of ISO 8473 (null C    internet) is also supported for communications over a single ISO     8802-3 local area network.   2 o  The Connection-Oriented Network Service (CONS).   Upper Layers  D Compaq DECnet-Plus for OpenVMS software provides the OSI upper layerE stack consisting of Session, Presentation and Application layers. The F Application layer provides Association Control Service Element (ACSE);H File Transfer, Management, and Access (FTAM); and Virtual Terminal (VT).  E Compaq DECnet-Plus for OpenVMS also provides a range of DECnet appli- D cations and services including file and record access, remote termi- nal access, mail, and phone.   Applications  " Transport Options for Applications  E You can run applications written to the DECnet upper layers over NSP, D OSI, or TCP/IP transports using RFC 1006 and RFC 1859. This includesC the network applications that are licensed with DECnet-Plus as well F as user-written applications that adhere to the documented DECnet pro-D gramming interfaces. The use of TCP/IP transports using RFC 1006 andC RFC 1859 does not require any modification to the existing applica-  tion.   "                                  7       D You can run applications written to the OSI upper layers over OSI or TCP/IP transports.   Remote File Transfer  E Compaq DECnet-Plus for OpenVMS supports two upper layer protocols for C remote file transfer: the OSI protocol's File Transfer, Access, and < Management (FTAM) and the DECnet Data Access Protocol (DAP).   FTAM  E FTAM supports file transfer, access, and management between a DECnet- C Plus for OpenVMS system and other systems with software adhering to F ISO 8571. In addition, FTAM is conformant with NIST Phase II and PhaseC III agreements and is certified as being conformant to the released 7 specifications of U.S. GOSIP, U.K. GOSIP, and ENV41204.    In addition, FTAM:  G o  Provides users the ability to create, delete, rename, view, and copy     files using DCL commands.  D o  Is implemented as an Application Service Element (ASE) of the OSI    Application layer.   = o  Acts as the initiator or as the responder in a connection.   D o  Accesses and transfers files with both binary and character data.@    It supports FTAM-1, FTAM-2, FTAM-3, and NBS-9 document types.  E Compaq DECnet-Plus for OpenVMS also supports gateway services between 
 FTAM and DAP.   E A full description of the FTAM services in DECnet-Plus for OpenVMS is ( provided in Appendix A of this document.   DAP   D The DECnet Data Access Protocol (DAP) supports task-to-task communi-2 cations, file and record access, and proxy access.  "                                  8       E Task-to-Task Communications: For most applications, you can use task- D to-task communications in a transparent manner where the remote taskD is treated as a full-duplex, record-oriented device. Transparent op-H eration is provided with the following interfaces: system service calls,I RMS calls (OPEN, GET, PUT, and CLOSE), and high-level language I/O state- E ments (which are mapped to RMS calls). A nontransparent mode of task- D to-task communications is offered by means of the system service in-G terface that extends the capabilities provided by the transparent mode. D These capabilities include support for interrupt messages and multi- ple inbound connect requests.   C Using Compaq DECnet-Plus for OpenVMS, an OpenVMS program written in C a native mode programming language can exchange messages with other  user programs.  D File Access: File access is supported to and from remote DECnet-PlusC for OpenVMS systems, transparent to native mode high-level language D programs using RMS. User programs can sequentially read, create, and delete files on a remote node.  E Record Access: User programs can perform record level operations such H as GET, PUT, UPDATE, DELETE, FIND, and REWIND to access and modify filesC residing on a remote OpenVMS node. In addition to sequential access E to a file, several other access methods are supported through RMS us- C ing DECnet-Plus for OpenVMS. These methods include random access by D relative record number, random access by key value, random access byE record file address (RFA), and block I/O access by virtual block num-  ber.  E Proxy Access: Remote users can have access to up to 15 proxy accounts C on a specific remote system. One proxy account should be designated 2 as the default proxy account on the remote system.    Command Language File Management  C You can use most OpenVMS DIGITAL Command Language (DCL) commands to H perform remote file operations. These commands include: ANALYZE, APPEND,E BACKUP, CLOSE, CONVERT, COPY, CREATE, DELETE, DIFFERENCES, DIRECTORY, D DUMP, OPEN, PRINT, PURGE, READ, SEARCH, SUBMIT, TYPE, and WRITE. TheC operation of these commands is transparent except for commands that   "                                  9       F invoke processing on a specific system (for example, SUBMIT/REMOTE andD PRINT/REMOTE). Only a node name added to a file specification is re-F quired to invoke the network capabilities using one of these commands.  E Using the COPY command, a user can transfer sequential, relative, and_E indexed-sequential (ISAM) files between DECnet-Plus for OpenVMS nodesmE that support compatible file structures and record formats. Users cantI transfer sequential or relative files with fixed length, variable length, G or variable length with fixed control field records between two DECnet- H Plus for OpenVMS systems. Similarly, multikeyed indexed files with vari-+ able or fixed length records are supported.n  C The SUBMIT/REMOTE command allows command files residing on a remoteaG node to be submitted for execution at the remote node. The command filenE must be in the format expected by the node responsible for execution.pC DECnet-Plus for OpenVMS allows OpenVMS command files to be receivedt  from other systems and executed.  C The DCL command EXCHANGE/NETWORK allows the transfer of files to orpI from heterogeneous systems. This command gives users the option to trans-tC fer file types between MS-DOS, ULTRIX, and UNIX systems and OpenVMSCF systems regardless of record semantics. Unlike the COPY command, whichC preserves file and record organization during a file transfer, this6D command enables the user to modify file and record attributes during file transfer.                              "                                 10 o  a  - OSI Application Programming Interfaces (APIs)d  E The OSI application programming interfaces enable users to write dis-eE tributed applications that communicate over open networks and use thet% OSI services provided by DECnet-Plus.a  C The interfaces are provided under the Extended Function license and  include:  ? o  An interface to FTAM (File Transfer, Access, and Management)i  C o  Interfaces to the ACSE (Association Control Service Element) and     Presentation layers  ; o  An interface to ROSE (Remote Operations Service Element)a  ( o  An interface to the OSI Session layer  D The interfaces permit application writers to use the services of the' OSI upper layers in their applications.r  F The APIs allow you to develop applications on DECnet-Plus systems. YouF must compile and link source code with the APIs. The APIs are requiredF on the development system and the compile/link system. You can run theD resulting application on any DECnet-Plus system with the appropriateD operating system. The APIs are not required on these target systems.+ See Appendix C for details on the OSI APIs.a   Network Virtual Terminal  C DECnet-Plus supports two upper layer protocols for terminal access:sF the OSI Virtual Terminal protocol and the DECnet Command Terminal pro- tocol.   Virtual Terminal  E Virtual Terminal (VT) supports the ISO Virtual Terminal Protocol (ISOhE 9041). This protocol allows remote logins and access to remote appli-sC cations between DECnet-Plus for OpenVMS systems and any remote sys- G tem, including multivendor systems, that also run an ISO-compliant Vir-o tual Terminal implementation.l  "                                 11 s  o  G Virtual Terminal is implemented as an Application Service Element (ASE)  of the OSI Application layer.t  E Virtual Terminal may act as the terminal/initiator (for a local user)g/ or as the host/responder (for the remote user).   G A full description of Virtual Terminal features is provided in Appendix- B of this SPD.                                                                "                                 12 n  i   Command Terminal  F The DCL command SET HOST allows a terminal user on one DECnet-Plus forE OpenVMS node to establish a logical connection to another DECnet-PlustE node that uses the Command Terminal (CTERM) protocol. This connection G makes the terminal appear to be physically connected to the remote sys-aF tem and the operator can use all the standard system and network util-D ities supported by that remote node. This capability is particularlyC useful for doing remote program development and allows the terminaltE users on smaller application-oriented systems to use the resources of,$ larger development-oriented systems.  E Other interfaces are included in DECnet-Plus for OpenVMS. You can de-yE velop programs and procedures based on these interfaces for functionsdF such as file access and task-to-task communications on individual sys-C tems. Because the DECnet-Plus for OpenVMS interfaces stay the same,CG you can use the programs and procedures developed on an individual sys- 4 tem in a network environment without modifying them.   Services   Downline Loading  F Compaq DECnet-Plus for OpenVMS allows for the loading of an unattendedE system using the services provided by the Maintenance Operations Mod- D ule (MOM). MOM provides a set of maintenance operations over variousE types of circuits by using the Maintenance Operations Protocol (MOP).SD A loadable system is a system that has a load device enabled for MOPF service functions and for which a properly formatted load file is sup-E plied. Downline loading involves transferring a copy of the load file D image to a remote target node. Load requests can come from the localH DECnet-Plus for OpenVMS operator or from the target node. Downline load-, ing is supported for Compaq server products.   Downline Task Loadingp          "                                 13 d  .  F Initial task images for loadable systems can be stored on OpenVMS fileE system devices and loaded into remote nodes. Programs already execut- D ing on loadable systems can be checkpointed to the host OpenVMS fileD system and later restored to main memory in the node. These featuresE simplify the operation of network systems that do not have mass stor-  age devices.   Upline Dumping  C Memory images of adjacent nodes connected by Compaq DECnet-Plus fordG OpenVMS can be written or dumped into a file on an OpenVMS system. This F facility provides assistance in troubleshooting in the event of a sys-F tem crash. This facility is also supported for Compaq server products.                                                      "                                 14 C  /   Mail  E The OpenVMS Mail utility allows transmission of text messages betweentE users on systems supporting MAIL-11. The Compaq DECnet-Plus for Open- F VMS software allows users to exchange mail with users of other DECnet-
 Plus systems.o   Phoneh  C The OpenVMS Phone utility allows users to send and receive data in-oH teractively from one user's terminal to another user's terminal. DECnet-C Plus allows users on different systems in the same DECnet-Plus net-  work to exchange information.l   OpenVMS Cluster Alias   C Compaq DECnet-Plus for OpenVMS supports the ability to access nodesVD in an OpenVMS Cluster using a separate alias node address, while re-E taining the ability to address each node in the cluster individually. F Not all network objects can be accessed using this mechanism. The max-F imum number of nodes supported for a cluster alias is 94. Refer to the9 OpenVMS Cluster SPD (42.18.xx) for relevant restrictions.   C DECnet-Plus no longer requires a cluster member to be configured as C a router. Clusters in a DECnet-Plus environment require a reachable " IS-IS compliant router on the LAN.   Network Management  G Network management is provided with the Network Control Language (NCL).fE Network management implements the DECnet-Plus layered model, based ondE the Compaq hierarchical structure called Enterprise Management Archi-o tecture (EMA).  H Users can access NCL through either a command line interface or a graph-F ical user interface (GUI) called net$mgmt. The GUI allows network man-E agers to view the status of network components and control those com-w, ponents from a Motif-based window interface.    "                                 15 d  i  E The Compaq DECnet-Plus for OpenVMS network management software allows. system and network managers to:g  D o  Control and monitor the operation of a network and provide infor-4    mation related to network traffic and performance  ) o  Configure network operating parameters   6 o  Start up and shut down network components as needed  F o  Detect and isolate network problems, and return the network to ser-    vice once repaired.  E In addition, the network management software can provide information,cF warning network managers of faulty or failing network components, both hardware and software.  C Network Command Language (NCL) is provided as a utility to the net-a7 work manager to perform the operations described above.e  D Network managers can also use NCL to test specific components of theD network. NCL enables transmission and reception of test messages ei-E ther between systems or through controller loopback arrangements. The0G messages can then be compared for possible errors. NCL helps users iso-e late network problems.  G Compaq DECnet-Plus for OpenVMS provides network event logging to a ter- C minal device, disk file, or remote system. NCL users can enable and D disable the event logging facility as well as optionally filter spe-
 cific events.   E NCL uses the DNA Common Management Information Protocol (CMIP), whichrH permits entity management from a single location anywhere in the DECnet-
 Plus network.a  E The Common Trace Facility (CTF) allows the network manager to collectmF and display information about specific protocol exchanges between sys- tems.o    "                                 16 r     E Compaq DECnet-Plus for OpenVMS supports an ISO CMISE application pro-eE gramming interface (API) conforming to the service definitions in ISOcD 9595. The API allows for development of applications that can commu-C nicate with other management applications conforming to ISO 9595 onp remote nodes in the network.  E DECnet-Plus supports the DECnet Phase IV NCP for remote management ofn Phase IV DECnet systems.   Name Service Options  C Compaq DECnet-Plus for OpenVMS allows the use of one or more naming D services. The available services are DECdns, DNS/BIND, and the LocalD namespace. Node name and addressing information is stored in the na-D tive name service; TCP/IP information is maintained in DNS/BIND, andF DECnet and OSI information is maintained in DECdns or the Local names- pace.M  C When you use more than one name service, a configurable search listCD defines the order in which the existing services are to be accessed.   Local Namespace   F Using the Local namespace, you can define up to 100,000 nodes in a lo-D cal naming database. A migration tool is available to move the PhaseD IV database to the new large local file format and/or DECdns format.   DNS/BIND  D DECnet can now use TCP/IP naming and addressing information from the DNS/BIND name service.   DECdns  F Compaq DECnet-Plus for OpenVMS provides a global naming service called0 the DIGITAL Distributed Naming Service (DECdns).  H The full DECdns service provides a consistent, network-wide set of namesC for network resources called the namespace. This namespace is main-oC tained by one or more DECdns server systems. Compaq recommends thato  "                                 17 e  o  F DECdns servers be installed on at least two systems in every LAN. This/ should provide adequate service and redundancy.   C The DECdns client is included in DECnet-Plus for OpenVMS Alpha. The G DECdns server is not supported on Alpha systems. An OpenVMS VAX, ULTRIX0D MIPS, or Tru64 UNIX system is required to support the DECdns server.  ( The features provided by DECdns include:  G o  A networkwide name-to-attribute mapping service that allows selectedeC    Compaq applications to create, read, modify, and delete names inr    the namespace  D o  A hierarchical structure permitting a large number of names to be,    stored and distributed across the network  / o  Access control to each name in the namespacen   o  Management and event loggingc   Distributed Time Service  C Compaq DECnet-Plus for OpenVMS provides a network time service withpF DECdts, the DIGITAL Distributed Time Service. DECdts provides precise,F fault-tolerant clock synchronization for systems in a LAN or WAN. TimeF is provided in Coordinated Universal Time (UTC) and can be used acrossD a global network. Several forms of time providers are supported, andC a callable interface for applications allows users to add their owntE time providers. DECdts can be used by distributed applications to de-n3 termine event sequencing, duration, and scheduling.   	 Operation   E DECnet-Plus is implemented under OpenVMS as an ancillary control pro-oF cess (ACP) and a network device driver with Compaq-supplied executive-) level components and user-level programs.r  D The normal OpenVMS protection has been incorporated in the operationE of DECnet-Plus. For example, incoming connects, including file access.C and file transfer requests, are protected by the normal OpenVMS lo-eE gin and file protection mechanisms. Outgoing connects, including filed  "                                 18 s  n  C access and file transfer requests, can include user password infor-sC mation that is implicitly specified by NCL, or explicitly specified.0 by the user for verification on the remote node.   Configuration and Performancee  E You can configure DECnet-Plus using either the BASIC or ADVANCED con-I figuration options.p  @ Cluster nodes are configurable from any node within the cluster.  D As with any network protocol, the performance of a given DECnet-PlusE for OpenVMS node is a function not only of the expected network traf- G fic and resultant processing, but also of the amount of concurrent pro-eE cessing specific to that node. Thus, node performance depends on manyP factors including:   o  CPU typeM  < o  Number and type of devices attached to the particular CPU  , o  Number of device interrupts per unit time  ) o  Communications line(s) characteristicsm   o  Number and size of buffersc  - o  Message size and frequency of transmission    o  Applications in use  F It is important to note that the rate at which user data can be trans-F mitted (throughput) over a communications line can sometimes approach,E but will never exceed, the actual line speed. This is because the ac-sG tual throughput is a function of many factors, including the line qual- E ity, protocol overhead, topology, and network application(s), as well % as the factors cited in this section.r  G The performance of DECnet-Plus is comparable to the performance of DEC- 
 net Phase IV.i  "                                 19    v   Standards Conformanceo  C Compaq DECnet-Plus for OpenVMS has been designed and implemented tot# conform to the following standards:    o  ISO  
    -  4335      -  7776, 7809  E    -  8073, 8208, 8327, 8473, 8571, 8650, 8802-2, 8802-3, 8823, 8878, 
       8881      -  9314, 9542, 9041  
    -  3309  $ o  EN 41 204, 41 205, 41 206, 41 207  D o  CCITT Recommendation X.25 (1978, 1980, or 1984) using the LAPB orB    LAPBE variants of the X.25 packet level and data link protocols   o  U.S. GOSIP V2.0   o  U.K. GOSIP V4.0  E Contact your local Compaq office for the most recent conformance cer-s
 tificates.  
 DocumentationL  F The documentation for Compaq DECnet-Plus for OpenVMS Alpha is supplied as follows:   H o  Online versions of the documentation are shipped as part of the Open-E    VMS Online Documentation Library on CD-ROM and on the OpenVMS lay-i    ered product CD-ROM.   F o  Printed copies of the documentation are available as a separate or-    der.d  D o  An optional X.25 documentation set covering accounting, X.29, and.    X.25 Mail is available as a separate order.  "                                 20 s  .  @ o  New features are documented extensively in the Release Notes.   Installation  C DECnet-Plus software is customer installable. Installation servicesSD are available for customers who request installation of the software5 product by an experienced Compaq software specialist.P  F Compaq requires that a customer's first use of X.25 include Compaq In-C stallation Services. These services provide for installation of theo> software product by an experienced Compaq software specialist.   Customer Responsibilities   C Before Compaq Services can install the software, the customer must:B  E o  Ensure that the system meets the minimum hardware and software re-t1    quirements (as specified in the relevant SPDs)e  D o  Prior to installing Compaq hardware or software, obtain, install,E    and demonstrate as operational any modems and other necessary cus-eG    tomer equipment or facilities to which Compaq's communications hard-      ware or software will connect  D o  Designate one adjacent node to verify installation and connectiv-    ity  E o  Make available for a reasonable period of time, as mutually agreedfC    upon by Compaq and the customer, all hardware communications fa-bB    cilities and terminals that are to be used during installation.  C Delays caused by any failure to meet these responsibilities will ber6 charged at the prevailing rate for time and materials.  C Installation of Compaq DECnet-Plus for OpenVMS consists of the fol-t
 lowing tasks:M  D o  Verify that all components of Compaq DECnet-Plus for OpenVMS have    been received.   F o  Verify that the necessary versions of the OpenVMS software and doc-    umentation are available.  "                                 21 e  p  , o  Verify the appropriate SYSGEN parameters.F    Note: If a software specialist is required to modify the previouslyE    installed operating system parameters, a time and materials charge,    will apply.  C o  Create any necessary Compaq DECnet-Plus for OpenVMS accounts ands    directories.   C o  Enable software by registering the License Product Authorizationl    Key (PAK) .  C o  Install the Compaq DECnet-Plus software on the target system us-a5    ing the POLYCENTER Software Installation utility .m  C o  Verify the proper installation of Compaq DECnet-Plus for OpenVMSeD    by running a series of tests to show connectivity to a designated    node.  C Connectivity to all other nodes within the network is the responsi-eE bility of the customer. Compaq recommends the use of NCL to help ver-t ify connectivity.t  G In some cases, the PSDN supplier (or PTT) may impose restrictions, lim- C itations, or requirements on the proposed Compaq network configura-pC tion. The customer must understand and adhere to these controls fori every network.   Hardware Requirements   F Refer to the OpenVMS Operating System for Alpha and VAX Software Prod-D uct Description (SPD 25.01.xx) for hardware requirements and proces- sor support.  D For general device or controller descriptions, refer to the Network- ing Buyer's Guide.  0 Disk Space Requirements (Block Cluster Size = 1)  C The following counts refer to the disk space required on the systemPC disk. The sizes are approximate; actual sizes may vary depending onyC the user's system environment, configuration, and software options.   "                                 22 o     % Disk space required for installation:T   -  Base software: 89,000 blocks   - -  With all optional software: 116,000 blockse   Supported LAN Adapters  F Refer to the OpenVMS Operating System for Alpha and VAX Software Prod-D uct Description (SPD 25.01.xx) for a list of supported LAN adapters.   Software Requirements   D Compaq DECnet-Plus for OpenVMS Alpha requires OpenVMS operating sys- tem Version 7.3.   Optional Softwaret   TCP/IP  C A separate TCP/IP protocol stack is required to use the DECnet overyE TCP/IP features in DECnet-Plus. This release contains support for In-oC ternet Protocol Version 4 (IPv4) and does not support Internet Pro-lD tocol Version 6 (IPv6). The following TCP/IP product has been tested with DECnet-Plus:   3 o  DIGITAL TCP/IP Services for OpenVMS Version 5.1. 6    DIGITAL TCP/IP Client Software License: QL-0M2A*-**8    DIGITAL TCP/IP Services Software License: QL-0LXA*-**5    DIGITAL TCP/IP Client Upgrade License: QL-0PHA*-**n    SPD: 46.46.xx   X.25 Optional Licensea  E The DECnet-Plus for OpenVMS Alpha license grants the right to use thesD OSI applications for CONS over LLC2 or CLNS over DEC-HDLC. All otherE X.25 software functions over LAPB and LLC2 require the X.25 for Open-n VMS Alpha license.    "                                 23 r  a  F The X.25 for OpenVMS Alpha license is also required to enable the X.25C utilities, such as X.25 Mail and SET HOST/X.25, as well as the X.25t* application programming interfaces (APIs).   Software License: QL-0THA*-AAy  $ Media and Documentation: QA-03XAA-H8 (See SPD 47.37.xx.)    Growth Considerationsa  D The minimum hardware/software requirements for any future version ofC this product may be different from the requirements for the currenth version.   Distribution Media  C This product is available as part of the OpenVMS Consolidated Soft-iF ware Distribution on CD-ROM. The software documentation for this prod-E uct is also available as part of the OpenVMS Online Documentation Li-r brary on CD-ROM.   Ordering Information  D In the following table, asterisks (*) denote variant fields. For ad-C ditional information on available licenses, services, and media re-S" fer to the appropriate price book.  - Software Li-         QL-MTFA*-AA (End System)i censes:o  4                      QL-MTGA*-AA (Extended Function)    Software Media:      QA-03XAA-H8    Software Documen-    QA-MTFAA-GZ tation:       "                                 24 l  l      Consolidated         QT-03XAA-*8 Distribution	 Services:n   Software Licensing  D The DECnet-Plus licenses give users the right to use the software onE a single CPU and include the delivery of a License Product Authoriza-o> tion Key (PAK) to enable the DECnet-Plus for OpenVMS software.  G The End System license grants the right to use all the DECnet-Plus fea-mG tures with the exception of the cluster alias, the OSI application pro- ? gramming interfaces, the OSI applications gateway, and routing.n  E The Extended Function license grants the right to use the DECnet-PlusDC end-system features, OSI application gateways, OSI application pro-PF gramming interfaces, host-based routing, and the cluster alias. An Ex-G tended Function license is required on at least one node in every clus-o9 ter configuration to enable the use of the cluster alias.m  E This software is furnished under a license only. For more information D about Compaq's licensing terms and policies, contact your local Com- paq office.l  # License Management Facility Supporte  D This product supports the OpenVMS Alpha License Management Facility.  < License units for this product are allocated on a CPU basis.  E For more information on the License Management Facility, refer to theuE OpenVMS Alpha Operating System for Alpha and VAX Software Product De-lE scription (SPD 25.01.xx) or the License Management Facility manual ofs5 the OpenVMS Alpha operating system documentation set.f  F For more information about Compaq's licensing terms and policies, con- tact your local Compaq office.    "                                 25 a  s   Software Product Servicesn   Prerequisite Support  D For the use of X.25 with PSDNs, the customer and Compaq must jointlyD prepare a Network Profile and Customer Support Plan covering all theH intended network nodes, their usage of switched virtual circuits (SVCs),D permanent virtual circuits (PVCs), and other network facilities, andF their support. Without this Network Profile and Customer Support Plan,. Compaq cannot support the network connections.  D A variety of service options are available from Compaq. For more in-, formation, contact your local Compaq office.   Software Warrantyp  F This software is provided by Compaq with a 90 day comformance warrantyF in accordance with the Compaq warranty terms applicable to the license	 purchase.N                                          "                                 26    l  8 Appendix A: File Transfer, Access, and Management (FTAM)  C FTAM software provides communications for the following file opera-t tions between open systems:   1 o  Copying files between local and remote systemso  ) o  Appending, deleting, or renaming filesn  % o  Displaying information about filesn  E An open system is a computer system that implements the standards fordG each of the seven layers of the Open Systems Interconnection (OSI) Ref-iC erence Model for communications as defined by the International Or-rF ganization for Standardization. An FTAM system is any open system con-E taining an FTAM implementation that conforms to the FTAM standard andtF includes the implementations of the necessary underlying OSI services.  F FTAM implements several standards that define the following componentsF of these layers of the OSI Basic Reference Model: the FTAM service el-C ement and the Association Control Service Element (ACSE) of the Ap- ? plication layer, the Presentation layer, and the Session layer.w   Supported Standardsi  - FTAM conforms to the following OSI standards:t  D o  ISO 8571 - File Transfer, Access, and Management service and pro-    tocol   o  ISO 8650 - ACSE protocol.  # o  ISO 8823 - Presentation protocolo   o  ISO 8327 - Session protocol  D Table 1 compares the supported implementation profiles for different6 standards bodies and their relationship to each other.    "                                 27 n  y  C ___________________________________________________________________r  C Table_1:_Standards_and_Implementation______________________________   
 International  Standardized Profiles (ISP)C ISO_10607_________NIST________CEN/CENELEC_and_EWOS_________________l   Part 1: Spec-     -           -  ification of
 ACSE, Pre-
 sentation and  Session proto- cols for use by FTAM    Part 2: Def-      -           -s
 inition of document types, con-a
 straint sets,e and syntaxes  % Part 3: AFT11     T1 -        A/111 -f) - Simple          Simple      iENV 41 204d File Trans-       File fer Service       Transfer (Unstructured)  % Part 4: AFT12     T2 - Po-    A/112 -o( (DISP)[1] -       sitional    ENV 41 206 Positional        File File Trans-       Transfer fer Service 	 (Flat)[2]C  C ___________________________________________________________________a [1]Draft ISP( [2]AFT12 is not supported by DECnet-Plus  "                                 28 t  L    C ___________________________________________________________________-  
 Internationalc Standardized Profiles (ISP)C ISO_10607_________NIST________CEN/CENELEC_and_EWOS_________________E  $ Part 5: AFT3      M1 -        A/13 -( (DISP)[1] -       Manage-     ENV 41 205 File Manage-      mentC ment_Service_______________________________________________________  [1]Draft ISPC ___________________________________________________________________    FTAM Component Softwares  E The component software includes the user facilities (initiators), re-w< sponders, management tools, and problem determination tools.   FTAM User Facilities  E Users access the FTAM user facilities by entering the following Open-EC VMS operating system commands: APPEND, COPY, DIRECTORY, RENAME, andcG DELETE. These commands operate on files stored on any FTAM system whoseCC implementations are compatible with FTAM. You cannot use these com-w8 mands to manipulate files directly on your local system.  & Support for Any File-Naming Convention  C A file designation is system-specific information that identifies aeF file to its storage system. FTAM software lets users specify files us-F ing the naming conventions of the systems where the files reside. FTAMD supports the OpenVMS operating system RMS format for file specifica-E tions and a comparable style of file-specification format that accom-T" modates non-RMS file designations.        "                                 29    D   Support for Several File Types  F FTAM software can access and transfer files containing both binary andE ASCII data. FTAM-1, FTAM-2, FTAM-3, and NBS-9 document types are sup-  ported.e  E FTAM-1 files are unstructured text files, FTAM-2 files are sequentialnC text files, and FTAM-3 files are unstructured binary files. Table 2 E shows the parameters supported by FTAM-1, FTAM-2, and FTAM-3 documentS types.  C ___________________________________________________________________   C Table_2:_FTAM_Document_Types_______________________________________              String Document  Signifi-    Universal C Type______cance_______Class_______Maximum_String_Length____________   A FTAM-1    Not         IA5String   Presence and absence of parame- %           significant             tere#                       GeneralString   7           Fixed       VisibleStrinPresence of parametere  #                       GraphicStringe  A           Variable    VisibleStrinPresence and absence of parame-i%                                   tery#                       GraphicStringo  B FTAM-2    Not         VisibleStrinPresence or absence of parameter           significant #                       GraphicStringe  B FTAM-3    Not                     Presence or absence of parameter           significanti  C __________Fixed___________________Presence_of_parameter____________n  % NBS-9 files are NBS file directories.s  "                                 30       / Flexible and Transparent Access for Local Filesd  D FTAM software treats local files the same way that the OpenVMS oper-% ating system file system treats them.i   File Transfers  E The FTAM COPY command transfers files between compatible FTAM systemsfE without modifying the source file. The facility can transfer files inAC either direction between the local system and a remote FTAM system.oE The COPY command can also transfer files between two remote FTAM sys-f tems for a local FTAM user.s  F The COPY command also allows you to append one or more files to a sin-/ gle output file within or between FTAM systems.u   FTAM-DAP Gateway  D The FTAM-DAP Gateway lets you perform file operations from a non-OSIG system that supports the DAP protocol to an OSI system supporting FTAM.tD Remote users of the gateway need not establish accounts on the gate-D way system to use its capabilities. The gateway does not support the APPEND functionality.M                                  "                                 31 t     
 File Deletion   E The FTAM DELETE command lets you delete one or more files on any com-aG bination of FTAM systems provided you have delete access to those filesa on the specific FTAM system.   Renaming Requestsr  E The FTAM RENAME command allows you to rename files. The command worksoF on files stored on remote FTAM systems (remote files). The command en-C ables you to change the path name or file name of an existing file.oC For remote files, you must specify whatever type of information the 1 remote FTAM system requires for specifying files.c   Directory Requests  D The FTAM DIRECTORY command lets you display the complete set of FTAMF file attributes. Specific options allow you to vary the display of at-D tributes that are meaningful in an OpenVMS operating system environ-G ment, for example, date and time of the last modification of file name.1   FTAM File Error Recovery  F FTAM provides file error recovery functionality, both in the COPY ini-E tiator command and in the FTAM responder. File error recovery is pro-0? vided for classes 1, 2, and 3 errors as detailed in ISO 8571-4.e  D Class 1 file error recovery provides only the restart functionality,E while classes 2 and 3 provide both the restart and recovery function-o ality as follows:e  F o  If an internal error is detected in the data transfer regime, classE    1 recovery restarts the data transfer regime by retransmitting thedC    file data beginning at the negotiated checkpoint within the dataa    transfer regime.d  F o  Class 2 error recovery provides for the re-establishment of the se-C    lect and open regimes, and also allows for the retransmission of H    file data beginning at a negotiated checkpoint within the data trans-    fer regime.  "                                 32 a  i  C o  Class 3 error recovery provides full recovery by re-establishingmC    a lost FTAM association and its select and open regimes. Class 3eD    recovery then restarts the data transfer regime by retransmittingG    the file data beginning at the negotiated checkpoint within the datar    transfer regime.n  H All restart and recovery operations and procedures are completely trans- parent to the user.t                                                                "                                 33 e  e  * Management and Problem Determination Tools  E FTAM software supplies a number of management tools, including an in-gF stallation verification procedure (IVP), a tracing utility, event log-+ ging, and informational and error messages.e  . FTAM Installation Verification Procedure (IVP)  C The FTAM IVP sets up outbound and inbound application associations.aC A connection is made to your local system (as a loopback test). The D FTAM IVP checks that your installation is able to set up and releaseC presentation and session connections. It tests the FTAM software bybF starting a responder and reading the attributes of a file with the DI- RECTORY command.   FTAM Tracing Utility  C The FTAM tracing utility (OSITRACE) is a tool for identifying prob- C lems in protocol exchanges between your local system and any remote F FTAM system. The tracing utility captures protocol exchanges and tran-K scribes them into easily read text; OSITRACE data is written to SYS$OUTPUT.a  C The FTAM tracing utility monitors data exchanges for individual as-lC sociations. The tracing utility can trace data originating from therC following components: FTAM (DATA, PROTOCOL, and STRUCTURING), ACSE,i Presentation, and Session.   OSI Address Lookup Using X.500  E The FTAM software is capable of retrieving network addresses from theeF X.500 directory. You can use this functionality with or instead of re-+ trieving addresses from a local repository.s   FTAM Event Logging  K For event logging, the FTAM responder writes records to OSIF$RESPONDER.LOG.s        "                                 34 a  t  ( Requirements for Compatibility with FTAM  E FTAM lets an open system perform a specific set of file transfer, ac-tE cess, and management activities with any open system having a compat-  ible FTAM implementation.o  F The Protocol Implementation Conformance Statement (PICS) provides more/ information about Compaq's FTAM implementation.                                                                 "                                 35 o      Appendix B: Virtual Terminal  F DECnet-Plus Virtual Terminal (VT) is Compaq Computer Corporation's im-D plementation of the ISO Virtual Terminal Basic Class standard, whichC consists of the service definition (ISO 9040) and the protocol (ISOfD 9041). VT software adheres to these standards, thereby providing in-G teractive access between DECnet-Plus systems and other multivendor ter- G minal systems and host systems that also adhere to the ISO Virtual Ter-s minal Basic Class standard.i  D VT is implemented as an Application Service Element (ASE) of the OSI Application layer.  D VT can run over Transport layer classes 0, 2 or 4 over CONS, and TP4? over CLNS. VT can also run over TCP/IP networks using RFC 1006.o  D VT provides terminal/initiator (for a local user) and host/responderI (for the remote user) capabilities. Terminal/responder and host/initiatore are not supported.   Supported Standardst  + VT conforms to the following OSI standards:a  5    ISO 9041 - Virtual Terminal protocol - basic class     ISO 8650 - ACSE protocole#    ISO 8823 - Presentation protocol     ISO 8327 - Session protocol   Virtual Terminal Featurese  1 Virtual Terminal supports the following features:E  4 o  Basic class (character cell terminals) of service  * o  Asynchronous mode (A-Mode) of operation   o  Profile Support  #    -  Default A-mode (per ISO 9040)s  B    -  A-mode Generalized Telnet (adheres to OIW Stable Agreements)  ;    -  A-mode Transparent (adheres to OIW Stable Agreements)   "                                 36 s  Q  ;    -  A-mode Telnet 1988 (adheres to OIW Stable Agreements)A   o  Functional Units       -  destructiveBreak      -  structuredCOs4      -  urgentData   o  Supported GatewaysP      -  Bidirectional VT/Telnetn      -  Bidirectional VT/LAT   o  Online Help   OSI Address Lookup using X.500  C The VT software is capable of retrieving network addresses from the2F X.500 directory. You can use this functionality with or instead of re-+ trieving addresses from a local repository.e   Command Mode  E Command mode allows you to execute commands that can modify the char-wC acteristics of the Virtual Terminal association with the remote ap-a
 plication.  
 Trace Utilitye  D The VT tracing utility (OSITRACE) is a tool for identifying problemsC in protocol exchanges between your local system and any remote sys-rF tem. The utility captures protocol exchanges and transcribes them into easily read text..  C The tracing utility monitors data exchanges for individual associa-VE tions. The utility can trace data originating from the VT, ACSE, Pre-e" sentation, and Session components.  "                                 37 o  e  2 Appendix C: OSI Application Programming Interfaces   FTAM API  E The FTAM API supports the OSI standard ISO 8571: Information Process-fE ing Systems, Open Systems Interconnection, and File Transfer, Access,p and Management.o  E The FTAM API provides the interface to the FTAM protocol machine pro- E vided in DECnet-Plus. Communications between the application code and-I the FTAM protocol machine are carried out using ASN.1 encoded data struc- 0 tures. The API supports the following functions:      Abort    Begin-Group	    Cancels    Change-Attributes	    CreateE    Close    Datag    Data-End 	    Deletee    Deselect     End-Group
    Initializet    Openr    Read-Attributes    Readi	    SelectK    Terminate    Transfer-Endl    Write  ! OSI Application Kernel (OSAK) APIn  D The OSAK API provides a direct interface to servcies at the ACSE andE Presentation layer. The OSAK API supports the following OSI standardsa for the ACSE layer:i    "                                 38 F  t  C o  ISO 8650: Information Processing Systems, Open Systems Intercon-eC    nection, Protocol Specification for the Association Control Ser-e    vice Elementt  C o  ISO 8649: Information Processing Systems, Open Systems Intercon- F    nection, Service Definition for the Association Control Service El-    ement  E The OSAK API provides the interface to the ACSE services. It providesr the following services:p      Associate
    Release    Abort    Redirecta  C The redirect service is not an ACSE service. The service allows ap-oD plications to redirect an incoming association to another process on the local system.o  F The OSAK API also includes support for the OSI Presentation layer with( support for the following OSI standards:  C o  ISO 8823: Information Processing Systems, Open Systems Intercon-tC    nection, Connection-Oriented Presentation Protocol Specification   C o  ISO 8822: Information Processing Systems, Open Systems Intercon-i?    nection, Connection-Oriented Presentation Service Definitiono  C o  ISO 8327: Information Processing Systems, Open Systems Intercon-oD    nection, Basic Connection-Oriented Session Protocol Specification  C o  ISO 8326: Information Processing Systems, Open Systems Intercon-r@    nection, Basic Connection-Oriented Session Service Definition  > The Presentation layer services supported by the OSAK API are:      Alter-Context    Datad    Capability-Data    Expedited-Datau
    Typed-Datat  "                                 39 P  ,      Token-Pleasep
    Token-Give     Control-Give 
    Sync-Majori
    Sync-Minora    Resynchronize    Exception-Reportm    Activity-Start     Activity-Interrupt     Activity-Resume    Activity-Discardo    Activity-Endi  G The OSAK API also supports (by pass through) the OSI Session layer ser-r vices.   Session Layer API   D The Session layer API, called the OSAK Session Programming Interface, (SPI), supports the following OSI standards:  C o  ISO 8327: Information Processing Systems, Open Systems Intercon-iD    nection, Basic Connection Oriented Session Protocol Specification  C o  ISO 8326: Information Processing Systems, Open Systems Intercon-eA    nection, Basic Connection Oriented Session Service Definition.n  D The Session layer supports ISO Session version 1 and version 2. Ses-F sion version 1 allows up to 512 octets of user data on a service. Ses-D sion version 2 supports the restrictions imposed by the National In-C stitute of Standards and Technology allowing up to 10,240 octets ofe data on a service.  F Compaq DECnet-Plus for OpenVMS Version 7.3 includes Version 3.0 of theE OSAK SPI. Users of the OSAK SPI Version 1.1 should upgrade to Versione 3.0.  D The OSAK API provides the interface to the following connect and re- lease services:f  
    Connect  "                                 40 i  o  
    Release    Abort    Redirecth  E The redirect service is not a Session service. The service allows ap- C plications to redirect an incoming connection to another process ons the local system.   9 The Session layer services supported by the OSAK API are:c      DataO    Capability-Data    Expedited-Data 
    Typed-Datao    Token-Please8
    Token-Giver    Control-Give 
    Sync-Majorp
    Sync-Minort    Resynchronize    Exception-Report     Activity-Startl    Activity-Interrupt.    Activity-Resume    Activity-Discard     Activity-End_                            "                                 41 l  :   ROSE API  C The Remote Operations Service Element (ROSE) supports the OSI stan-nF dard ISO 9072: Information Processing Systems, Text Communication, and Remote Operations.  D ROSE supports interactive applications in a distributed open systemsD environment. It is a service for multivendor distributed processing.  D The ROSE functionality provides a mechanism that allows for encodingC and decoding the remote operations protocol control information, as 0 defined in ISO 9072, for the following services:  	    Invoke 	    Resultr    Error	    Rejecta  H The information in this document is valid at the time of release. PleaseE contact your local Compaq office for the most up-to-date information.F  "  2001 Compaq Computer Corporation  F COMPAQ and the Compaq logo Registered in U.S. Patent and Trademark Of-C fice. DECnet and OpenVMS are trademarks of Compaq Information Tech-L nologies Group, L.P.  D All other product names mentioned herein may be trademarks or regis-/ tered trademarks of their respective companies.I  F Confidential computer software. Valid license from Compaq required forC possession, use, or copying. Consistent with FAR 12.211 and 12.212,-H Commercial Computer Software, Computer Software Documentation, and Tech-C nical Data for Commercial Items are licensed to the U.S. Government_+ under vendor's standard commercial license.r  E Compaq shall not be liable for technical or editorial errors or omis-eC sions contained herein. The information in this document is subjectT to change without notice.   "                                 42 n  h                                                                                  "                                 43