      Software Product  Description   C ___________________________________________________________________   C PRODUCT NAME:  Compaq DECnet-Plus Version 7.3 for OpenVMS VAX   SPD  25.03.45   Description   F Compaq DECnet-Plus Version 7.3 for OpenVMS VAX (formerly known as DEC-C net/OSI) is an implementation of Phase V of the DIGITAL Network Ar- 6 chitecture (DNA) for the OpenVMS VAX 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.   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 o  X.25 network management interface, providing efficient wide area     network (WAN) management.  C                                                          April 2001   C                                                         AE-NJ32U-TE        C o  The ability to configure all members of a cluster from any clus-     ter member.  C o  The ability to generate an OpenVMS audit event when a connection     is established.  1 o  OSI application programming interfaces (APIs).   E o  Expanded naming options, allowing the use of a larger Local names- 4    pace, DECdns, and/or DNS/BIND as naming services.  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.  * 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:  "                                  2       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 D       FDDI LANs, and DDCMP for backwards compatibility. HDLC supportD       includes the LAPB (Link Access Protocol 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.  E OpenVMS programs written in native-mode programming languages can use % DECnet-Plus for OpenVMS capabilities.   "                                  3       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   G Compaq DECnet-Plus for OpenVMS uses synchronous, Ethernet and FDDI com- > munications 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-F nectionless service and ISO 8802-3 LLC Type 2. Compaq DECnet-Plus also> supports Ethernet Version 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 Supported synchronous devices allow for the use of DDCMP, DIGITAL HDLC, E LAPB/E and SDLC protocols. BISYNC and GENBYTE protocols are also sup- F ported on some options. WAN device drivers are required by X.25 to es-) tablish host-based wide area connections.   D Synchronous controllers use DDCMP or HDLC, when connected either di-D rectly or through modems, to provide full- or half-duplex communica-C tions over point-to-point lines. Synchronous DDCMP multipoint trib- F utary connections are also supported. Asynchronous controllers use DD-F CMP, when connected either directly or through modems, to provide onlyD full duplex communications over point-to-point lines. Error correct-2 ing and data suppression modems are not supported.  F Asynchronous lines are supported only to other systems running DECnet-= Plus for OpenVMS VAX, DECnet-VAX, DECnet-RSX, and DECnet-DOS.       "                                  4       E DDCMP operation is not supported in cases where an asynchronous phys- E ical communications line is emulated by lower-level protocols or com- D munications subsystems. Examples of this include X.29 Virtual Termi-C nals, asynchronous connections as emulated by terminal servers, and " connections through data switches.  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.    X.25  D The Compaq DECnet-Plus for OpenVMS VAX license includes the right toH use X.25 Access software, formerly known as VAX P.S.I. Access. The rightC to use X.25 Native Mode software, formerly known as VAX P.S.I., re- G quires an additional license. See the Optional Software section of this E SPD for ordering information. The X.25 software in Compaq DECnet-Plus F for OpenVMS is backward compatible with systems running the older X.25C Native Mode products. Applications written to the older X.25 inter- G faces will continue to run, unchanged, with the X.25 software supported  on DECnet-Plus.   D The X.25 Native Mode software allows suitably configured DECnet-PlusE systems to connect to PSDNs that conform to CCITT recommendation X.25 E (1980 or 1984) and/or to International Standards (ISO) 7776 and 8208. D This allows a DECnet-Plus system to function as data terminal equip-F ment (DTE) or be addressed as data circuit terminating equipment (DCE) as follows:   C o  A packet-mode DTE connected to a supported PSDN (supported PSDNs H    are listed in Table 4) conforming to CCITT Recommendation X.25 (1980,    1984)  G o  A packet-mode DTE connected to a CSMA/CD LAN conforming to ISO 8802- E    3 using ISO Logical Link Control Type 2 (LLC2) as specified in ISO     8881     "                                  5       F o  A packet-mode DTE/DCE connected to a DCE/DTE conforming to ISO 7776    and 8208   E You can configure X.25 for native operation to support direct connec- D tions from a VAX system to one or more PSDNs, each of which may haveF one or more DTEs. The software also allows communication with any non-E Compaq X.25 system on the same LAN that supports the ISO Logical Link  Control Type 2 (LLC2) protocol.   E Direct access to a PSDN (using the supported device drivers) requires 3 an X.25 license. See the Optional Software section.    X.25 Access Software  C DECnet-Plus logical links are established by OpenVMS to connect the D X.25 Access system to the X.25 Connector system. These links may useE any supported DECnet-Plus communications path between the X.25 Access F system and the Connector system, provided they do not use an X.25 con-C nection. X.25 Access uses these links to transmit X.25 or X.29 mes- > sages between the Connector system and the X.25 Access system.  C Note that successful use of an X.29 connection, either for incoming L X.29 calls or by means of the host-based PAD (packet assembler/disassembler)E utility supplied with X.25 Access, depends on the DECnet-Plus circuit C between the Access and Connector system having a low response time. F This configuration requires high-speed DECnet-Plus connections and few intermediate routing systems.   E A single X.25 Access system can connect to one or more Connector sys- E tems concurrently, and hence access all PSDN(s) accessible from those C Connector systems. When X.25 Access is used, one of these Connector D systems/PSDN combinations must be established as the default gateway! for outbound and inbound traffic.    Features  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.  "                                  6       4 The X.25 software can be used in the following ways:  + o  Process-to-process (X.25) communications   , o  Process-to-terminal (X.29) communications  , o  Terminal-to-process (X.29) communications  ( Process-to-Process (X.25) Communications  C The X.25 software provides access for OpenVMS user programs written C in VAX MACRO and high-level languages such as VAX FORTRAN. The X.25 D software does not support programs executing in PDP-11 compatibility mode.   D The X.25 programming interface allows application programs to accessH the service interface to the packet level by means of the standard Open-D VMS QIO interface. Functions include setting up and breaking networkC connections, data transmission and reception, sending and receiving E interrupt messages, and resetting virtual circuits. The interface al- C lows splitting and recombining of messages that are longer than the % packet size selected for the circuit.   C The X.25 programming interface enables an application program using E OpenVMS system services to communicate with complementary software on E other systems (Compaq or non-Compaq DTEs) accessible through the X.25  connection.   A Process-to-Terminal and Terminal-to-Process (X.29) Communications   E The X.25 software supports terminal communications according to CCITT D recommendations X.3, X.28, and X.29 for outgoing and incoming termi- nal traffic.  G X.25 native users may make outgoing calls to other Compaq or non-Compaq C CPUs, or suitable network PADs accessible through a PSDN, using the F X.29 programming interface or by using the host-based PAD. The PAD fa-9 cility accepts DCL-style commands or CCITT X.28 commands.     "                                  7       G The X.29 interactive terminal interface allows remote asynchronous ter- D minals (character-mode DTEs) connected to the network to communicateC with the X.25 host in a manner similar to local terminals. Dissimi- E larities might appear as a result of delays caused by the PSDN(s) and D the various PAD parameter settings chosen by the user or peculiar toC the PSDN(s). In this case, the remote PAD must convert code between E ASCII and the code the terminal uses. Note that there may be some re- " strictions imposed by the PSDN(s).  C Terminal parameters defined in the X.3 recommendation are supported F explicitly. Network-specific enhancements or extensions to the X.3 pa-E rameters are available at both the X.29 programming interface and the F host-based PAD user interface. Terminal processes that depend on theseD extensions might cause problems when used on other PSDNs or when ac-E cessing one PSDN through another (for example, international access).   E The X.29 terminal interface is compatible with the local terminal in- D terface, except for those facilities where the PSDN does not provideG adequate support. The X.29 interface includes support for specific X.29 
 signaling.  C The host-based PAD employs a DCL-style command syntax, offering the C ability to reference the CCITT PAD parameters symbolically, as well D as an interface that conforms to the standard CCITT command signals.F The host-based PAD also offers the capability of running multiple X.29D sessions using the OpenVMS SPAWN and ATTACH commands. The host-basedE PAD supports reception of reselection messages to allow X.29 calls to  be redirected to another DTE.   D The X.29 programming interface is similar to the X.25 one and allowsG an OpenVMS process to control the virtual circuit (for example, to mod- C ify PAD parameters or clear a call). You can also use the X.29 pro- E gramming interface to make an outgoing call to a remote PAD. The pro- A gramming interface allows generation of PAD reselection messages.   F The maximum number of terminals supported (both local and remote X.29)F must not exceed the number supported by OpenVMS. The use of PVCs (per-C manent virtual circuits) for X.29 connections is not defined by the @ 1980, 1984, and 1988 CCITT Recommendations and is not supported.  "                                  8        Static X.25 Circuits  C X.25 allows the use of DECnet-Plus facilities over static X.25 cir- > cuits. These circuits are called statically assigned circuits.   Virtual Circuits  D X.25 native software supports both permanent virtual circuits (PVCs)E and switched virtual circuits (SVCs). One virtual circuit is used for  each:   0 o  Incoming or outgoing X.29 terminal connection  - o  X.25 connection, using either a SVC or PVC   D X.25 native supports a maximum of 4,096 virtual circuits per system.  B X.25 Access supports a maximum of 900 virtual circuits per system.  E Note that each virtual circuit requires a certain amount of memory so D the number of logical virtual circuits possible on any single system# is limited by the available memory.   
 Configuration   C The X.25 software includes a configuration procedure to configure a E VAX system. This menu-based interface allows network managers to cre- G ate an initialization script to configure entities and their attributes  after initial installation.    X.25 Accounting   D The X.25 Accounting utility enables the system manager to obtain in-F formation PSDN usage. X.25 Accounting can extract the information col-F lected and display the information directly on a terminal or write theC information to a file. It can also extract information for selected_E records, or produce a summary. The X.25 Accounting utility is compat-s) ible with the OpenVMS Accounting utility.   D For incoming X.29 calls, no information about the process/account onE to which a user is logged can be stored. However this information may ; be obtained by correlation with OpenVMS accounting records.s  "                                  9 n  a  
 X.25 Securityn  H X.25 security allows control of both remote DTE access to the X.25 soft-C ware, and access to the PSDN(s) by OpenVMS processes. X.25 securityv* allows for access control on the basis of:  C o  The remote DTE numbers involved, either on the basis of individ- D    ual DTE numbers or groups of DTE numbers with common leading dig-    its.a  C o  The process making the outgoing call or the application handlings    the incoming call.a                                                        "                                 10    o  	 X.25 Maill  C The X.25 Mail utility allows communications through electronic mailIE between two OpenVMS systems running the X.25 software in native or inrC access mode. Refer to the OpenVMS Operating System SPD 25.01.xx fore$ more information about OpenVMS Mail.  " Synchronous Communications Devices  E The X.25 Native Mode software supports the synchronous communicationssF devices listed in the Communications Devices section, Table 2. The de-C vices are different in many respects, particularly in the amount oftE CPU used. For optimum performance, Compaq recommends the use of a di-   rect memory access (DMA) device.   Line Interfaces   E The electrical line interface used for PSDN communications depends on E the hardware device used. X.25 Native Mode software provides only theuE electrical interface of a DTE rather than a DCE, and does not providepF clock signals. Therefore, an external clock source (for example, a mo- dem) is required.i  F The range of supported synchronous communications devices covers V.24,E V.35 and V.10, RS232, RS422 and RS423 interfaces over point-to-point,.G 4-wire, synchronous, full-duplex lines at transmission rates up to 256Ks bits per second.   Prerequisite Support  D For new PSDNs, the customer and Compaq should jointly prepare a Net-E work Profile and Customer Support Plan covering all the intended net-aF work systems, their usage of SVCs, PVCs, and other network facilities,D and their support. Without this Network Profile and Customer Support4 Plan, Compaq cannot support the network connections.   Optional Facility Supporta      "                                 11 t  k  C Support for any given CCITT X.25 facility depends on support for itCG in the appropriate supported PSDN. Generally, X.25 software is designednE to disallow use of facilities that the PSDN does not support. Table 1rF shows the options that X.25 is capable of supporting, rather than whatE X.25 actually supports when used on a particular PSDN. The X.25 prod--G uct documentation describes specific facility availability for the sup-t ported public PSDNs.  C ___________________________________________________________________u  C Table_1:_Optional_X.25_Facility_Support____________________________5  &                              Paragraph&                              Number in6                              CCITT X.25    DECnet-PlusC Option_______________________(1984)________Support_________________n  . Extended packet sequence     6.2           Yes	 numberingd  . Non-standard default         6.10          Yes window sizea  . Default throughput           6.11          N/A classes assignment  6 Packet retransmission        6.4           See Note[1]  . Incoming calls barred        6.5           N/A  . Outgoing calls barred        6.6           N/A  . One-way logical channel      6.7           N/A outgoing  . One-way logical channel      6.8           Yes incoming  . Closed user group (CUG)      6.14.1        Yes  . CUG with outgoing access     6.14.2        Yes  . CUG with incoming access     6.14.3        Yes  C ___________________________________________________________________p> [1]Not applicable to a DTE. The X.25 software does not support< receiving a level-3 reject packet and does not generate one.  "                                 12 i  y    C ___________________________________________________________________r  &                              Paragraph&                              Number in6                              CCITT X.25    DECnet-PlusC Option_______________________(1984)________Support_________________i  . Incoming calls barred        6.14.4        Yes
 within CUG  . Outgoing calls barred        6.14.5        Yes
 within CUG  . CUG selection                6.14.6        Yes  - CUG with outgoing access     6.14.7        NoV	 selection,  . Absence of both CUG          6.14.8        Yes selection facilities  . Bilateral CUG (BCUG)         6.15.1        Yes  . BCUG with outgoing access    6.15.2        Yes  . BCUG selection               6.15.3        Yes  . Reverse charging             6.18          Yes  . Reverse charging accep-      6.19          Yes tance   . Local charge prevention      6.20          N/A  . Network user identifica-     6.21          Yes tion  . Charging information         6.22          Yes  . RPOA selection               6.23          Yes  7 Hunt group                   6.24          See Note[ 2]   . Call redirection             6.25          N/A  C ___________________________________________________________________tA [2]The individual DTEs must be assigned their own addresses inde-n@ pendent of the hunt group address. X.25 can then ignore the hunt> group. Alternatively, each line on the same CPU can be config-? ured as if connected to a separate PSDN; each with the same DTEa address.  "                                 13 k       C ___________________________________________________________________x  &                              Paragraph&                              Number in6                              CCITT X.25    DECnet-PlusC Option_______________________(1984)________Support_________________p  . Called line address          6.26          Yes modified notificationr  . Call redirection notifi-     6.27          Yes cation  . Transit delay selection      6.28          Yes and indication  - On-line facility regis-      6.1           Noa tratione  . Non-standard packet size     6.9           Yes  . Flow control parameter       6.12          Yes negotiationo  . Throughput class negotia-    6.13          Yes tion  . Fast select                  6.16          Yes  . Fast select acceptance       6.17          Yes  - D-bit modification           6.3           Noo  . Abbreviated address          -             N/A  - Datagram queue length        -             Nou	 selectiono  - Datagram service signal      -             Nor logical channela  - Datagram non-delivery        -             Noo
 indication  - Datagram delivery            -             No- confirmation  "                                 14 n  D    C ___________________________________________________________________   &                              Paragraph&                              Number in6                              CCITT X.25    DECnet-PlusC Option_______________________(1984)________Support_________________n  7 Call statistics (non-        -             See Note [3]  X.25)iC ___________________________________________________________________ A [3]The X.25 software does not generate these statistics, however,u= incoming statistics supplied by the PSDN are available in thea4 accounting records and at the programming interface.C ___________________________________________________________________q  C The X.25 software does not support the following items of the CCITTr X.25 recommendation:   o  Multi-link protocol  ' o  Use of the D-bit in outgoing packets   & Wide Area Network (WAN) Device Drivers  E The WAN device drivers included in Compaq DECnet-Plus for OpenVMS VAXlG support synchronous communications. The device drivers all offer a sup-f ported user ($QIO) interface.C  E The device drivers all support full-duplex and half-duplex operation,nE where appropriate to the protocol. DDCMP and SDLC device drivers sup-eE port both point-to-point and multipoint tributary operation. `BISYNC'fD refers to the IBM implementation of bisynchronous protocol. The GEN-D BYTE protocol is a general byte-oriented protocol for use with user-7 written framing routines on some of the device drivers.d  D The maximum permitted line speed depends on the line interface stan-H dard used and must not exceed 19.29 Kbits/second for an RS232 V.24 stan-C dard interface. There may be additional line speed restrictions forAG other line interface standards. For more information, refer to the SPDsl  "                                 15 o  n  G for the synchronous interfaces. The Compaq communications layered prod- D ucts may not necessarily support operation of the synchronous inter-F face at the maximum speed supported by the device driver. Refer to theF appropriate Software Product Description for the Compaq communications@ layered product for precise details of supported configurations.  C In all cases, the data throughput over the synchronous lines is de-e8 pendent on the user applications and system environment.  C The device drivers support modem control signal operation. Refer tomF the product descriptions for the appropriate synchronous interface for? details of the modem signals supported by an individual device.v  C Supported controllers are listed in the Communications Devices sec-i tion, Table 2.  C WAN device drivers include a pseudodriver (WANDRIVER) that provides F a programming interface to the Data Link level for the LAPB, DEC-HDLC, and DDCMP protocols.  
 Network Layero  D Compaq DECnet-Plus for OpenVMS supports the Connectionless-Mode Net-G work Service (CLNS) and the Connection-Oriented Network Service (CONS).s  D Exchange of routing information between end systems and routers usesE the ISO 9542 ES-IS routing protocol. This protocol allows DECnet-PlusoI systems to autoconfigure as end systems with ISO 9542-conformant routers.D  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-CE tems per area and up to 63 areas per network), and uses the same ini-e@ 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-nE ticircuited and multihomed. Multicircuit support allows multiple cir-mD cuits to be active simultaneously. This functionality increases net-C work reliability and data throughput. Multihomed end-system supports: allows a system to have up to three network entity titles.  "                                 16       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 thatt are used to reach remote nodes.s   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-dF 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 oncD the OpenVMS operating system. The supported applications include allI licensed DECnet applications as well as layered products and user-writtenrE 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/IPuC network is supported along with other layered OSI applications suchr as X.400 and X.500.m  C A separate TCP/IP stack is required on the same system with DECnet-fC Plus. See the Optional Software section of this SPD for informationn on supported TCP/IP products.e  C OSI transport supports transport classes 0, 2, and 4 on connection-r9 oriented networks and class 4 on connectionless networks.c  "                                 17 m  s  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 communicateaC    across linked subnetworks. The inactive subset of ISO 8473 (nulliC    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. TheSF 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-hD 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,9D OSI, or TCP/IP transports using RFC 1006 and RFC 1859. This includesC the network applications that are licensed with DECnet-Plus as wellaF 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.   D You can run applications written to the OSI upper layers over OSI or TCP/IP transports.   Remote File Transfer      "                                 18 e  e  E Compaq DECnet-Plus for OpenVMS supports two upper layer protocols for C remote file transfer: the OSI protocol's File Transfer, Access, andr< 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 releaseds7 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 copya    files using DCL commands.  D o  Is implemented as an Application Service Element (ASE) of the OSI    Application layer.p  = o  Acts as the initiator or as the responder in a connection.2  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 betweene
 FTAM and DAP.u  E A full description of the FTAM services in DECnet-Plus for OpenVMS isu( provided in Appendix A of this document.   DAPt  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-sD 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,  "                                 19 i  p  I RMS calls (OPEN, GET, PUT, and CLOSE), and high-level language I/O state-kE ments (which are mapped to RMS calls). A nontransparent mode of task-aD 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.a  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 accessoE 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-n 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 designatedh2 as the default proxy account on the remote system.    Command Language File Management  C You can use most OpenVMS DIGITAL Command Language (DCL) commands totH perform remote file operations. These commands include: ANALYZE, APPEND,E BACKUP, CLOSE, CONVERT, COPY, CREATE, DELETE, DIFFERENCES, DIRECTORY,oD DUMP, OPEN, PRINT, PURGE, READ, SEARCH, SUBMIT, TYPE, and WRITE. TheC operation of these commands is transparent except for commands thatfF 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.  "                                 20       E Using the COPY command, a user can transfer sequential, relative, andrE indexed-sequential (ISAM) files between DECnet-Plus for OpenVMS nodes E that support compatible file structures and record formats. Users caniI transfer sequential or relative files with fixed length, variable length,oG or variable length with fixed control field records between two DECnet-oH Plus for OpenVMS systems. Similarly, multikeyed indexed files with vari-+ able or fixed length records are supported.p  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 filetE must be in the format expected by the node responsible for execution.eC DECnet-Plus for OpenVMS allows OpenVMS command files to be receivedo  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, ULTRIX, and UNIX systems and OpenVMSlF systems regardless of record semantics. Unlike the COPY command, whichC preserves file and record organization during a file transfer, thiseD command enables the user to modify file and record attributes during file transfer.  - OSI Application Programming Interfaces (APIs)p  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)D  C o  Interfaces to the ACSE (Association Control Service Element) and_    Presentation layers  ; o  An interface to ROSE (Remote Operations Service Element)d      "                                 21 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.6  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._   Network Virtual Terminal  C DECnet-Plus supports two upper layer protocols for terminal access:cF the OSI Virtual Terminal protocol and the DECnet Command Terminal pro- tocol.   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)o of the OSI Application layer.Y  E Virtual Terminal may act as the terminal/initiator (for a local user)c/ or as the host/responder (for the remote user).o  G A full description of Virtual Terminal features is provided in Appendix  B 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 E node that uses the Command Terminal (CTERM) protocol. This connectionr  "                                 22    n  G makes the terminal appear to be physically connected to the remote sys- F 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-eE velop programs and procedures based on these interfaces for functionsTF 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.   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-6D ule (MOM). MOM provides a set of maintenance operations over variousE types of circuits by using the Maintenance Operations Protocol (MOP). D 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 file1D 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-C ing is supported for Compaq server products. However, this facilityuC is not supported over asynchronous DECnet-Plus for OpenVMS VAX con-a	 nections.    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.  "                                 23 _  _  D Downline task loading is not supported over asynchronous DECnet-Plus for OpenVMS VAX connections.   Upline Dumping  C Memory images of adjacent nodes connected by Compaq DECnet-Plus foreG OpenVMS can be written or dumped into a file on an OpenVMS system. ThislF facility provides assistance in troubleshooting in the event of a sys-F tem crash. This facility is also supported for Compaq server products.  F This facility is not supported over asynchronous DECnet-Plus for Open- VMS VAX connections.   Mail  E The OpenVMS Mail utility allows transmission of text messages between E users on systems supporting MAIL-11. The Compaq DECnet-Plus for Open-tF VMS software allows users to exchange mail with users of other DECnet-
 Plus systems.r   Phone   C The OpenVMS Phone utility allows users to send and receive data in-uH 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-n work to exchange information.f                            "                                 24 E      OpenVMS Cluster Aliasl  C Compaq DECnet-Plus for OpenVMS supports the ability to access nodes D in an OpenVMS Cluster using a separate alias node address, while re-E taining the ability to address each node in the cluster individually.tF 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 (29.78.xx) for relevant restrictions.   C DECnet-Plus no longer requires a cluster member to be configured asiC 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).iE Network management implements the DECnet-Plus layered model, based onfE the Compaq hierarchical structure called Enterprise Management Archi-e 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-l, ponents from a Motif-based window interface.  E The Compaq DECnet-Plus for OpenVMS network management software allowsv system 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 parametersa  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,SF warning network managers of faulty or failing network components, both hardware and software.  "                                 25 s     C Network Command Language (NCL) is provided as a utility to the net- 7 work manager to perform the operations described above.y  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-t late network problems.  G Compaq DECnet-Plus for OpenVMS provides network event logging to a ter-iC minal device, disk file, or remote system. NCL users can enable andyD disable the event logging facility as well as optionally filter spe-
 cific events.h  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 collectrF and display information about specific protocol exchanges between sys- tems.t  E Compaq DECnet-Plus for OpenVMS supports an ISO CMISE application pro-tE gramming interface (API) conforming to the service definitions in ISO D 9595. The API allows for development of applications that can commu-C nicate with other management applications conforming to ISO 9595 on  remote nodes in the network.  E DECnet-Plus supports the DECnet Phase IV NCP for remote management ofR Phase IV DECnet systems.   Name Service Options  C Compaq DECnet-Plus for OpenVMS allows the use of one or more namingpD 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.e  "                                 26    l  C When you use more than one name service, a configurable search listeD defines the order in which the existing services are to be accessed.   Local Namespaceo  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-iC tained by one or more DECdns server systems. Compaq recommends thatoF DECdns servers be installed on at least two systems in every LAN. This/ should provide adequate service and redundancy.s  ( The features provided by DECdns include:  G o  A networkwide name-to-attribute mapping service that allows selectedrC    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 namespacee   o  Management and event loggingn   Distributed Time Service  "                                 27 d  a  C Compaq DECnet-Plus for OpenVMS provides a network time service withdF 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 own E time providers. DECdts can be used by distributed applications to de-C3 termine event sequencing, duration, and scheduling.   	 Operationo  E DECnet-Plus is implemented under OpenVMS as an ancillary control pro-wF cess (ACP) and a network device driver with Compaq-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 accessrC and file transfer requests, are protected by the normal OpenVMS lo-oE gin and file protection mechanisms. Outgoing connects, including filemC access and file transfer requests, can include user password infor-hC mation that is implicitly specified by NCL, or explicitly specifiedh0 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-n 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-tG fic and resultant processing, but also of the amount of concurrent pro-nE cessing specific to that node. Thus, node performance depends on many, factors including:   o  CPU type   < o  Number and type of devices attached to the particular CPU  "                                 28 l  s  , o  Number of device interrupts per unit time  ) o  Communications line(s) characteristicsd   o  Number and size of bufferst  - o  Message size and frequency of transmissionm   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-tG tual throughput is a function of many factors, including the line qual-aE ity, protocol overhead, topology, and network application(s), as wellp% as the factors cited in this section.E  G The performance of DECnet-Plus is comparable to the performance of DEC-s
 net Phase IV.r   Standards Conformances  C Compaq DECnet-Plus for OpenVMS has been designed and implemented to # conform to the following standards:d   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  "                                 29 l  l   o  U.K. GOSIP V4.0  E Contact your local Compaq office for the most recent conformance cer-o
 tificates.  
 Documentationc  D The documentation for Compaq DECnet-Plus for OpenVMS VAX is supplied as follows:L  H o  Online versions of the documentation are shipped as part of the Open-F    VMS Online Documentation Library on CD-ROM, and on the OpenVMS lay-    ered product CD-ROM.   E o  Printed copies of the documentation are shipped with TK50 and mag-o    tape H-kits.a  @ o  New features are documented extensively in the Release Notes.   Installation  C DECnet-Plus software is customer installable. Installation serviceseD are available for customers who request installation of the software5 product by an experienced Compaq software specialist.a  F Compaq requires that a customer's first use of X.25 include Compaq In-C stallation Services. These services provide for installation of theg> software product by an experienced Compaq software specialist.   Customer Responsibilities,  C Before Compaq Services can install the software, the customer must:o  E o  Ensure that the system meets the minimum hardware and software re-p1    quirements (as specified in the relevant SPDs)   D o  Prior to installing Compaq hardware or software, obtain, install,E    and demonstrate as operational any modems and other necessary cus-cG    tomer equipment or facilities to which Compaq's communications hard-e     ware or software will connect  "                                 30 c  a  D o  Designate one adjacent node to verify installation and connectiv-    ity  E o  Make available for a reasonable period of time, as mutually agreedsC    upon by Compaq and the customer, all hardware communications fa-tB    cilities and terminals that are to be used during installation.  C Delays caused by any failure to meet these responsibilities will bes6 charged at the prevailing rate for time and materials.  C Installation of Compaq DECnet-Plus for OpenVMS consists of the fol-n
 lowing tasks:d  D o  Verify that all components of Compaq DECnet-Plus for OpenVMS have    been received.m  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 chargem    will apply.  C o  Create any necessary Compaq DECnet-Plus for OpenVMS accounts and     directories.M  C o  Enable software by registering the License Product Authorizationi    Key (PAK) .  C o  Install the Compaq DECnet-Plus software on the target system us-e5    ing the POLYCENTER Software Installation utility .   C o  Verify the proper installation of Compaq DECnet-Plus for OpenVMS D    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-sE bility of the customer. Compaq recommends the use of NCL to help ver-e ify connectivity.s  "                                 31 A  F  G In some cases, the PSDN supplier (or PTT) may impose restrictions, lim-aC itations, or requirements on the proposed Compaq network configura-nC tion. The customer must understand and adhere to these controls for  every network.  9 For installation of the X.25 software, the customer must:   H o  Demonstrate equivalence of operation for modems other than Bell 208A,I    208B, 209, 212A synchronous modems, or in Europe, PTT approved modems.c  E o  Subscribe to the open user group and to at least two switched vir-hE    tual circuits (SVCs) to complete the product's installation check-pF    out (this test loops information from the X.25 native system to theC    PSDN and back to X.25 native system). Systems that use permanentqC    virtual circuits (PVCs) or closed user groups only, or where the D    PSDN does not support calls to the same DTE address, require spe-F    cially negotiated arrangements for Compaq installation of the prod-    uct.E   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 system C disk. The sizes are approximate; actual sizes may vary depending oniC the user's system environment, configuration, and software options.(              "                                 32    o   For OpenVMS VAX Systemsp  D Disk space required for installation of base software: 85,000 blocks  F Disk space required for installation of all optional software: 115,000 blocks   For WAN Device Drivers  ; Disk space required for installation: 5,000 blocks (2.5 MB)o  C The disk space required for permanent use depends on the number and C type of drivers installed, but should not exceed the space requireda for installation.c   For X.25 Softwaree  9 Disk space required for installation: 8,000 blocks (4 MB)a  = Disk space required for use (permanent): 10,000 blocks (5 MB)i  E These counts refer to the disk space required on the system disk. TheoD sizes are approximate; actual sizes may vary depending on the user's8 system environment, configuration, and software options.   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.   Cluster Environmenti  F The WAN device drivers are fully supported when installed on any validD and licensed OpenVMS Cluster configuration. A device driver can onlyE be accessed from the system or node containing the communications de-t vice.   C On common disks, to configure some product-specific attributes thatoD must remain unique to each system, certain components of the productF are stored in the system-specific environment (SYS$SPECIFIC: [SYSxxx])E of the VAX computer on which the installation is being performed. Then  "                                 33 e  s  E remaining components of the product, including some or all of the ex- C ecutable images, are installed common to all accessing VAX systems.   G Though some or all of the product's executable images exist in the com-aF mon system directory (SYS$COMMON: [SYS$LDR]) and are executable by allD VAX computers sharing this directory, it is essential that the prod-D uct be installed separately on all OpenVMS Cluster systems requiring2 access to configure the product uniquely for each.  E The same version of WAN device drivers must be used on all systems insG OpenVMS Cluster systems accessing a common disk and in local area Open-t VMS Cluster configurations.c   Communications Devices  C One of the communications devices listed in Table 2 is required foro use with X.25 native and WANDD.h  C ___________________________________________________________________e  C Table_2:_Synchronous_Communications_Devices_________________________  ( Busless    Q-bus       VAXBI       VAXftC Systems____Systems_____Systems_____Systems_____UNIBUS_Systems______D  4 DSH32      DPV11       DMB32       DSF32       DMF32  4 DST32      DSV11       DSB32                   DUP11   DSW43i   DSW42O   DSW41s  C DSW21______________________________________________________________t  9 Refer to Table 3 for line speeds for supported protocols.m  F o  The DSH32 (dual synchronous line) and the DST32 (single synchronousD    line) are multifunction devices for busless systems. The communi-D    cations controllers support DMA transfers for bit-oriented proto-E    cols and perform character transmission, reception, and framing ina
    microcode.e  "                                 34    s  H o  The DSW21 and DSW41 (single line) and the DSW42 (dual line) are high-J    performance synchronous communications controllers for busless MicroVAXC    3100 and VAXstation 4000 systems. The communications controllersCC    support DMA transfers for bit- and character-oriented protocols. E    The communications controller performs character transmission, re-a%    ception, and framing in microcode.p  C o  The DPV11-DA or the DPV11-S (Q-bus) and DUP11 (UNIBUS) are char-aE    acter interrupt devices for data link handling. CPU cycles are re-oD    quired for data link level protocol processing and for each char-    acter sent and received.   E o  The DSV11 is a dual-line synchronous communications device for alltJ    Q-bus systems. The DSV11 supports DMA transfers for bit- and character-C    oriented protocols. The communications controller performs char- ;    acter transmission, reception, and framing in microcode.S  D o  The DSF32 (MI-bus) is a multifunction device for VAXft fault tol-E    erant systems. The DSF32 provides a dual-line synchronous capabil-aF    ity and supports DMA transfers for bit- and character-oriented pro-E    tocols. The communications controller performs character transmis-AG    sion, reception, and framing in microcode. You can use the two linesrD    independently to run different protocols or to provide a failoverD    capability between lines in the event of an application or system    failure.e  F o  The DMB32 (BI-bus) and the DMF32 (UNIBUS) are multifunction devicesF    that include a single DMA line. The communications controllers per-D    form character transmission, reception, and framing in microcode.  C o  The DSB32 (BI-bus) is a dual-line synchronous communications de-uD    vice for VAXBI systems. The DSB32 supports DMA transfers for bit-B    and character-oriented protocols. The communications controllerH    performs character transmission, reception, and framing in microcode.   Notes:  E o  The DSH32 and DST32 are not supported on VAXstation 2000 and VAXs-l    tation 3100 systems.p  "                                 35       G o  The DSB32 is not supported for use on the VAX 7000 or VAX 10000 sys-r    tems.  E o  The DSB32 is not supported for use on a VAX 6600 with extended ad-a1    dressing (>512 MB of physical memory) enabled.   F o  The DMB32, DMF32, and DSH32 are multifunction devices. Only the de-D    vice driver for the synchronous ports are included in the DECnet-    Plus kit.  D o  The DMB32 must be revision J or later for applications using GEN-!    BYTE, HDLC, or SDLC protocols..  D o  The DMF32 must be revision J of later for applications using HDLCD    protocol and revision M is required for simultaneous operation of    the printer port.  C o  The DMB32 only supports a synchronous line speed of 19.2 Kb/s if D    any asynchronous lines are in use. The DMB32 is also supported onC    VAX 7000 and VAX 10000 systems configured with extended address-C$    ing, (32-bit physical addresses).  F o  The DMF32 is supported on a VAXBI system fitted with a DWBUA UNIBUS3    adapter for DDCMP and GENBYTE protocol use only.-  C o  The DSH32 running the DDCMP protocol only supports a single lineaG    at 9.6 Kb/s on a MicroVAX 2000. Running the BISYNC protocol, it onlys9    supports a single line at 4.8 Kb/s on a MicroVAX 2000.o  D o  The DSV11, DSW42, and the DSB32 support the use of different pro-1    tocols on each of the two lines of the device.E  F o  The DUP11 is supported on a VAXBI system fitted with a DWBUA UNIBUSD    adapter for VAX 8200, VAX 8250, VAX 8300, VAX 8300, VAX 8350, VAXA    8500, VAX 8530, VAX 8550, VAX 8700, and VAX 8800 systems only.a  F All the WAN device drivers included with DECnet-Plus offer support forC a user ($QIO) interface. Table 3 lists the device driver character-IF istics and indicates the maximum permitted line speeds for each of the3 line protocols supported by the individual drivers.   "                                 36       C ___________________________________________________________________   C Table_3:_Synchronous_Device_Driver_Characteristics_________________   5                                Maximum Line Speed forf7                              Supported Protocols (Kb/s)m  C Device___Code_____DDCMP____HDLC_____SDLC___________________________r  ( DMB32    SI       19.2     38.4     38.4  * DSB32    SL       64/64    192/64   192/64  * DSV11    SJ       256/64   256/64   256/64  ( DMF32    XG       19.2     19.2     19.2  ' DPV11    SE       9.6      9.6      9.6v  ( DSH32    ZS       19.2     19.2     19.2  (                   /9.6     /9.6     /9.6  ( DST32    ZS       9.6      19.2     19.2  ' DUP11    SE       4.8      9.6      9.6s  ) DSF32    SF/SM    64/64    64/64    64/64   * DSW43    ZT       256/64   256/64   256/64  * DSW42    ZT       256/64   256/64   256/64  ' DSW41    ZT       256      256      256p  C DSW21____ZT_______256______256______256____________________________C  E Note: Where two line speeds are shown, for example 256/64, the higherlC speed refers to single line operation of the device while the lowere2 speed refers to dual line operation of the device.  E The WAN device drivers included with DECnet-Plus also provide a pseu-iF dodriver (WANDRIVER) that provides a programming interface to the data7 link level for the LAPB, DEC-HDLC, and DDCMP protocols.i  E The device drivers all support full-duplex and half-duplex operation,-E where appropriate to the protocol. DDCMP and SDLC device drivers sup-IE port both point-to-point and multipoint tributary operation. "BISYNC"c  "                                 37    W  D refers to the IBM implementation of bisynchronous protocol. The GEN-D BYTE protocol is a general byte-oriented protocol for use with user-E written framing routines, is supported by the DMB32 and the DMF32 de-i
 vice drivers.o  D The maximum permitted line speed depends on the line interface stan-D dard used and must not exceed 19.2 Kb/s for an RS232 V.24 interface.E There may be additional line speed restrictions for other line inter-CG face standards. Refer to the Software Product Descriptions for the syn-p) chronous interfaces for more information.m  E Other Compaq communications layered products may not necessarily sup-lE port operation of the synchronous interface at the maximum line speedaG supported by the device driver. Refer to the appropriate Software Prod-oF uct Description for the Compaq communications layered product for pre-) cise details of supported configurations.d  C In all cases, throughput over synchronous lines is dependent on thec( user application and system environment.  F The WAN device drivers all support modem control signal operation. Re-H fer to the Software Product Descriptions for the appropriate synchronousC interface for details of the modem signals supported by an individ-s ual interface.   Optional Hardwarer  H Additional communications device(s) subject to the limitations described$ in Table 3 of this SPD are required.   Supported Public Networks   E Table 4 describes public PSDNs that are supported with the X.25 soft- D ware only in the countries shown. In addition to these public PSDNs,F certain private PSDNs have been tested by Cpompaq and appropriate pro-( files are included in the X.25 software.        "                                 38 m  i  E Since the publication of this SPD, other configurations may have beenMC tested. Consult your local Compaq office for any questions concern- E ing other public PSDNs. Compaq has designed or adopted the X.25 soft--E ware to operate with equipment conforming to ISO 8208/7776, with cer-,C tain private PSDNs that have been approved by Compaq, and with pub-cD lic networks in Table 4. Profiles for these private and public PSDNsF are included in X.25. Connections to public networks not shown in this" table are not supported by Compaq.  C The presence of a network/country combination in Table 4 shows Com-rD paq's commitment to support the X.25 software when using that publicC X.25 service. It does not necessarily imply that network certifica-oD tion by the particular networking authority has been granted for allD or any hardware devices supported by the X.25 software. Contact yourG local Compaq office for up-to-date information regarding supported con- % figurations and certification status.m  G Compaq has designed or adapted the X.25 software to operate with equip-fF ment conforming to ISO 7776/8208 with the public networks in the coun-D tries listed below and with certain private PSDNs that have been ap- proved by Compaq.m  C ___________________________________________________________________t  C Table_4:_Supported_Public_Networks_________________________________u  C Country_________________Public_Network_and_CCITT_revision(s)_______p   Argentina               ArpacO   Australia               AustpacO   Austria                 Datex-P    Belgium                 DCSc   Brazil                  Renpac  , Canada                  Datapac (1976, 1980)                         DPN-NASn                         Faspac"                         Infoswitch  "                                 39 r  e    C ___________________________________________________________________   C Country_________________Public_Network_and_CCITT_revision(s)_______e   Chile                   VTRNET   China                   CNPACn   Denmark                 Datapako  * Ireland                 Eirpac (1980,1984)                         Postgemi   Finland                 Datapak,    France                  Transpac   Germany                 Datex-Po   Hong Kong               Datapak                          GDNw                         INET                          Intelpak   Indonesia               SKDP   Italy                   Itapac  . Japan                   DDX (1976, 1980, 1984)#                         ACE Telenetu                         CCVANo                         INS-P                          Jaisnet &                         Venus-P (1980)                          Venus-LP                         Tymnet   Luxembourg              LUXPAC   Malaysia                Maypac   Mexico                  TelepacC  ! Netherlands             Datanet 1c   New Zealand             Pacnet   Norway                  Datapaki   Pakistan                Paknet  "                                 40 t       C ___________________________________________________________________l  C Country_________________Public_Network_and_CCITT_revision(s)_______t   Philippines             Datanete   Portugal                TelepacM   Singapore               Telepacr    South Korea             Dacomnet   Spain                   Iberpace   Sweden                  Datapak   , Switzerland             Telepac (1978, 1980)   Taiwan                  Pacnet   Thailand                Samart                         Thaipak    Turkey                  Turpac   United Kingdom          PSSe   United States           AccunetS                         Autonet %                         Bell Atlantic "                         Compuserve                         ConnNeta                         Digipacg                          Fedexitc                          Graphnet                         IMPACS                         Infonet 0                         MarkNet Extended Service                         PPSNET!                         Pulselink                          Sinet                          Telenetr                         Tymnet+                         Western Union PTN-1 C ________________________Worldnet___________________________________i  "                                 41 a  t  E Note: Compaq offices in Japan can supply the mandatory additional in- B formation that explains the special use of X.25 with the DDX PSDN.  C Unless otherwise acknowledged within the product documentation, the F trademarks under which the services are offered are proprietary to theE respective national PTT, the owning or operating companies, or equiv- : alent organization. X.25 Software Configuration Guidelines  C Table 5 describes the physical hardware configurations supported by'D X.25 in terms of CPU type and communication interface. It is assumedG that there are 128 bytes of user data per packet in an X.25 native modesE configuration where data is being sent and received at maximum speedsoE in both directions. This table indicates the maximum load for certaine4 VAX processors supported at the time of publication.  F The numbers given in the table are load costs. Load costs indicate theC overhead of full-duplex packet transfer at the indicated speed. The-C load units are calculated for an application that does no work with-F transmitted/received data, and indicate a maximum packet rate for thatD configuration. An idle device incurs negligible load. Systems should) be configured to sustain peak load rates.f  C ___________________________________________________________________x  C Table_5:_CPUs,_Maximum_Load_and_Supported_Devices__________________n                           Maximumo/                         Load in       Supported C CPU_____________________load_units____Device(s)____________________n  , MicroVAX II             160           DSV11,.                                       DPV11-DA  , MicroVAX 2000           100           DSH32,+                                       DST32n  + MicroVAX 3100           350           DSH32i  , MicroVAX 3100 Model     440           DSW41,+ 30/40                                 DSW42x  "                                 42 n       C ___________________________________________________________________s                           Maximum /                         Load in       SupportedoC CPU_____________________load_units____Device(s)____________________   , MicroVAX 3100 Model     1000          DSW41,+ 80                                    DSW42t  , MicroVAX 3100 Model     2100          DSW41,+ 90                                    DSW42   , MicroVAX 3300/3400      210           DSV11,-                                       DPV11-Sa  , MicroVAX 3500/3600      330           DSV11,-                                       DPV11-Sa  , MicroVAX 3800/3900      390           DSV11,-                                       DPV11-Sm  + VAXft Model 310         320           DSF32n  + VAXserver 3100          290           DSH32   , VAXserver 6000 Model    210           DMB32,+ 210                                   DSB32    VAXserver 6000 Model DSB32h  , VAXserver 6000 Model    300           DMB32,+ 400 Series                            DSB32a  , VAX-11/730              40            DMF32,+                                       DUP11o  , VAX-11/750              70            DMF32,+                                       DUP11m  , VAX-11/780              120           DMF32,+                                       DUP11x  , VAX-11/785              180           DMF32,+                                       DUP11   , VAX 8600                400           DMF32,+                                       DUP11   "                                 43    e    C ___________________________________________________________________                            Maximums/                         Load in       SupportedoC CPU_____________________load_units____Device(s)____________________o  , VAX 8650                500           DMF32,+                                       DUP11   , VAX 4000 Model 300      580           DSV11,-                                       DPV11-S_  , VAX 6000 Model 200      250           DMB32,+ Series                                DSB32   , VAX 6000 Model 300      350           DMB32,+ Series                                DSB32_  , VAX 6000 Model 400      450           DMB32,+ Series                                DSB322  , VAX 8200/8300           100           DMB32,+                                       DSB32_  , VAX 8250/8350           125           DMB32,+                                       DSB32m  , VAX 8500                360           DMB32,+                                       DSB32i  , VAX 8530                450           DMB32,+                                       DSB32e  , VAX 8550                550           DMB32,+                                       DSB32g  , VAX 8700                700           DMB32,+                                       DSB32(  , VAX 8800/8810/882/      700           DMB32,+ 8830/8840                             DSB32o  , VAX 8842                700           DMB32,+                                       DSB32o  , VAX 8978                700           DMB32,C ______________________________________DSB32________________________m   Factors to Considern  "                                 44 o  p  C Other factors to consider when configuring hardware devices for usea# with X.25 on a given processor are:   H o  Hardware configuration limits, such as power supply, backplane space,D    bus throughput and mapping registers available, and any other re-E    strictions on the number of devices per CPU or per bus must be ob-s
    served.  D o  Actual/average packet size in bytes - Generally, doubling the ac-F    tual packet size will halve the load units consumed for direct mem-G    ory access (DMA) devices, but increase the load units for character-m1    interrupt devices by approximately 30 percent.s  C o  Table 5 assumes that data is sent and received in each directiondD    of a full-duplex line in equal ratio. If the number of X.25 pack-C    ets per second is predominantly one-way, the load units per lineo?    can be reduced proportionately up to a factor of 50 percent.r  C The maximum system configuration with a mix of device types is com- D puted by adding the load costs (in load units) for each device up toF the limit for a given processor type. Table 6 lists the load units for devices at various speeds.  C ___________________________________________________________________r  C Table_6:_Load_Units_per_Line_at_Various_Speeds_____________________2  ?                                 Load Units used at Speed (Kb/s)o   Device      # of    Max.C Type________Lines___Speed___4.8____9.6____19.2___48_____64_________T  ; DMB32       1       64.0    9      18     36     n/s[1] n/sn  ; DSB32       2       64.0    9      18     36     90     1202             or 1    192.0d  ; DMF32       1       19.2    9      18     36     n/s    n/s   C ___________________________________________________________________ @ [1]n/s indicates that the use of the device at this speed is not supported by x.25.  "                                 45    d    C ___________________________________________________________________d  ?                                 Load Units used at Speed (Kb/s)t   Device      # of    Max.C Type________Lines___Speed___4.8____9.6____19.2___48_____64_________   ; DPV11-      1       9.6     23     64     n/s    n/s    n/so DA[2]. DPV11-Se  ; DST32       1       19.2    10     20     40     n/s    n/s   ; DSH32       1       19.2    10     20     40     n/s    n/so  ; DUP11[2]    1       9.6     23     46     n/s    n/s    n/sh  ; DSV11       2       64.0    9      18     36     90     120r             or 1    256.0   ; DSW21       1       256.0   9      18     36     90     120  DSW41d  ; DSW42       2       64.0    9      18     36     90     1202 DSW43       or 1    256.0s  ; DSF32       2       64.0    9      18     36     90     120EC ___________________________________________________________________sB [2]For more than one character interrupt device, multiply the load= units by 50 percent to allow for interaction between devices.KC ___________________________________________________________________t  
 Example 1:  D A VAX 8500 computer is being used to process X.25 native mode commu-C nications. If the system uses one line of a DSB32 at 192 Kb/s and a F DMB32 at 19.2 Kb/s, the load unit total is 156. Assuming these devicesE are fully active, they will consume 156/360 = 43% of the CPU for com-hE munications processing. It is inadvisable to add more devices to thisrE CPU, unless it is dedicated to the task of communications processing.a  
 Example 2:  E When one line of a DSV11 is fully used on a MicroVAX 3800 at 64 Kb/s,dD it consumes 120/390 = 31% of the processor in processing X.25 commu-
 nications.  "                                 46 _  _  F Certain versions of these products depend on a specific version of theC operating system. Refer to the Software Product Descriptions of the ; product in question to determine which version is required.m   Software RequirementsM  D Compaq DECnet-Plus for OpenVMS VAX requires OpenVMS operating system Version 7.3.   OpenVMS Tailoring   D The following OpenVMS classes are required for full functionality of this layered product:       OpenVMS Required Save Set    Network Support    Programming Support  C For more information, refer to the OpenVMS Operating System for Al- H pha and VAX Software Product Description (SPD 25.01.xx). OpenVMS classesC and tailoring are discussed in the OpenVMS VAX installation manual.    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:l  3 o  DIGITAL TCP/IP Services for OpenVMS Version 5.1.e6    DIGITAL TCP/IP Client Software License: QL-GL7A*-**8    DIGITAL TCP/IP Services Software License: QL-VHRA*-**5    DIGITAL TCP/IP Client Upgrade License: QL-0PHA*-**r    SPD: 46.46.xx   X.25 Optional License   "                                 47 l  a  F An X.25 license is required when using X.25 and the LAPB protocol overG the WAN. This license is not required when using X.25 and the LLC2 pro-r tocol on the LAN.C   Software License: QL-071A*-AA   C Media and Documentation: Included in Compaq DECnet-Plus for OpenVMSt! VAX media and documentation kits.g   Growth Considerationso  D The minimum hardware/software requirements for any future version ofC this product may be different from the requirements for the currents version.   Distribution Media  C This product is available as part of the OpenVMS Consolidated Soft-eF ware Distribution on CD-ROM. The software documentation for this prod-E uct is also available as part of the OpenVMS Online Documentation Li-t brary on CD-ROM.  D Compaq DECnet-Plus for OpenVMS VAX is also available on TK50 stream-C ing tape for a limited time. Support for H-Kits on this traditionalu? media are being phased out in favor of the CD-ROM distribution.r   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 Li-         QL-D04A*-AA censes:              End Systemm                         QL-D05A*-AA&                      Extended Function      "                                 48 f  t      OpenVMS VAX CD-      QA-VWJ8A-A8 ROM Distribution:m  # Software Media:      QA-D04AA-H*(*)   4 Software Documen-    QA-D04AA-GZ (Documentation Set) tation:     Consolidated         QT-VWJ8A-*8 Distribution Service:    Software Product     QT-D04A*-**	 Services:t   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-t> 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- E tures with the exception of the DECdns Server, cluster alias, the OSIaE application programming interface, the OSI applications gateways, ands routing.  E The Extended Function license grants the right to use the DECnet-Plus E end-system features, the DECdns Server, OSI application gateways, OSI E application programming interfaces, host-based routing, and the clus-iC ter alias. An Extended Function license is required on at least onerD node in every cluster configuration to enable the use of the cluster alias.  E This software is furnished under a license only. For more informationoD about Compaq's licensing terms and policies, contact your local Com- paq office.t  # License Management Facility Supporte  B This product supports the OpenVMS VAX License Management Facility.  < License units for this product are allocated on a CPU basis.  "                                 49    r  E For more information on the License Management Facility, refer to the D OpenVMS Operating System for Alpha and VAX Software Product Descrip-D tion (SPD 25.01.xx) or the License Management Facility manual of the/ OpenVMS VAX operating system documentation set.   F For more information about Compaq's licensing terms and policies, con- tact your local Compaq office.   Software Product Services_   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 Warranty_  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.                           "                                 50 l     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 filesp  E An open system is a computer system that implements the standards foraG 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 protocola  # o  ISO 8823 - Presentation protocol    o  ISO 8327 - Session protocol  D Table 7 compares the supported implementation profiles for different6 standards bodies and their relationship to each other.    "                                 51       C ___________________________________________________________________   C Table_7:_Standards_and_Implementation______________________________e  
 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-a
 straint sets,S 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 -o( (DISP)[1] -       sitional    ENV 41 206 Positional        File File Trans-       Transfer fer Service 	 (Flat)[2]a  C ___________________________________________________________________a [1]Draft ISP( [2]AFT12 is not supported by DECnet-Plus  "                                 52 k  l    C ___________________________________________________________________s  
 Internationale Standardized Profiles (ISP)C ISO_10607_________NIST________CEN/CENELEC_and_EWOS_________________l  $ Part 5: AFT3      M1 -        A/13 -( (DISP)[1] -       Manage-     ENV 41 205 File Manage-      mentC ment_Service_______________________________________________________n [1]Draft ISPC ___________________________________________________________________    FTAM Component Software   E The component software includes the user facilities (initiators), re-o< sponders, management tools, and problem determination tools.   FTAM User Facilities  E Users access the FTAM user facilities by entering the following Open-LC VMS operating system commands: APPEND, COPY, DIRECTORY, RENAME, andeG 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.        "                                 53 X  0   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-4 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 8_E shows the parameters supported by FTAM-1, FTAM-2, and FTAM-3 documentd types.  C ____________________________________________________________________  C Table_8:_FTAM_Document_Types_______________________________________              String Document  Signifi-    UniversaleC Type______cance_______Class_______Maximum_String_Length____________4  A FTAM-1    Not         IA5String   Presence and absence of parame- %           significant             terX#                       GeneralString   7           Fixed       VisibleStrinPresence of parameter3  #                       GraphicString   A           Variable    VisibleStrinPresence and absence of parame- %                                   ter #                       GraphicStringr  B FTAM-2    Not         VisibleStrinPresence or absence of parameter           significantr#                       GraphicString0  B FTAM-3    Not                     Presence or absence of parameter           significant   C __________Fixed___________________Presence_of_parameter____________   % NBS-9 files are NBS file directories.   "                                 54       / 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.o  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.5D 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.A                                  "                                 55       
 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 worksiF 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-g? 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-r ality as follows:t  F o  If an internal error is detected in the data transfer regime, classE    1 recovery restarts the data transfer regime by retransmitting themC    file data beginning at the negotiated checkpoint within the datad    transfer regime.m  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 ofeH    file data beginning at a negotiated checkpoint within the data trans-    fer regime.  "                                 56    u  C o  Class 3 error recovery provides full recovery by re-establishingmC    a lost FTAM association and its select and open regimes. Class 3hD    recovery then restarts the data transfer regime by retransmittingG    the file data beginning at the negotiated checkpoint within the datas    transfer regime._  H All restart and recovery operations and procedures are completely trans- parent to the user.u                                                                "                                 57 e  e  * 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). ThetD 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,4 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.a   FTAM Event Logging  K For event logging, the FTAM responder writes records to OSIF$RESPONDER.LOG.c        "                                 58 _  _  ( Requirements for Compatibility with FTAM  E FTAM lets an open system perform a specific set of file transfer, ac-nE cess, and management activities with any open system having a compat-1 ible FTAM implementation.a  F The Protocol Implementation Conformance Statement (PICS) provides more/ information about Compaq's FTAM implementation.s                                                                "                                 59 i  i   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 (ISOeD 9041). VT software adheres to these standards, thereby providing in-G teractive access between DECnet-Plus systems and other multivendor ter-qG minal systems and host systems that also adhere to the ISO Virtual Ter-M minal Basic Class standard.e  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/initiatorx are not supported.   Supported Standardss  + VT conforms to the following OSI standards:   5    ISO 9041 - Virtual Terminal protocol - basic classl    ISO 8650 - ACSE protocol #    ISO 8823 - Presentation protocole    ISO 8327 - Session protocol   Virtual Terminal Featureso  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)I  B    -  A-mode Generalized Telnet (adheres to OIW Stable Agreements)  ;    -  A-mode Transparent (adheres to OIW Stable Agreements)c  "                                 60 .  O  ;    -  A-mode Telnet 1988 (adheres to OIW Stable Agreements)    o  Functional Unitsq      -  destructiveBreak      -  structuredCOs       -  urgentData   o  Supported Gatewaysi      -  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 thegF X.500 directory. You can use this functionality with or instead of re-+ trieving addresses from a local repository.b   Command Mode  E Command mode allows you to execute commands that can modify the char-sC acteristics of the Virtual Terminal association with the remote ap-e
 plication.  
 Trace Utilitys  D The VT tracing utility (OSITRACE) is a tool for identifying problemsC in protocol exchanges between your local system and any remote sys-eF tem. The utility captures protocol exchanges and transcribes them into easily read text.o  C The tracing utility monitors data exchanges for individual associa- E tions. The utility can trace data originating from the VT, ACSE, Pre-g" sentation, and Session components.  "                                 61    i  2 Appendix C: OSI Application Programming Interfaces   FTAM API  E The FTAM API supports the OSI standard ISO 8571: Information Process-SE ing Systems, Open Systems Interconnection, and File Transfer, Access,e and Management.   E The FTAM API provides the interface to the FTAM protocol machine pro-WE vided in DECnet-Plus. Communications between the application code andoI the FTAM protocol machine are carried out using ASN.1 encoded data struc-d0 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:O    "                                 62       C o  ISO 8650: Information Processing Systems, Open Systems Intercon--C    nection, Protocol Specification for the Association Control Ser-p    vice Elementm  C o  ISO 8649: Information Processing Systems, Open Systems Intercon-dF    nection, Service Definition for the Association Control Service El-    ement  E The OSAK API provides the interface to the ACSE services. It providesd the following services:r      Associate
    Release    Abort    Redirecta  C The redirect service is not an ACSE service. The service allows ap-tD 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-nC    nection, Connection-Oriented Presentation Protocol Specificationn  C o  ISO 8822: Information Processing Systems, Open Systems Intercon-M?    nection, Connection-Oriented Presentation Service Definitionn  C o  ISO 8327: Information Processing Systems, Open Systems Intercon-pD    nection, Basic Connection-Oriented Session Protocol Specification  C o  ISO 8326: Information Processing Systems, Open Systems Intercon-p@    nection, Basic Connection-Oriented Session Service Definition  > The Presentation layer services supported by the OSAK API are:      Alter-Context    Datac    Capability-Data    Expedited-Datae
    Typed-Datau  "                                 63 u  m      Token-Pleaseo
    Token-Givep    Control-Giveo
    Sync-Major 
    Sync-Minori    Resynchronize    Exception-Reporto    Activity-Starto    Activity-Interrupto    Activity-Resume    Activity-Discards    Activity-Endi  G The OSAK API also supports (by pass through) the OSI Session layer ser-m 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.p  F Support for the OSAK SPI interface is limited to Version 3.0. The OSAK1 Version 1.1 SPI interface is no longer supported.r  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.  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.  "                                 64    m  D The OSAK API provides the interface to the following connect and re- lease services:   
    Connect
    Release    Abort    Redirectl  E The redirect service is not a Session service. The service allows ap-mC plications to redirect an incoming connection to another process onI the local system.i  9 The Session layer services supported by the OSAK API are:p      Datap    Capability-Data    Expedited-Datae
    Typed-Data     Token-Pleaser
    Token-Givee    Control-Give 
    Sync-Major 
    Sync-Minor1    Resynchronize    Exception-Report_    Activity-Start_    Activity-Interrupt     Activity-Resume    Activity-Discard_    Activity-End_                    "                                 65 S  0   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, as20 defined in ISO 9072, for the following services:  	    Invokeo	    Result     Error	    Reject   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.p  "  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-s nologies Group, L.P.  D All other product names mentioned herein may be trademarks or regis-/ tered trademarks of their respective companies.   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.e  E Compaq shall not be liable for technical or editorial errors or omis-sC sions contained herein. The information in this document is subjectc to change without notice.C  "                                 66 s  e                                                                                  "                                 67