                Software
       Product        Description   I       ___________________________________________________________________   H       PRODUCT NAME: HP DECnet for OpenVMS Integrity servers Version 8.4 >       SPD 48.48.13               and OpenVMS Alpha Version 8.4  M       Note: This Software Product Description (SPD) covers DECnet for OpenVMS K       on Alpha and Integrity servers. Unless explicitly noted, the features L       described apply to both platforms. Licenses and part numbers are plat-M       form specific and are noted in the Ordering Information section of this 
       SPD.         DESCRIPTION   I       DECnet for OpenVMS on Alpha and Integrity servers allows a suitably J       configured OpenVMS system to participate as an end node. With properI       network planning, DECnet networks can contain up to 1,023 nodes per 2       network area and up to 63 areas per network.  L       DECnet for OpenVMS end node or Extended function products are licensedJ       separately for OpenVMS systems. The DECnet for OpenVMS License Prod-L       uct Authorization Key (PAK), when registered on an OpenVMS system, en-E       ables communication between systems using the DECnet protocols.   I       DECnet for OpenVMS has been implemented in accordance with Phase IV K       of the Digital Network Architecture (DNA) product. DECnet for OpenVMS I       is a layered product that ships with the Alpha and Integrity server L       operating system. On OpenVMS Alpha systems, the DECnet for OpenVMS Li-J       cense provides the right to use the software product on a single CPUL       and includes the delivery of a License Product Authorization Key (PAK)M       to enable DECnet for OpenVMS software. On OpenVMS Integrity server sys- L       tems, the DECnet for OpenVMS license is part of the Base Operating En-J       vironment (BOE), which is licensed on a per core license basis. DEC-I       net for OpenVMS is warranted only for use with Phase IV and DECnet- :       Plus (formerly DECnet/OSI) products supported by HP.    I                                                                March 2010        H       HP DECnet for OpenVMS Integrity servers Version 8.4   SPD 48.48.13#       and OpenVMS Alpha Version 8.4   I       DECnet for OpenVMS offers task-to-task communications, file manage- L       ment, downline system and task loading, network command terminals, andI       network resource sharing capabilities using the Digital Network Ar- J       chitecture (DNA) protocols. DECnet for OpenVMS communicates with ad-<       jacent and nonadjacent Phase IV and DECnet-Plus nodes.  L       OpenVMS programs written in MACRO and native mode high-level languages2       can use DECnet for OpenVMS VAX capabilities.  J       The network functions available to a DECnet for OpenVMS user depend,I       in part, on the configuration of the rest of the network. Each DEC- M       net product offers its own subset of Digital Network Architecture (DNA) J       functions and its own set of features to the user. Networks consist-J       ing entirely of DECnet for OpenVMS Phase IV nodes have all the func-L       tions described in this SPD. The functions available to users on mixedK       networks can be determined by a comparison of the SPDs for the appro-        priate DECnet products.   .       Standard DECnet for OpenVMS Capabilities          Task-to-Task Communication  I       For most applications, task-to-task communication can be programmed L       in a transparent manner where the remote task is treated as a full du-I       plex, record-oriented device. Transparent operation is provided via L       the following interfaces: System Service calls, Record Management Sys-I       tem (RMS) calls (OPEN, GET, PUT, and CLOSE) and high-level language K       I/O statements (which are mapped to RMS calls). A nontransparent mode J       of task-to-task communication is offered by means of the System Ser-I       vice interface that extends the capabilities provided by the trans- L       parent mode. These capabilities include support for interrupt messages,       and multiple inbound connect requests.  M       Using DECnet for OpenVMS, an OpenVMS program can exchange messages with I       other user programs. The two user programs can be on the same node, J       on adjacent Phase IV or DECnet-Plus nodes, or on any two nonadjacentJ       Phase IV or DECnet-Plus nodes in the same network connected by PhaseI       IV or DECnet-Plus routing nodes. DECnet for OpenVMS imposes no spe- 4       cial data formatting requirements on the user.  (                                        2       H       HP DECnet for OpenVMS Integrity servers Version 8.4   SPD 48.48.13#       and OpenVMS Alpha Version 8.4          Network Resource Access   K       File Access - File access is supported to and from remote DECnet sys- M       tems using RMS. User programs can sequentially read, create, and delete        files on a remote node.   L       Record Access - User programs can perform record level operations suchN       as GET, PUT, UPDATE, DELETE, FIND, and REWIND to access and modify filesI       residing on a remote OpenVMS node. In addition to sequential access K       to a file, several other access methods are supported through RMS us- I       ing DECnet for OpenVMS. These methods include random access by rel- N       ative record number, random access by key value, random access by RecordG       File Address (RFA), and block I/O access by virtual block number.          Proxy Access  K       Remote users can have access to up to 15 proxy accounts on a specific J       remote system. One proxy account should be designated as the default)       proxy account on the remote system.   &       Command Language File Management  I       Most OpenVMS Digital Command Language (DCL) commands can be used to K       perform network file operations. These commands include: ANALYZE, AP- J       PEND, BACKUP, CLOSE, CONVERT, COPY, CREATE, DELETE, DIFFERENCES, DI-O       RECTORY, DUMP, OPEN, PRINT, PURGE, READ, SEARCH, SUBMIT, TYPE, and WRITE. M       The operation of these commands is transparent except for commands that W       invoke processing on a specific system (that is, SUBMIT/REMOTE and PRINT/REMOTE). J       Only a node name added to a file specification is required to invoke9       the network capabilities via one of these commands.   K       Using the COPY command, a user can transfer sequential, relative, and L       indexed-sequential (ISAM) files between DECnet nodes that support com-N       patible file structures and record formats. Sequential or relative filesL       with fixed length, variable length, or variable length with fixed con-M       trol field records can be transferred between two OpenVMS systems. Sim- L       ilarly, multikeyed indexed files with variable or fixed length records       are supported.    (                                        3       H       HP DECnet for OpenVMS Integrity servers Version 8.4   SPD 48.48.13#       and OpenVMS Alpha Version 8.4   I       The SUBMIT/REMOTE command allows command files residing on a remote M       node to be submitted for execution at the remote node. The command file K       must be in the format expected by the node responsible for execution. I       DECnet for OpenVMS also allows OpenVMS command files to be received &       from other systems and executed.  J       The DCL command EXCHANGE/NETWORK, allowing for the transfer of filesN       to or from heterogeneous systems, is available. This command gives usersI       the option to transfer file types between MS-DOS[R], ULTRIX or Dig- K       ital UNIX, and OpenVMS systems regardless of record semantics. Unlike I       the COPY command, which preserves file and record organization dur- K       ing a file transfer, this command enables the user to modify file and -       record attributes during file transfer.          Downline System Loading   K       DECnet for OpenVMS allows for the loading of an unattended system us- K       ing the services provided by the Maintenance Operations Module (MOM). M       MOM provides a set of maintenance operations over various types of cir- J       cuits by using the Maintenance Operations Protocol (MOP). A loadableM       system is a system that has a load device enabled for MOP service func- K       tions and for which a properly formatted load file is supplied. Down- I       line loading involves transferring a copy of the properly formatted I       load file image of a remote node's operating system from an OpenVMS I       node to the unattended target node. For example, DECnet for OpenVMS K       permits the user to load routing software from the OpenVMS node down- I       line to the target node. Load requests can come from the local DEC- K       net for OpenVMS operator or from the target node. Downline loading is J       supported for HP server products. However, this facility is not sup-%       ported over asynchronous lines.          Downline Task Loading   L       Initial task images for loadable systems can be stored on OpenVMS fileK       system devices and loaded into remote nodes. Programs already execut- L       ing on loadable remote systems can be checkpointed to the host OpenVMSM       file system and later restored to main memory in the remote node. These I       features simplify the operation of network systems that do not have        mass storage devices.   (                                        4       H       HP DECnet for OpenVMS Integrity servers Version 8.4   SPD 48.48.13#       and OpenVMS Alpha Version 8.4   =       This facility is not supported over asynchronous lines.          Upline Dumping  K       Memory images of adjacent nodes connected by DECnet can be written or K       dumped into a file on an OpenVMS system. This facility helps the sys- I       tem manager in fault isolation on a remote system. This facility is ,       also supported for HP server products.  =       This facility is not supported over asynchronous lines.                                                             (                                        5       H       HP DECnet for OpenVMS Integrity servers Version 8.4   SPD 48.48.13#       and OpenVMS Alpha Version 8.4          Network Command Terminal  K       The DCL command SET HOST allows a terminal user on one DECnet node to I       establish a logical connection to another DECnet node that uses the I       Command Terminal Protocol (CTERM). This connection makes the termi- I       nal appear physically connected to the remote system and the opera- I       tor can use all the standard system and network utilities supported I       by that remote node. This capability is particularly useful for do- M       ing remote program development and allows the terminal users on smaller N       application-oriented systems to use the resources of larger development-       oriented systems.          OpenVMS MAIL Utility  K       The OpenVMS MAIL utility allows transmission of text messages between J       users of a standalone system. The DECnet for OpenVMS software allowsK       users to send and receive OpenVMS MAIL to or from users of other sys- 7       tems that operate within the same DECnet network.          OpenVMS PHONE Utility   I       The OpenVMS PHONE utility allows users to send and receive data in- K       teractively from one user's terminal to another user's terminal. DEC- L       net increases the scope of OpenVMS PHONE to allow active users on dif-A       ferent systems in the same network to exchange information.          Cluster Alias   K       DECnet supports the ability to access some or all nodes in a VMSclus- J       ter using a separate alias node address, while retaining the abilityK       to address each node in the cluster individually. Not all network ob- L       jects may be accessed using this mechanism. More than 64 nodes can op-J       erate within a cluster, but the maximum number of nodes that are al-L       lowed to participate in the cluster alias is 64. Refer to the VMSclus-K       ter Software Product Description (SPD 29.78.xx) for relevant restric-        tions.  L       DECnet and DECnet-Plus nodes can coexist in the same cluster. However,K       DECnet and DECnet-Plus must have separate system disks, and they can- '       not share the same cluster alias.   (                                        6       H       HP DECnet for OpenVMS Integrity servers Version 8.4   SPD 48.48.13#       and OpenVMS Alpha Version 8.4   K       The DECnet for OpenVMS Alpha cluster alias requires that at least one F       node in the VMScluster be licensed as an Extended Function node.  I       Refer to the DECnet-Plus documentation for details on configuring a         DECnet-Plus cluster alias.         Network Management  I       The Network Control Program (NCP) performs three primary functions: L       displaying statistical and error information, controlling network com-I       ponents, and testing network operation. These functions can be per- L       formed locally or executed at remote Phase IV nodes that support theseK       functions. NCP allows for planning, building, tuning, and controlling L       DECnet networks. NCP can be used to create and manage networks includ-K       ing local node operation, remote node operation, circuits, lines, and        objects.  K       An operator can display the status of DECnet activity at any Phase IV L       node in the network. The user can choose to display statistics relatedJ       to the node itself or the communication lines attached to that node,K       including traffic and error data. The local operator can also perform I       many network control functions such as starting and stopping lines, >       activating the local node, and downline loading systems.  N       DECnet provides network event logging to a terminal device or disk file.L       Any logged event can be used to monitor, diagnose, and tune a network.I       The NCP utility can be used to enable and disable the event logging        facility.   I       NCP can also be used to test components of the network. NCP enables K       transmission and reception of test messages over individual lines ei- K       ther between nodes or through other controller loopback arrangements. K       The messages can then be compared for possible errors. NCP allows the I       performance of a logical series of tests that will aid in isolating        network problems.          Integrated Interfaces       (                                        7       H       HP DECnet for OpenVMS Integrity servers Version 8.4   SPD 48.48.13#       and OpenVMS Alpha Version 8.4   J       DECnet interfaces are standard parts of the OpenVMS operating systemJ       for use on local, standalone systems. Users can develop programs andK       procedures based upon these interfaces for such functions as file ac- J       cess and task-to-task communication on individual systems. Since theI       DECnet interfaces stay the same, the programs and procedures devel- M       oped on an individual system can be used in a network environment with-        out being modified.          Communications Options  J       DECnet for OpenVMS uses Ethernet and FDDI communications controllersL       to interface with other network nodes. LAN failover sets are also sup-       ported on Alpha.         LAN Failover  L       DECnet for OpenVMS provides support for OpenVMS LAN failover sets. LANL       failover provides a mechanism to protect LAN applications against net-J       work interface card (NIC) failures. A LAN failover set is defined byM       the system manager and consists of a set of like adapters (all the same J       class) that support LAN failover. One adapter in the failover set isN       used for LAN traffic; one or more other adapters in the set remain idle.J       If the active adapter fails, one of the idle adapters in the set au-M       tomatically takes over LAN traffic using the same address as the failed        adapter.  "       DECnet for OpenVMS Operation  J       DECnet for OpenVMS is implemented under the OpenVMS operating systemL       as an Ancillary Control Process (ACP) and a network device driver withH       executive-level components and user-level programs supplied by HP.  J       The normal OpenVMS protection has been incorporated in the operationJ       of DECnet for OpenVMS. For example, incoming connects including fileK       access and file transfer requests are protected by the normal OpenVMS L       login and file protection mechanisms. Outgoing connects including fileJ       access and file transfer requests can include user password informa-K       tion that is implicitly specified via NCP, or explicitly specified by 3       the user for verification on the remote node.   (                                        8       H       HP DECnet for OpenVMS Integrity servers Version 8.4   SPD 48.48.13#       and OpenVMS Alpha Version 8.4   6       DECnet for OpenVMS Configuration and Performance  K       The process of configuring a DECnet node is based primarily on trade- N       offs of cost, performance, and functionality while satisfying the user'sL       application requirements. It can be expected that network applicationsK       will range from low-speed, low-cost situations to those of relatively I       high performance and functionality. The performance of a given DEC- I       net for OpenVMS node is a function not only of the expected network I       traffic and resultant processing, but also of the amount of concur- K       rent processing specific to that node. Thus, node performance depends         on many factors including:         o  CPU types  #       o  Number and type of devices   J       o  In an SMP environment, the overall load on the primary CPU is es-I          pecially relevant because the Phase IV NETACP can only be sched-           uled on that CPU.  2       o  Number of device interrupts per unit time  .       o  Communication line(s) characteristics  #       o  Number and size of buffers   3       o  Message size and frequency of transmission          o  Applications in use  4       o  Size and frequency of route-through traffic  L       It is important to note that the rate at which user data can be trans-L       mitted (throughput) over a communications line can sometimes approach,J       but will never exceed, the actual line speed. The reason is that theI       actual throughput is a function of many factors, including the line J       quality, protocol overhead, topology, and network application(s), as0       well as the factors cited in this section.    (                                        9       H       HP DECnet for OpenVMS Integrity servers Version 8.4   SPD 48.48.13#       and OpenVMS Alpha Version 8.4          INSTALLATION  L       For the first installation of this product, HP recommends the purchaseI       of HP's Installation Services. These services provide for installa- I       tion of the software product by an experienced HP Software Special- 
       ist.         Customer Responsibilities   <       Before HP can install the software, the customer must:  K       o  Ensure that the system meets the minimum hardware and software re- 8          quirements (as specified in the relevant SPDs).  J       o  Prior to installing HP hardware or software, obtain, install, andK          demonstrate as operational any modems and other necessary customer N          equipment or facilities to which HP's communication hardware or soft-          ware will connect.   I       o  Designate one adjacent node to verify installation/connectivity.   K       o  Make available for a reasonable period of time, as mutually agreed K          upon by HP and the customer, all hardware communication facilities ?          and terminals that are to be used during installation.   I       Delays caused by any failure to meet these responsibilities will be A       charged at the then prevailing rate for time and materials.   H       Installation for DECnet for OpenVMS will consist of the following:  I       o  Verification that all components of DECnet for OpenVMS have been           received.  I       o  Verification that the necessary versions of the OpenVMS software )          and documentation are available.   ;       o  Verification of the appropriate SYSGEN parameters.   M          Note: Should a HP Software Specialist be required to modify the pre- J          viously installed operating system parameters, a time and materi-          als charge will apply.   >       o  Create any necessary DECnet accounts and directories.  (                                       10       H       HP DECnet for OpenVMS Integrity servers Version 8.4   SPD 48.48.13#       and OpenVMS Alpha Version 8.4   I       o  Enable software via License Product Authorization Key (PAK) reg-           istration.   8       o  Define and create a local node DECnet database.  I       o  Modify the system's startup command procedure to include startup +          of the DECnet for OpenVMS network.   J       o  Verify the proper installation of DECnet for OpenVMS by running aC          series of tests to show connectivity to a designated node.   I       Connectivity to all other nodes within the network is the responsi-        bility of the customer.          HARDWARE REQUIREMENTS   L       Refer to the HP OpenVMS for Integrity Servers and HP OpenVMS Alpha Op-K       erating Systems Software Product Description (SPD 82.35.xx) for hard- K       ware requirements and processor support. Reference can be made to the J       configuration charts listed in the OpenVMS Operating System SPD. ForI       general device or controller descriptions, please refer to the Net- ,       works and Communications Buyers Guide.         CLUSTER ENVIRONMENT   K       DECnet for OpenVMS is fully supported when installed on any valid and I       licensed VMScluster configuration without restrictions. The SYSTEMS L       SUPPORTED section of the HP OpenVMS for Integrity Servers and HP Open-N       VMS Alpha Operating Sy stems Software Product Description (SPD 82.35.xx)J       details any special hardware required or not supported by this prod-
       uct.  J       OpenVMScluster software provides a distributed computing environmentJ       across a highly integrated set of Integrity server and Alpha systemsL       that operate as a single environment. OpenVMScluster members can shareK       many resources such as disk and tape storage, CPU resources, and sys- K       tem management operations. Within this highly integrated environment, O       systems retain their independence because they use local, memory-resident     (                                       11       H       HP DECnet for OpenVMS Integrity servers Version 8.4   SPD 48.48.13#       and OpenVMS Alpha Version 8.4   M       copies of the OpenVMS operating system. Thus, members can boot and fail ;       independently while benefiting from common resources.   M       OpenVMScluster configurations are fully described in the OpenVMScluster .       Software Product Description (29.78.xx).         SOFTWARE REQUIREMENTS   0       DECnet for OpenVMS requires the following:  7       o  OpenVMS Operating System Version 8.4 for Alpha   C       o  OpenVMS Operating System Version 8.4 for Integrity servers   6       Only the Base OpenVMS Kit component is required.         GROWTH CONSIDERATIONS   J       The minimum hardware/software requirements for any future version ofI       this product may be different from the requirements for the current        version.         DISTRIBUTION MEDIA  8       DECnet for OpenVMS Alpha is distributed on CD-ROM.  K       DECnet for OpenVMS Integrity server system is distributed on DVD with +       the Base Operating Environment (BOE).          SOFTWARE LICENSING  K       On OpenVMS Alpha systems, the DECnet for OpenVMS License provides the L       right to use the software and includes the delivery of a License Prod-K       uct Authorization Key (PAK) to enable DECnet for OpenVMS software. On J       OpenVMS Integrity servers, the DECnet for OpenVMS license is part ofI       the Base Operating Environment, which is licensed on a per core li-        cense basis.      (                                       12       H       HP DECnet for OpenVMS Integrity servers Version 8.4   SPD 48.48.13#       and OpenVMS Alpha Version 8.4   J       To use this software product on additional CPUs, users must purchaseK       a Single-Use License Option for each CPU on OpenVMS Alpha systems. On J       OpenVMS Integrity server systems, users must purchase additional PCL(       license units for each active CPU.  K       The DECnet for OpenVMS End System License grants the right to use all J       the DECnet features with the exception of cluster alias support. TheJ       DECnet for OpenVMS Extended Function license is required for cluster       alias support.  J       This software is furnished under the licensing provisions of HP Com-J       puter Corporation's Standard Terms and Conditions. For more informa-I       tion about HP's licensing terms and policies, contact your local HP 
       office.   )       LICENSE MANAGEMENT FACILITY SUPPORT   D       This product supports the OpenVMS License Management Facility.  J       License units for this product are allocated on a CPU capacity basisK       on OpenVMS Alpha. On OpenVMS Integrity servers, DECnet is licensed on I       a Per Core License (PCL) basis, as part of the Base Operating Envi-        ronment.  K       For more information on the License Management Facility, refer to the J       OpenVMS Operating System Software Product Description (SPD 25.01.xx)M       or the License Management Facility manual of the OpenVMS operating sys-        tem documentation set.         ORDERING INFORMATION  K       DECnet for OpenVMS is a layered product that ships with the Alpha op- B       erating system and with the BOE on Integrity server systems.  K       DECnet for OpenVMS licenses also include the right to use DECnet-Plus        for OpenVMS.  L       Base License Option Numbers for DECnet for OpenVMS Alpha and Integrity       servers are as follows:   (                                       13       H       HP DECnet for OpenVMS Integrity servers Version 8.4   SPD 48.48.13#       and OpenVMS Alpha Version 8.4   I       ___________________________________________________________________ I       _____________________HP_OpenVMS_Alpha_Licenses_____________________   .       End System                   QL-MTFA*-AA.       Extended Function            QL-MTGA*-AA.       End System to Extended       QL-MTHA*-AAI       Function_Upgrade___________________________________________________   "       * Denotes processor variant.  I       ___________________________________________________________________ I       _________________HP_OpenVMS_Integrity_Licenses[1]__________________   9       End System                   Included in OE license *       Extended Function            BA406ACI       ___________________________________________________________________ D       [1]Update licenses not available; updates available through SWI       Updates_Service.___________________________________________________          Media and Documentation   K       Product binary kits and online documentation are delivered on consol- @       idated media libraries. Delivery model varies by platform.  I       ___________________________________________________________________ I       __________HP_OpenVMS_Alpha_Media_and_Online_Documentation__________   .       Software Layered Products    QA-03XAA-H8       Library Package[1].       Software Layered Products    QA-5G98A-H8       and Operating System       Library Package[1]I       ___________________________________________________________________ I       [1]Quarterly_Software_Updates_Service_is_available.________________             (                                       14       H       HP DECnet for OpenVMS Integrity servers Version 8.4   SPD 48.48.13#       and OpenVMS Alpha Version 8.4   I       ___________________________________________________________________ I       ______HP_OpenVMS_Integrity_Media_and_Online_Documentation[1]_______   .       Base Operating Environ-      BA322AA#AJR
       mentI       ___________________________________________________________________ H       [1]Product ships on Layered Products Library media included in allF       Operating Environment media kits, available with initial OpenVMSI       OE_order.__________________________________________________________   J       NOTE: If you are adding a layered product to an existing OpenVMS In-J       tegrity system and do not have the latest software revision on site,I       please contact your local Sales Rep to request a Special Media kit.          SOFTWARE PRODUCT SERVICES   J       Support for this product is provided only under a prior version sup-H       port contract. For more information, contact your local HP office.           SOFTWARE WARRANTY   K       This software is provided by HP with a 90 day comformance warranty in J       accordance with the HP warranty terms applicable to the license pur-       chase.  L       The above information is valid at time of release. Please contact your:       local HP office for the most up-to-date information.  @        Copyright 2010 Hewlett-Packard Development Company, L.P.  M       Confidential computer software. Valid license from HP required for pos- J       session, use or copying. Consistent with FAR 12.211 and 12.212, Com-K       mercial Computer Software, Computer Software Documentation, and Tech- I       nical Data for Commercial Items are licensed to the U.S. Government 1       under vendor's standard commercial license.         (                                       15       H       HP DECnet for OpenVMS Integrity servers Version 8.4   SPD 48.48.13#       and OpenVMS Alpha Version 8.4   K       The information contained herein is subject to change without notice. K       The only warranties for HP products and services are set forth in the J       express warranty statements accompanying such products and services.K       Nothing herein should be construed as constituting an additional war- N       ranty. HP shall not be liable for technical or editorial errors or omis-       sions contained herein.                                                                     (                                       16