      Software Product  Description   C ___________________________________________________________________   D PRODUCT NAME:   HP DECnet-Plus for OpenVMS Integrity servers Version8                 8.4                                     E                 and OpenVMS Alpha Version 8.4            SPD 50.45.21    Description   F HP DECnet-Plus for OpenVMS is an implementation of Phase V of the DIG-C ITAL Network Architecture (DNA) for the OpenVMS Alpha and Integrity  servers operating system.   G HP DECnet-Plus integrates DECnet and Open Systems Interconnection (OSI) C network protocols, allowing both stacks to share integrated network G functions up to the Transport layer. Upper layers have been implemented D as separate towers, allowing existing DECnet and OSI applications toF share the integrated Transport layer. Existing DECnet Phase IV and newC DECnet and OSI applications are supported by DECnet-Plus. In combi- C nation with TCP/IP protocol stacks, OpenVMS systems can participate H in multivendor, multiprotocol networks adhering to open networking stan- dards.  , HP DECnet-Plus for OpenVMS features include:  G o  Support for OpenVMS LAN failover sets. LAN failover provides a mech- C    anism to protect LAN applications against network interface card C    (NIC) failures. A LAN failover set is defined by the system man- C    ager and consists of a set of like adapters (all the same class) E    that support LAN failover. One adapter in the failover set is used F    for LAN traffic; one or more other adapters in the set remain idle.C    If the active adapter fails, one of the idle adapters in the set E    automatically takes over LAN traffic using the same address as the     failed adapter.  D o  DECdns Server on Integrity server systems, Alpha systems, and VAX
    systems  C                                                          March 2010        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- E    ning DECnet Phase IV and OSI protocols and FDDI large packets, and 0    X.25 switched and permanent virtual circuits.  G o  FAST configuration option, which allows quick configuration upgrades     from Phase IV to Phase V.  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 one or more of the following di- D    rectory naming services: Local, DECdns, and/or DNS/BIND (referredE    to as Domain by DECnet-Plus software). These directory naming ser- C    vices can be searched in any order, as determined during config-     uration of the product.  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.   "                                  2       E o  The Network Control Language (NCL). Network management is based on G    DNA CMIP, HP's implementation of the OSI international standard Com- '    mon 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.  * o  Dynamic connections over X.25 networks.  D HP DECnet-Plus for OpenVMS includes OSI implementation in accordance. 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- 7       work (LAN) and wide area network (WAN) , and X.25   E    -  Logical Link Control type 2 (LLC2) for Connection-Oriented Net- "       work Service (CONS) over LAN  "                                  3       E    -  Data Link layer, supporting High-level Data Link Control (HDLC) C       for wide area communications (Alpha only), ISO 8802-3 (Ether- F       net CSMA/CD) and FDDI LANs. HDLC support includes the LAPB (LinkE       Access Protocol Balanced) protocol for X.25 communications. For C       Version 8.2, HDLC is supported only on OpenVMS Alpha systems.   C    -  Physical layer, with CSMA/CD, HDLC (Alpha only), and FDDI de-        vices supported.  C HP 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, Advanced Server/PATHWORKS, DECnet-E Plus implementations on other OpenVMS systems and Tru64 UNIX systems, F as well as systems running TCP/IP transports and on OSI-compliant sys- tems from other vendors.  E OpenVMS programs written in native-mode programming languages can use % DECnet-Plus for OpenVMS capabilities.   D Depending on the system configuration, networks combining HP 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   E HP DECnet-Plus for OpenVMS uses Ethernet and FDDI communications con- / trollers 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-D nectionless service. HP DECnet-Plus also supports Ethernet Version 2" packet formats on CSMA/CD devices.          "                                  4       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- 9 based synchronous communications interfaces (Alpha-only).   H All the synchronous devices support DIGITAL-HDLC (Alpha-only) and LAPB/EC (Alpha-only) and data link protocols. X.25 for OpenVMS Alpha is re- 5 quired to establish host-based wide area connections.   D HP DECnet-Plus for OpenVMS allows a maximum of 32 circuits on a fullF routing node and up to four circuits defined and operational on an endE system. This capability allows a single end system to be connected to D up to four separate LANs or WANs. HP recommends that the circuits be# equal in capacity and connectivity.   F The optional X.25 for OpenVMS software allows HP DECnet-Plus for Open-E VMS systems to connect to PSDNs (packet switching data networks) con- C forming to CCITT Recommendation X.25 (1980 or 1984) and/or ISO 7776 G and 8208, or through an X.25 relay system directly connected to a PSDN, D or through an X.25 connector node (X.25 gateway), or over TCP/IP us-E ing RFC 1613 (XOT). The software allows process-to-process as well as C terminal-to-process communications between Alpha systems and remote * DTE (data terminal equipment) 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, refer to the X.25D for OpenVMS Alpha and Integrity systems Software Product Description (SPD 47.37.xx).   "                                  5       
 Network Layer   ' HP DECnet-Plus for OpenVMS supports the F Connectionless-Mode Network 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.  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   0 HP 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 OSI and DECnet applications to run    over TCP/IP    "                                  6       " 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.  E RFC 1006 is a specification for running OSI applications over TCP/IP. D Operation of the FTAM and Virtual Terminal application over a TCP/IPC network is supported along with other layered OSI applications such  as X.400 and X.500.   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     across linked subnetworks.   2 o  The Connection-Oriented Network Service (CONS).                "                                  7        Upper Layers  F HP DECnet-Plus for OpenVMS software provides the OSI upper layer stackC consisting of Session, Presentation and Application layers. The Ap- D plication layer provides Association Control Service Element (ACSE);H File Transfer, Management, and Access (FTAM); and Virtual Terminal (VT).  C HP DECnet-Plus for OpenVMS also provides a range of DECnet applica- D tions and services including file and record access, remote terminal access, mail, and phone.   Applications  " Transport Options for Applications  D You can run applications written to the DECnet upper layers over NSPE or TCP/IP transports using RFC 1859. This includes the network appli- F cations that are licensed with DECnet-Plus as well as user-written ap-G plications that adhere to the documented DECnet programming interfaces.   D You can run applications written to the OSI upper layers over OSI or! TCP/IP transports using RFC 1006.   C Existing DECnet and OSI applications require no modification to run ( over TCP/IP using RFC 1859 and RFC 1006.   Remote File Transfer  E HP DECnet-Plus for OpenVMS supports two upper layer protocols for re- F mote file transfer: the OSI protocol's File Transfer, Access, and Man-9 agement (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.   "                                  8        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.  F HP 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.  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.   E Using HP DECnet-Plus for OpenVMS, an OpenVMS program written in a na- D tive mode programming language can exchange messages with other user	 programs.     "                                  9       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 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 nodes E that support compatible file structures and record formats. Users can I 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.         "                                 10       C The SUBMIT/REMOTE command allows command files residing on a remote G node to be submitted for execution at the remote node. The command file E must be in the format expected by the node responsible for execution. C DECnet-Plus for OpenVMS allows OpenVMS command files to be received   from other systems and executed.  C The DCL command EXCHANGE/NETWORK allows the transfer of files to or I from heterogeneous systems. This command gives users the option to trans- C fer file types between MS-DOS, UNIX systems and OpenVMS systems re- F gardless of record semantics. Unlike the COPY command, which preservesE file and record organization during a file transfer, this command en- F ables the user to modify file and record attributes during file trans- fer.  - OSI Application Programming Interfaces (APIs)   E The OSI application programming interfaces enable users to write dis- E tributed applications that communicate over open networks and use the % OSI services provided by DECnet-Plus.   C The interfaces are provided under the Extended Function license and  include:  ? o  An interface to FTAM (File Transfer, Access, and Management)   C o  Interfaces to the ACSE (Association Control Service Element) and     Presentation layers  ; o  An interface to ROSE (Remote Operations Service Element)   ( 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.   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 B for details on the OSI APIs.   "                                 11        Network Virtual Terminal  C DECnet-Plus supports two upper layer protocols for terminal access: F the OSI Virtual Terminal protocol and the DECnet Command Terminal pro- tocol.                                                                      "                                 12        Virtual Terminal  E Virtual Terminal (VT) supports the ISO Virtual Terminal Protocol (ISO E 9041). This protocol allows remote logins and access to remote appli- C cations between DECnet-Plus for OpenVMS systems and any remote sys- G tem, including multivendor systems, that also run an ISO-compliant Vir-  tual Terminal implementation.   G Virtual Terminal is implemented as an Application Service Element (ASE)  of the OSI Application layer.   E Virtual Terminal may act as the terminal/initiator (for a local user) / or as the host/responder (for the remote user).   G A full description of Virtual Terminal features is provided in Appendix  A of this SPD.   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-Plus C or DECnet Phase IV node that uses the Command Terminal (CTERM) pro- F tocol. This connection makes the terminal appear to be physically con-E nected to the remote system and the operator can use all the standard D system and network utilities supported by that remote node. This ca-D pability is particularly useful for doing remote program developmentE and allows the terminal 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- E velop programs and procedures based on these interfaces for functions F such as file access and task-to-task communications on individual sys-C tems. Because the DECnet-Plus for OpenVMS interfaces stay the same, G you can use the programs and procedures developed on an individual sys- 4 tem in a network environment without modifying them.          "                                 13        Services   Downline Loading  G HP DECnet-Plus for OpenVMS allows for the loading of an unattended sys- D tem using the services provided by the Maintenance Operations ModuleF (MOM). MOM provides a set of maintenance operations over various typesG of circuits by using the Maintenance Operations Protocol (MOP). A load- C able system is a system that has a load device enabled for MOP ser- C vice 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 HP server products.                                                    "                                 14        Downline Task Loading   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  E Memory images of adjacent nodes connected by HP DECnet-Plus for Open- C VMS 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-B tem crash. This facility is also supported for HP server products.   Mail  E The OpenVMS Mail utility allows transmission of text messages between C users on systems supporting MAIL-11. The HP DECnet-Plus for OpenVMS F software allows users to exchange mail with users of other DECnet-Plus and/or DECnet Phase IV systems.    Phone   C The OpenVMS Phone utility allows users to send and receive data in- H 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.    OpenVMS Cluster Alias   E HP DECnet-Plus for OpenVMS supports the ability to access nodes in an D OpenVMS Cluster using a separate alias node address, while retainingE the ability to address each node in the cluster individually. Not all F network objects can be accessed using this mechanism. The maximum num-D ber of nodes supported for a cluster alias is 92. Refer to the Open-5 VMS Cluster SPD (29.78.xx) for relevant restrictions.     "                                 15       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). E Network management implements the DECnet-Plus layered model, based on D the HP hierarchical structure called Enterprise Management Architec- ture (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- , ponents from a Motif-based window interface.  F The HP DECnet-Plus for OpenVMS network management software allows sys- tem and network managers to:  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, F 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- 7 work manager to perform the operations described above.   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. The G messages can then be compared for possible errors. NCL helps users iso-  late network problems.  "                                 16       C HP 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), which H permits entity management from a single location anywhere in the DECnet-
 Plus network.   E The Common Trace Facility (CTF) allows the network manager to collect F and display information about specific protocol exchanges between sys- tems.   E HP DECnet-Plus for OpenVMS supports an ISO CMISE application program- G ming interface (API) conforming to the service definitions in ISO 9595. C The API allows for development of applications that can communicate C with other management applications conforming to ISO 9595 on remote  nodes in the network.   D DECnet-Plus supports the NCP Emulator for remote management of Phase IV DECnet systems.                                      "                                 17        Name Service Options  D HP DECnet-Plus for OpenVMS allows the use of one or more naming ser-F vices. The available services are DECdns, DNS/BIND (referred to as Do-C main by DECnet-Plus software), and the Local namespace. TCP/IP host C name and address information is maintained in DNS/BIND. DECnet node I names and address towers are maintained in the DECdns and/or Local names- H paces. If DECnet over TCP/IP is in use by the DECdns clerks and servers,H then the IP towers will be automatically maintained in the DECdns names-
 pace as well.   C When you use more than one name service, a configurable search list D 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 Phase@ IV database to the large local file format and/or DECdns format.   DNS/BIND  I DECnet can use TCP/IP naming and addressing information from the DNS/BIND 
 name service.    DECdns  F HP DECnet-Plus for OpenVMS provides a global naming service called 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- F tained by one or more DECdns server systems. HP recommends that DECdnsF servers be installed on at least two systems in every LAN. This should( provide adequate service and redundancy.  ( The features provided by DECdns include:  G o  A networkwide name-to-attribute mapping service that allows selected C    HP applications to create, read, modify, and delete names in the     namespace  "                                 18       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 namespace    o  Management and event logging                                                                     "                                 19        Distributed Time Service  G HP DECnet-Plus for OpenVMS provides a network time service with DECdts, E the DIGITAL Distributed Time Service. DECdts provides precise, fault- C tolerant clock synchronization for systems in a LAN or WAN. Time is C provided in Coordinated Universal Time (UTC) and can be used across D a global network. Several forms of time providers are supported, andC a callable interface for applications allows users to add their own D time providers, including NTP. DECdts can be used by distributed ap-C plications to determine event sequencing, duration, and scheduling.    Secure Shell  C HP DECnet-Plus for OpenVMS now supports Secure Shell (SSH) and uses E the port forwarding feature of SSH. This enables you to transmit DEC- D net/IP data over a secure channel, thus providing data security. TheF DECnet transmitter side requires modification to support this feature;6 however the receiver side does not require any change.  E This feature can be used either Process wide or System wide by defin- 8 ing the logical with the /PROCESS or /SYSTEM qualifiers.  	 Operation   E DECnet-Plus is implemented under OpenVMS as an ancillary control pro- G cess (ACP) and a network device driver with HP-supplied executive-level # components and user-level programs.   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- E gin and file protection mechanisms. Outgoing connects, including file C access and file transfer requests, can include user password infor- C mation that is implicitly specified by NCL, or explicitly specified 0 by the user for verification on the remote node.          "                                 20        Configuration and Performance   E You can configure DECnet-Plus using either the BASIC or ADVANCED con-  figuration options.   @ 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- E cessing specific to that node. Thus, node performance depends on many  factors including:   o  CPU types   o  Number and type of devices   , o  Number of device interrupts per unit time  ) o  Communications line(s) characteristics    o  Number and size of buffers   - 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- G 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.   G The performance of DECnet-Plus is comparable to the performance of DEC- C net Phase IV. However, in a symmetrical multiprocessing environment D the performance of DECnet-Plus can be far superior to that of DECnetE Phase IV. With DECnet Phase IV the NETACP process can only execute on C the primary CPU. With DECnet-Plus the NET$ACP process can be sched- = uled on any available CPU, resulting in improved performance.   "                                 21        Standards Conformance   D HP DECnet-Plus for OpenVMS has been designed and implemented to con-  form 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 orJ    LAPBE variants of the X.25 packet level and data link protocols (Alpha-    only)   o  U.S. GOSIP V2.0   o  U.K. GOSIP V4.0  E Contact your local HP office for the most recent conformance certifi-  cates.  
 Documentation   D The documentation for HP DECnet-Plus for OpenVMS is supplied as fol- lows:   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-     ered product CD-ROM.   F o  Printed copies of the documentation are available as a separate or-    der.   "                                 22       D o  An optional X.25 documentation set covering accounting, X.29, and.    X.25 Mail is available as a separate order.  @ o  New features are documented extensively in the Release Notes.   Installation  C DECnet-Plus software is customer installable. Installation services D are available for customers who request installation of the software1 product by an experienced HP software specialist.   D HP requires that a customer's first use of X.25 include HP Installa-C tion Services. These services provide for installation of the soft- 6 ware product by an experienced HP software specialist.   Customer Responsibilities   ? Before HP Services can install the software, the customer must:   E o  Ensure that the system meets the minimum hardware and software re- 1    quirements (as specified in the relevant SPDs)   D o  Prior to installing HP hardware or software, obtain, install, andE    demonstrate as operational any modems and other necessary customer C    equipment or facilities to which HP's communications hardware 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 agreed C    upon by HP and the customer, all hardware communications facili- >    ties and terminals that are to be used during installation.  C Delays caused by any failure to meet these responsibilities will be 6 charged at the prevailing rate for time and materials.  D Installation of HP DECnet-Plus for OpenVMS consists of the following tasks:  E o  Verify that all components of HP DECnet-Plus for OpenVMS have been     received.  "                                 23       F o  Verify that the necessary versions of the OpenVMS software and doc-    umentation are available.  , 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 HP DECnet-Plus for OpenVMS accounts and di- 
    rectories.   C o  Enable software by registering the License Product Authorization     Key (PAK) .  E o  Install the HP DECnet-Plus software on the target system using the -    POLYCENTER Software Installation utility .   G o  Verify the proper installation of HP DECnet-Plus for OpenVMS by run- D    ning a series of tests to show connectivity to a designated node.  C Connectivity to all other nodes within the network is the responsi- C bility of the customer. HP recommends the use of NCL to help verify 
 connectivity.   G In some cases, the PSDN supplier (or PTT) may impose restrictions, lim- C itations, or requirements on the proposed HP network configuration. C The customer must understand and adhere to these controls for every  network.   Hardware Requirements   F Refer to the HP OpenVMS for Integrity Servers and HP OpenVMS Alpha Op-E erating Systems Software Product Description (SPD 82.35.xx) for hard- ( ware requirements and processor support.  0 Disk Space Requirements (Block Cluster Size = 1)  C The following counts refer to the disk space required on the system C disk. The sizes are approximate; actual sizes may vary depending on C the user's system environment, configuration, and software options.   "                                 24       % Disk space required for installation:   + -  Base DECnet-Plus software: 89,000 blocks   C -  Base DECnet-Plus software with optional DECdns server and DECdts +    server software included: 104,000 blocks    Supported LAN Adapters  F Refer to the HP OpenVMS for Integrity Servers and HP OpenVMS Alpha Op-F erating Systems Software Product Description (SPD 82.35.xx) for a list of supported LAN adapters.   Software Requirements   G HP DECnet-Plus for OpenVMS Integrity servers Version 8.4 requires Open- E VMS Version 8.4 and Alpha Version 8.4 requires OpenVMS Version 8.4 of  the operating system.    Optional Software    TCP/IP  C A separate TCP/IP protocol stack is required to use the DECnet over E TCP/IP features in DECnet-Plus. This release contains support for In- C ternet Protocol Version 4 (IPv4) and does not support Internet Pro- D tocol Version 6 (IPv6). The following TCP/IP product has been tested with DECnet-Plus:   + HP TCP/IP Services for OpenVMS Version 5.7. . HP TCP/IP Client Software License: QL-0M2A*-**0 HP TCP/IP Services Software License: QL-0LXA*-**- HP TCP/IP Client Upgrade License: QL-0PHA*-** 
 SPD: 46.46.xx    X.25 Optional License         "                                 25       C The DECnet-Plus for OpenVMS license grants the right to use the OSI C applications for CONS over LLC2 or CLNS over DEC-HDLC (Alpha-only). C All other X.25 software functions over LAPB (Alpha-only), LLC2, and . RFC 1613 require the X.25 for OpenVMS license.  F The X.25 for OpenVMS license is also required to enable the X.25 util-C ities, such as X.25 Mail and SET HOST/X.25, as well as the X.25 ap- D plication programming interfaces (APIs). Version 2.0 of the X.25 for< OpenVMS product is required for this version of DECnet-Plus.   Software Licenses:  $    Alpha                 QL-0THA*-AA       Integrity Servers     BA390AC   Media and Documenta- tion:   $    Alpha                 QA-03XAA-H8       Integrity Servers     BA390AA      (See SPD 
 47.37.xx.)   Growth Considerations   D The minimum hardware/software requirements for any future version ofC this product may be different from the requirements for the current  version.   Distribution Media  C This product is available as part of the OpenVMS Consolidated Soft- F ware Distribution on CD-ROM. The software documentation for this prod-E uct is also available as part of the OpenVMS Online Documentation Li-  brary on CD-ROM.    "                                 26        Ordering Information  D In the following table, asterisks (*) denote variant fields. For ad-C ditional information on available licenses, services, and media re- " fer to the appropriate price book.   Software Licenses:  $    Alpha End System      QL-MTFA*-AA  /    Integrity Servers     Included in OE license 
 End System  $    Alpha Extended        QL-MTGA*-AA Function       Integrity Servers     BA406AC Extended Function    Software Media:   $    Alpha                 QA-03XAA-H8       Integrity Servers     BA322AA                           BA323AA   Consolidated Distri- bution Services:  $    Alpha                 QT-03XAA-*8  9    Integrity Servers     Included in OE service offerings    Software Licensing  E The DECnet-Plus licenses give users the right to use the software and E includes the delivery of a License Product Authorization Key (PAK) to H enable the DECnet-Plus for OpenVMS software. On OpenVMS Integrity serverE systems, the DECnet for OpenVMS license is part of Base Operating En- ? vironment (BOE), which is licensed on a per core license basis.   G The End System license grants the right to use all the DECnet-Plus fea- G tures with the exception of the OSI application programming interfaces, * the OSI applications gateway, and routing.  "                                 27       E The Extended Function license grants the right to use the DECnet-Plus C end-system features, OSI application gateways, OSI application pro- , gramming interfaces, and host-based routing.  C DECnet-Plus Cluster Alias no longer requires a cluster member to be F configured as a router and hence the extended function license is alsoD not required to be present on the cluster. However it is required to3 have a reachable IS-IS compliant router on the LAN.   E The Extended Function License is also required to configure a node as  a DECdns server.  E This software is furnished under a license only. For more information F about HP's licensing terms and policies, contact your local HP office.  # License Management Facility Support   E This product supports the OpenVMS Alpha and Integrity servers 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 the D HP OpenVMS for Integrity Servers and HP OpenVMS Alpha Operating Sys-D tems Software Product Description (SPD 82.35.xx) or the License Man-C agement Facility manual of the OpenVMS Alpha operating system docu-  mentation set.  E For more information about HP's licensing terms and policies, contact  your local HP office.    Software Product Services    Prerequisite Support  C For the use of X.25 with PSDNs, it is recommended that the customer G and HP jointly prepare a Network Profile and Customer Support Plan cov- E ering all the intended network nodes, their usage of switched virtual E circuits (SVCs), permanent virtual circuits (PVCs), and other network   "                                 28       D facilities, and their support. Without this Network Profile and Cus-> tomer Support Plan, HP cannot support the network connections.  C A variety of service options are available from HP. For more infor- % mation, contact your local HP office.    Software Warranty   E This software is provided by HP with a 90 day comformance warranty in D accordance with the HP warranty terms applicable to the license pur- chase.                                                          "                                 29       8 Appendix A: File Transfer, Access, and Management (FTAM)  C FTAM software provides communications for the following file opera-  tions between open systems:   1 o  Copying files between local and remote systems   ) o  Appending, deleting, or renaming files   % o  Displaying information about files   E An open system is a computer system that implements the standards for G each of the seven layers of the Open Systems Interconnection (OSI) Ref- C erence Model for communications as defined by the International Or- F ganization for Standardization. An FTAM system is any open system con-E taining an FTAM implementation that conforms to the FTAM standard and F 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.    Supported Standards   - FTAM conforms to the following OSI standards:   D 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  D Table 1 compares the supported implementation profiles for different6 standards bodies and their relationship to each other.    "                                 30       C ___________________________________________________________________   C Table_1:_Standards_and_Implementation______________________________   
 International  Standardized Profiles (ISP)C 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      iENV 41 204  File Trans-       File fer Service       Transfer (Unstructured)  % Part 4: AFT12     T2 - Po-    A/112 - ( (DISP)[1] -       sitional    ENV 41 206 Positional        File File Trans-       Transfer fer Service 	 (Flat)[2]   C ___________________________________________________________________  [1]Draft ISP( [2]AFT12 is not supported by DECnet-Plus  "                                 31         C ___________________________________________________________________   
 International  Standardized Profiles (ISP)C ISO_10607_________NIST________CEN/CENELEC_and_EWOS_________________   $ Part 5: AFT3      M1 -        A/13 -( (DISP)[1] -       Manage-     ENV 41 205 File Manage-      mentC ment_Service_______________________________________________________  [1]Draft ISPC ___________________________________________________________________    FTAM Component Software   E The component software includes the user facilities (initiators), re- < sponders, management tools, and problem determination tools.   FTAM User Facilities  E Users access the FTAM user facilities by entering the following Open- C VMS operating system commands: APPEND, COPY, DIRECTORY, RENAME, and G DELETE. These commands operate on files stored on any FTAM system whose C implementations are compatible with FTAM. You cannot use these com- 8 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 a F 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- " modates non-RMS file designations.        "                                 32        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 FTAM-1 files are unstructured text files, FTAM-2 files are sequential C 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 document  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             ter #                       GeneralString   7           Fixed       VisibleStrinPresence of parameter   #                       GraphicString   A           Variable    VisibleStrinPresence and absence of parame- %                                   ter #                       GraphicString   B FTAM-2    Not         VisibleStrinPresence or absence of parameter           significant #                       GraphicString   B FTAM-3    Not                     Presence or absence of parameter           significant   C __________Fixed___________________Presence_of_parameter____________   % NBS-9 files are NBS file directories.   "                                 33       / Flexible and Transparent Access for Local Files   D FTAM software treats local files the same way that the OpenVMS oper-% ating system file system treats them.    File Transfers  E The FTAM COPY command transfers files between compatible FTAM systems E without modifying the source file. The facility can transfer files in C either direction between the local system and a remote FTAM system. E The COPY command can also transfer files between two remote FTAM sys-  tems for a local FTAM user.   F The COPY command also allows you to append one or more files to a sin-/ gle output file within or between FTAM systems.    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. D 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.                                   "                                 34       
 File Deletion   E The FTAM DELETE command lets you delete one or more files on any com- G bination of FTAM systems provided you have delete access to those files  on the specific FTAM system.   Renaming Requests   E The FTAM RENAME command allows you to rename files. The command works F 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. C For remote files, you must specify whatever type of information the 1 remote FTAM system requires for specifying files.    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.    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- ? vided for classes 1, 2, and 3 errors as detailed in ISO 8571-4.   D Class 1 file error recovery provides only the restart functionality,E while classes 2 and 3 provide both the restart and recovery function-  ality as follows:   F o  If an internal error is detected in the data transfer regime, classE    1 recovery restarts the data transfer regime by retransmitting the C    file data beginning at the negotiated checkpoint within the data     transfer regime.   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.  "                                 35       C o  Class 3 error recovery provides full recovery by re-establishing C    a lost FTAM association and its select and open regimes. Class 3 D    recovery then restarts the data transfer regime by retransmittingG    the file data beginning at the negotiated checkpoint within the data     transfer regime.   H All restart and recovery operations and procedures are completely trans- parent to the user.                                                                 "                                 36       * Management and Problem Determination Tools  E FTAM software supplies a number of management tools, including an in- F stallation verification procedure (IVP), a tracing utility, event log-+ ging, and informational and error messages.   . FTAM Installation Verification Procedure (IVP)  C The FTAM IVP sets up outbound and inbound application associations. C 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 by F 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.   C The FTAM tracing utility monitors data exchanges for individual as- C sociations. The tracing utility can trace data originating from the C following components: FTAM (DATA, PROTOCOL, and STRUCTURING), ACSE,  Presentation, and Session.   OSI Address Lookup Using X.500  E The FTAM software is capable of retrieving network addresses from the F X.500 directory. You can use this functionality with or instead of re-+ trieving addresses from a local repository.    FTAM Event Logging  K For event logging, the FTAM responder writes records to OSIF$RESPONDER.LOG.         "                                 37       ( Requirements for Compatibility with FTAM  E FTAM lets an open system perform a specific set of file transfer, ac- E cess, and management activities with any open system having a compat-  ible FTAM implementation.   F The Protocol Implementation Conformance Statement (PICS) provides more+ information about HP's FTAM implementation.                                                                 "                                 38        Appendix B: Virtual Terminal  E DECnet-Plus Virtual Terminal (VT) is Hewlett Packard Company's imple- F mentation of the ISO Virtual Terminal Basic Class standard, which con-G sists of the service definition (ISO 9040) and the protocol (ISO 9041). E VT software adheres to these standards, thereby providing interactive F access between DECnet-Plus systems and other multivendor terminal sys-F tems and host systems that also adhere to the ISO Virtual Terminal Ba- sic Class standard.   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.   D VT provides terminal/initiator (for a local user) and host/responderI (for the remote user) capabilities. Terminal/responder and host/initiator  are not supported.   Supported Standards   + VT conforms to the following OSI standards:   5    ISO 9041 - Virtual Terminal protocol - basic class     ISO 8650 - ACSE protocol #    ISO 8823 - Presentation protocol     ISO 8327 - Session protocol   Virtual Terminal Features   1 Virtual Terminal supports the following features:   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)   B    -  A-mode Generalized Telnet (adheres to OIW Stable Agreements)  ;    -  A-mode Transparent (adheres to OIW Stable Agreements)   "                                 39       ;    -  A-mode Telnet 1988 (adheres to OIW Stable Agreements)    o  Functional Units       -  destructiveBreak      -  structuredCOs       -  urgentData   o  Supported Gateways       -  Bidirectional VT/Telnet       -  Bidirectional VT/LAT   o  Online Help   OSI Address Lookup using X.500  C The VT software is capable of retrieving network addresses from the F X.500 directory. You can use this functionality with or instead of re-+ trieving addresses from a local repository.    Command Mode  E Command mode allows you to execute commands that can modify the char- C acteristics of the Virtual Terminal association with the remote ap- 
 plication.  
 Trace Utility   D The VT tracing utility (OSITRACE) is a tool for identifying problemsC in protocol exchanges between your local system and any remote sys- F tem. The utility captures protocol exchanges and transcribes them into easily read text.   C The tracing utility monitors data exchanges for individual associa- E tions. The utility can trace data originating from the VT, ACSE, Pre- " sentation, and Session components.  "                                 40       2 Appendix C: OSI Application Programming Interfaces   FTAM API  E The FTAM API supports the OSI standard ISO 8571: Information Process- E ing Systems, Open Systems Interconnection, and File Transfer, Access,  and Management.   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	    Cancel     Change-Attributes	    Create     Close    Data     Data-End 	    Delete     Deselect     End-Group
    Initialize     Open     Read-Attributes    Read 	    Select     Terminate    Transfer-End     Write  ! OSI Application Kernel (OSAK) API   D The OSAK API provides a direct interface to services at the ACSE andE Presentation layer. The OSAK API supports the following OSI standards  for the ACSE layer:     "                                 41       C o  ISO 8650: Information Processing Systems, Open Systems Intercon- C    nection, Protocol Specification for the Association Control Ser-     vice Element   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 provides  the following services:       Associate
    Release    Abort    Redirect   C The redirect service is not an ACSE service. The service allows ap- D plications to redirect an incoming association to another process on the local system.   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- C    nection, Connection-Oriented Presentation Protocol Specification   C o  ISO 8822: Information Processing Systems, Open Systems Intercon- ?    nection, Connection-Oriented Presentation Service Definition   C o  ISO 8327: Information Processing Systems, Open Systems Intercon- D    nection, Basic Connection-Oriented Session Protocol Specification  C o  ISO 8326: Information Processing Systems, Open Systems Intercon- @    nection, Basic Connection-Oriented Session Service Definition  > The Presentation layer services supported by the OSAK API are:      Alter-Context    Data     Capability-Data    Expedited-Data 
    Typed-Data   "                                 42           Token-Please 
    Token-Give     Control-Give 
    Sync-Major 
    Sync-Minor     Resynchronize    Exception-Report     Activity-Start     Activity-Interrupt     Activity-Resume    Activity-Discard     Activity-End   G The OSAK API also supports (by pass through) the OSI Session layer ser-  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- D    nection, Basic Connection Oriented Session Protocol Specification  C o  ISO 8326: Information Processing Systems, Open Systems Intercon- A    nection, Basic Connection Oriented Session Service Definition.   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 of  data on a service.  G HP DECnet-Plus for OpenVMS Version 7.3 includes Version 3.0 of the OSAK E SPI. Users of the OSAK SPI Version 1.1 should upgrade to Version 3.0.   D The OSAK API provides the interface to the following connect and re- lease services:   
    Connect
    Release  "                                 43           Abort    Redirect   E The redirect service is not a Session service. The service allows ap- C plications to redirect an incoming connection to another process on  the local system.   9 The Session layer services supported by the OSAK API are:       Data     Capability-Data    Expedited-Data 
    Typed-Data     Token-Please 
    Token-Give     Control-Give 
    Sync-Major 
    Sync-Minor     Resynchronize    Exception-Report     Activity-Start     Activity-Interrupt     Activity-Resume    Activity-Discard     Activity-End    ROSE API  C The Remote Operations Service Element (ROSE) supports the OSI stan- F 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   "                                 44       	    Result     Error	    Reject   H The information in this document is valid at the time of release. PleaseA contact your local HP office for the most up-to-date information.   :  Copyright 2010 Hewlett-Packard Development Company, L.P.  G Confidential computer software. Valid license from HP required for pos- D session, use or copying. Consistent with FAR 12.211 and 12.212, Com-E mercial 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.   E The information contained herein is subject to change without notice. E The only warranties for HP products and services are set forth in the D express warranty statements accompanying such products and services.E Nothing herein should be construed as constituting an additional war- H ranty. HP shall not be liable for technical or editorial errors or omis- sions contained herein.                                       "                                 45                                                                                       "                                 46