      Software Product  Description   C ___________________________________________________________________   G PRODUCT NAME:  Compaq DECnet for OpenVMS VAX and Alpha, Version 7.3 SPD  48.48.07  G Note: This Software Product Description (SPD) covers DECnet for OpenVMS E on VAX and Alpha platforms. Unless explicitly noted, the features de- D scribed apply to both platforms. Licenses and part numbers are plat-G form specific and are noted in the Ordering Information section of this  SPD.   DESCRIPTION   H DECnet for OpenVMS on VAX and Alpha allows a suitably configured OpenVMSE system to participate as an end node or, on VAX systems only, a rout- C ing node in DECnet computer networks. With proper network planning, E DECnet networks can contain up to 1,023 nodes per network area and up  to 63 areas per network.  D DECnet for OpenVMS end node and full (VAX) or Extended (Alpha) func-C tion products are licensed separately for OpenVMS systems. The DEC- D net for OpenVMS License Product Authorization Key (PAK), when regis-E tered on an OpenVMS system, enables communication between systems us-  ing the DECnet protocols.   C DECnet for OpenVMS has been implemented in accordance with Phase IV E of the Digital Network Architecture (DNA) product. DECnet for OpenVMS E is a layered product that ships with the Alpha and VAX operating sys- D tem and is separately licensed. DECnet for OpenVMS is warranted onlyD for use with Phase IV and DECnet-Plus (formerly DECnet/OSI) products) supported by Compaq Computer Corporation.   C DECnet for OpenVMS offers task-to-task communications, file manage- F ment, downline system and task loading, network command terminals, and  C                                                          April 2001        C network resource sharing capabilities using the Digital Network Ar- D chitecture (DNA) protocols. DECnet for OpenVMS communicates with ad-6 jacent and nonadjacent Phase IV and DECnet-Plus nodes.  F OpenVMS programs written in MACRO and native mode high-level languages, can use DECnet for OpenVMS VAX capabilities.  D The network functions available to a DECnet for OpenVMS user depend,C in part, on the configuration of the rest of the network. Each DEC- G net product offers its own subset of Digital Network Architecture (DNA) D functions and its own set of features to the user. Networks consist-D ing entirely of DECnet for OpenVMS Phase IV nodes have all the func-F tions described in this SPD. The functions available to users on mixedE networks can be determined by a comparison of the SPDs for the appro-  priate DECnet products.   D Routing capabilities are offered on OpenVMS VAX systems only. A FullC Function DECnet for OpenVMS VAX License PAK must be registered on a D node in order for that node to operate as a routing node. For a nodeC to operate as an end node, either the Full Function or the End Node C DECnet for OpenVMS VAX License PAK must be registered on that node. E Full Function DECnet for OpenVMS VAX software allows a node to be set E up as either a routing node or as an end node. See Appendix A of this F SPD for more information on routing capabilities in DECnet for OpenVMS VAX systems.                              "                                  2       ( Standard DECnet for OpenVMS Capabilities   Task-to-Task Communication  C For most applications, task-to-task communication can be programmed F in a transparent manner where the remote task is treated as a full du-C plex, record-oriented device. Transparent operation is provided via E the following interfaces: System Service calls, RMS calls (OPEN, GET, H PUT, and CLOSE) and high-level language I/O statements (which are mappedE to RMS calls). A nontransparent mode of task-to-task communication is E offered by means of the System Service interface that extends the ca- C pabilities provided by the transparent mode. These capabilities in- E clude support for interrupt messages and multiple inbound connect re-  quests.   G Using DECnet for OpenVMS, an OpenVMS program can exchange messages with C other user programs. The two user programs can be on the same node, D on adjacent Phase IV or DECnet-Plus nodes, or on any two nonadjacentD Phase IV or DECnet-Plus nodes in the same network connected by PhaseC IV or DECnet-Plus routing nodes. DECnet for OpenVMS imposes no spe- . cial data formatting requirements on the user.   Network Resource Access   E File Access - File access is supported to and from remote DECnet sys- G tems using RMS. User programs can sequentially read, create, and delete  files on a remote node.   F Record Access - User programs can perform record level operations suchH as GET, PUT, UPDATE, DELETE, FIND, and REWIND to access and modify filesC residing on a remote OpenVMS node. In addition to sequential access E to a file, several other access methods are supported through RMS us- C ing DECnet for OpenVMS. These methods include random access by rel- H ative record number, random access by key value, random access by RecordA File Address (RFA), and block I/O access by virtual block number.    Proxy Access      "                                  3       E Remote users can have access to up to 15 proxy accounts on a specific D remote system. One proxy account should be designated as the default# proxy account on the remote system.     Command Language File Management  C Most OpenVMS Digital Command Language (DCL) commands can be used to E perform network file operations. These commands include: ANALYZE, AP- D PEND, BACKUP, CLOSE, CONVERT, COPY, CREATE, DELETE, DIFFERENCES, DI-I RECTORY, DUMP, OPEN, PRINT, PURGE, READ, SEARCH, SUBMIT, TYPE, and WRITE. G The operation of these commands is transparent except for commands that Q invoke processing on a specific system (that is, SUBMIT/REMOTE and PRINT/REMOTE). D Only a node name added to a file specification is required to invoke3 the network capabilities via one of these commands.   E Using the COPY command, a user can transfer sequential, relative, and F indexed-sequential (ISAM) files between DECnet nodes that support com-H patible file structures and record formats. Sequential or relative filesF with fixed length, variable length, or variable length with fixed con-G trol field records can be transferred between two OpenVMS systems. Sim- F ilarly, multikeyed indexed files with variable or fixed length records are supported.  C The SUBMIT/REMOTE command allows command files residing on a remote G node to be submitted for execution at the remote node. The command file E must be in the format expected by the node responsible for execution. C DECnet for OpenVMS also allows OpenVMS command files to be received   from other systems and executed.  D The DCL command EXCHANGE/NETWORK, allowing for the transfer of filesH to or from heterogeneous systems, is available. This command gives usersC the option to transfer file types between MS-DOS[R], ULTRIX or Dig- E ital UNIX, and OpenVMS systems regardless of record semantics. Unlike C the COPY command, which preserves file and record organization dur- E ing a file transfer, this command enables the user to modify file and ' record attributes during file transfer.    Downline System Loading     "                                  4       E DECnet for OpenVMS allows for the loading of an unattended system us- E ing the services provided by the Maintenance Operations Module (MOM). G MOM provides a set of maintenance operations over various types of cir- D cuits by using the Maintenance Operations Protocol (MOP). A loadableG system is a system that has a load device enabled for MOP service func- E tions and for which a properly formatted load file is supplied. Down- C line loading involves transferring a copy of the properly formatted C load file image of a remote node's operating system from an OpenVMS C node to the unattended target node. For example, DECnet for OpenVMS E permits the user to load routing software from the OpenVMS node down- C line to the target node. Load requests can come from the local DEC- E net for OpenVMS operator or from the target node. Downline loading is C supported for Compaq server products. However, this facility is not " supported over asynchronous lines.   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- F ing on loadable remote systems can be checkpointed to the host OpenVMSG file system and later restored to main memory in the remote node. These C features simplify the operation of network systems that do not have  mass storage devices.   7 This facility is not supported over asynchronous lines.    Upline Dumping  E Memory images of adjacent nodes connected by DECnet can be written or E dumped into a file on an OpenVMS system. This facility helps the sys- C tem manager in fault isolation on a remote system. This facility is * also supported for Compaq server products.  7 This facility is not supported over asynchronous lines.    Network Command Terminal        "                                  5       E The DCL command SET HOST allows a terminal user on one DECnet node to C establish a logical connection to another DECnet node that uses the C Command Terminal Protocol (CTERM). This connection makes the termi- C nal appear physically connected to the remote system and the opera- C tor can use all the standard system and network utilities supported C by that remote node. This capability is particularly useful for do- G ing remote program development and allows the terminal users on smaller H application-oriented systems to use the resources of larger development- oriented systems.    OpenVMS MAIL Utility  E The OpenVMS MAIL utility allows transmission of text messages between D users of a standalone system. The DECnet for OpenVMS software allowsE users to send and receive OpenVMS MAIL to or from users of other sys- 1 tems that operate within the same DECnet network.    OpenVMS PHONE Utility   C The OpenVMS PHONE utility allows users to send and receive data in- E teractively from one user's terminal to another user's terminal. DEC- F net increases the scope of OpenVMS PHONE to allow active users on dif-; ferent systems in the same network to exchange information.   
 Cluster Alias   E DECnet supports the ability to access some or all nodes in a VMSclus- D ter using a separate alias node address, while retaining the abilityE to address each node in the cluster individually. Not all network ob- F jects may be accessed using this mechanism. More than 64 nodes can op-D erate within a cluster, but the maximum number of nodes that are al-F lowed to participate in the cluster alias is 64. Refer to the VMSclus-E ter Software Product Description (SPD 29.78.xx) for relevant restric-  tions.  F DECnet and DECnet-Plus nodes can coexist in the same cluster. However,E DECnet and DECnet-Plus must have separate system disks, and they can- ! not share the same cluster alias.     "                                  6       C The DECnet for OpenVMS VAX cluster alias requires that at least one H node in the VMScluster be a VAX system licensed as a Full Function node.  E The DECnet for OpenVMS Alpha cluster alias requires that at least one @ node in the VMScluster be licensed as an Extended Function node.  C Refer to the DECnet-Plus documentation for details on configuring a  DECnet-Plus cluster alias.   Network Management  C The Network Control Program (NCP) performs three primary functions: F displaying statistical and error information, controlling network com-C ponents, and testing network operation. These functions can be per- F formed locally or executed at remote Phase IV nodes that support theseE functions. NCP allows for planning, building, tuning, and controlling F DECnet networks. NCP can be used to create and manage networks includ-E ing local node operation, remote node operation, circuits, lines, and  objects.  E An operator can display the status of DECnet activity at any Phase IV F node in the network. The user can choose to display statistics relatedD to the node itself or the communication lines attached to that node,E including traffic and error data. The local operator can also perform C many network control functions such as starting and stopping lines, 8 activating the local node, and downline loading systems.  H DECnet provides network event logging to a terminal device or disk file.F Any logged event can be used to monitor, diagnose, and tune a network.C The NCP utility can be used to enable and disable the event logging 	 facility.   C NCP can also be used to test components of the network. NCP enables E transmission and reception of test messages over individual lines ei- E ther between nodes or through other controller loopback arrangements. E The messages can then be compared for possible errors. NCP allows the C performance of a logical series of tests that will aid in isolating  network problems.    Integrated Interfaces   "                                  7       D DECnet interfaces are standard parts of the OpenVMS operating systemD for use on local, standalone systems. Users can develop programs andE procedures based upon these interfaces for such functions as file ac- D cess and task-to-task communication on individual systems. Since theC DECnet interfaces stay the same, the programs and procedures devel- G oped on an individual system can be used in a network environment with-  out being modified.                                                                   "                                  8        Communications Options  D DECnet for OpenVMS uses Ethernet and FDDI communications controllers& to interface with other network nodes.   DECnet for OpenVMS Operation  F DECnet for OpenVMS VAX is implemented under the OpenVMS operating sys-E tem as an Ancillary Control Process (ACP) and a network device driver C with executive-level components and user-level programs supplied by  Compaq.   D The normal OpenVMS protection has been incorporated in the operationD of DECnet for OpenVMS. For example, incoming connects including fileE access and file transfer requests are protected by the normal OpenVMS F login and file protection mechanisms. Outgoing connects including fileD access and file transfer requests can include user password informa-E tion that is implicitly specified via NCP, or explicitly specified by - the user for verification on the remote node.   0 DECnet for OpenVMS Configuration and Performance  E The process of configuring a DECnet node is based primarily on trade- H offs of cost, performance, and functionality while satisfying the user'sF application requirements. It can be expected that network applicationsE will range from low-speed, low-cost situations to those of relatively C high performance and functionality. The performance of a given DEC- C net for OpenVMS node is a function not only of the expected network C traffic and resultant processing, but also of the amount of concur- E rent processing 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  , o  Number of device interrupts per unit time  ( o  Communication line(s) characteristics   o  Number and size of buffers   - o  Message size and frequency of transmission   "                                  9        o  Applications in use  E o  Size and frequency of route-through traffic (on DECnet for OpenVMS     VAX routing nodes only)  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,D but will never exceed, the actual line speed. The reason is that theC actual throughput is a function of many factors, including the line D quality, protocol overhead, topology, and network application(s), as* well as the factors cited in this section.   INSTALLATION  F For the first installation of this product, Compaq recommends the pur-C chase of Compaq's Installation Services. These services provide for C installation of the software product by an experienced Compaq Soft-  ware Specialist.   Customer Responsibilities   : Before Compaq can install the software, the customer must:  E o  Ensure that the system meets the minimum hardware and software re-_2    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- F    tomer equipment or facilities to which Compaq's communication hard-!    ware or software will connect.c  C o  Designate one adjacent node to verify installation/connectivity.m  E o  Make available for a reasonable period of time, as mutually agreed.E    upon by Compaq and the customer, all hardware communication facil-l?    ities and terminals that are to be used during installation.   C Delays caused by any failure to meet these responsibilities will bep; charged at the then prevailing rate for time and materials.,  "                                 10    a  B Installation for DECnet for OpenVMS will consist of the following:  C o  Verification that all components of DECnet for OpenVMS have beent    received.  C o  Verification that the necessary versions of the OpenVMS software #    and documentation are available.o  5 o  Verification of the appropriate SYSGEN parameters.s  F    Note: Should a Compaq Software Specialist be required to modify theC    previously installed operating system parameters, a time and ma-M    terials charge will apply.h  8 o  Create any necessary DECnet accounts and directories.  C o  Enable software via License Product Authorization Key (PAK) reg-e
    istration.P  2 o  Define and create a local node DECnet database.  C o  Modify the system's startup command procedure to include startupu%    of the DECnet for OpenVMS network.e  D o  Verify the proper installation of DECnet for OpenVMS 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-  bility of the customer.o   HARDWARE REQUIREMENTSm  G Refer to the OpenVMS Operating System Software Product Description (SPD D 25.01.xx) for hardware requirements and processor support. ReferenceC can be made to the configuration charts listed in the OpenVMS Oper-iG ating System SPD. For general device or controller descriptions, pleaseg6 refer to the Networks and Communications Buyers Guide.      "                                 11 A  i   CLUSTER ENVIRONMENTn  E DECnet for OpenVMS is fully supported when installed on any valid andyC licensed VMScluster configuration without restrictions. The SYSTEMSiF SUPPORTED section of the OpenVMS Operating System Software Product De-E scription (SPD 25.01.xx) details any special hardware required or note supported by this product.  G VMScluster software provides a distributed computing environment acrossoC a highly integrated set of VAX, Alpha, and/or MicroVAX systems that F operate as a single environment. VMScluster members can share many re-E sources such as disk and tape storage, CPU resources, and system man-XC agement operations. Within this highly integrated environment, sys-fF tems retain their independence because they use local, memory-residentG copies of the OpenVMS operating system. Thus, members can boot and failn5 independently while benefiting from common resources.t  E VMScluster configurations are fully described in the VMScluster Soft- G ware Product Description (29.78.xx) and include CI, Ethernet, and Mixeda Interconnect configurations.   SOFTWARE REQUIREMENTSo  * DECnet for OpenVMS requires the following:  ' o  OpenVMS Operating System Version 7.3d  0 Only the Base OpenVMS Kit component is required.   GROWTH CONSIDERATIONS   D The minimum hardware/software requirements for any future version ofC this product may be different from the requirements for the current  version.            "                                 12 a  n   DISTRIBUTION MEDIA  = DECnet for OpenVMS VAX is distributed on the following media:s   o  TK50 streaming tape  	 o  CD-ROMe  2 DECnet for OpenVMS Alpha is distributed on CD-ROM.   ORDERING INFORMATION  E DECnet for OpenVMS is a layered product that ships with the Alpha andn VAX operating system.   E DECnet for OpenVMS licenses also include the right to use DECnet-Plusn for OpenVMS.  F Base License Option Numbers for DECnet for OpenVMS VAX are as follows:  # End Node                QL-D04A*-AA   # Full Function           QL-D05A*-AAe  # End Node to Full        QL-D09A*-AA  Function Upgrade  D Base License Option Numbers for DECnet for OpenVMS Alpha are as fol- lows:a  # End System              QL-MTFA*-AAE  # Extended Function       QL-MTGA*-AAm  # End System to Ex-       QL-MTHA*-AAl tended Functionr Upgradee   *  Denotes processor variant.m  "                                 13 h  s   SOFTWARE LICENSING  E The DECnet for OpenVMS License provides the right to use the softwareeD product on a single CPU and includes the delivery of a License Prod-B uct Authorization Key (PAK) to enable DECnet for OpenVMS software.  D To use this software product on additional CPUs, users must purchase) a Single-Use License Option for each CPU.   G The DECnet for OpenVMS VAX End Node and the DECnet for OpenVMS End Sys- D tem License grants the right to use all the DECnet features with theC exception of cluster alias support. The DECnet for OpenVMS VAX Full C Function and the DECnet for OpenVMS Alpha Extended Function license & is required for cluster alias support.  C This software is furnished under the licensing provisions of CompaqgE Computer Corporation's Standard Terms and Conditions. For more infor-eD mation about Compaq's licensing terms and policies, contact your lo- cal Compaq office.  # LICENSE MANAGEMENT FACILITY SUPPORTT  > This product supports the OpenVMS License Management Facility.  E License units for this product are allocated on a CPU capacity basis.n  E For more information on the License Management Facility, refer to theaD OpenVMS Operating System Software Product Description (SPD 25.01.xx)G or the License Management Facility manual of the OpenVMS operating sys-  tem documentation set.   SOFTWARE PRODUCT SERVICESe  F A variety of service options are available. For more information, con- tact your local Compaq office.          "                                 14 t  v   SOFTWARE WARRANTYr  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.e  F The above information is valid at time of release. Please contact your8 local Compaq office for the most up-to-date information.  * Appendix A: DECnet for OpenVMS VAX Routing  # Routing Capabilities on OpenVMS VAX   C A DECnet for OpenVMS VAX node must function as a routing node when-SD ever multiple circuits are used by that node. Routing nodes maintainJ information on the paths to other nodes in the network. DECnet for OpenVMSD VAX end nodes provide all the capabilities of DECnet for OpenVMS VAXE routing nodes with the exception that end nodes cannot route messagesUE on behalf of other nodes in the network. Since end nodes do not routeOI messages, they do not need to maintain routing information. Consequently,tC end nodes initiate less overhead message traffic than routing nodestA and, therefore, consume less processing power than routing nodes.   E Adaptive Routing is the mechanism that routing nodes use to ``adapt''hF or choose other physical paths if the physical paths the routing nodes# are using fail or change line cost.   E In addition to adaptive routing, DECnet for OpenVMS VAX supports area D routing. Area routing is a method by which DECnet can send and routeC messages between the nodes in different areas of the network. Up touF 63 areas with up to 1,023 nodes per area are allowed. The network man-G ager has the option of separating a network into areas. Area-based DEC- E net networks are hierarchical networks and some restrictions apply to D communications from nodes in one area to nodes in another area. How-D ever, it is not required that all nodes in the network be DECnet forE OpenVMS VAX or even Phase IV nodes. Proper network planning is essen- I tial when using area routing or configuring large networks. Valid topolo-p, gies are the responsibility of the customer.    "                                 15 n     D Note: Only 32 routers (dedicated and/or host based) are supported on an extended LAN.  C A DECnet for OpenVMS VAX node has the ability to communicate with a C remote node over multiple circuits simultaneously, as long as thosetE circuits are all of equal cost and provide the lowest cost path. DEC-eE net for OpenVMS VAX routing nodes will split transmission of a packetsC load to a destination node via multiple paths if those paths are ofpC equal lowest cost. This capability is called Equal Cost Path Split-fC ting. This feature can increase throughput of data by using all the D best available paths. To take full advantage of this capability, allC intermediate routing nodes should also support this feature and allt; destination nodes must support out-of-order packet caching.t  F The above information is valid at time of release. Please contact your8 local Compaq office for the most up-to-date information.  "  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-e nologies Group, L.P.  D All other product names mentioned herein may be trademarks or regis-/ tered trademarks of their respective companies.r  F Confidential computer software. Valid license from Compaq required forC possession, use, or copying. Consistent with FAR 12.211 and 12.212,lH Commercial Computer Software, Computer Software Documentation, and Tech-C nical Data for Commercial Items are licensed to the U.S. Governmentu+ under vendor's standard commercial license.e  E Compaq shall not be liable for technical or editorial errors or omis-oC sions contained herein. The information in this document is subjects to change without notice.h          "                                 16 l                                                                                     "                                 17