HP DECnet Phase IV for OpenVMS Alpha and OpenVMS I64, Version 8.3

ManualsBrandsHP ManualsSoftwareOpenVMS 8.4

Software

Product

Description

PRODUCT NAME: HP DECnet for OpenVMS Alpha and OpenVMS I64, Version 8.3 SPD 48.48.11

Note: This Software Product Description (SPD) covers

DECnet for OpenVMS on Alpha and I64 platforms. Un-

less explicitly noted, the features described apply to both

platforms. Licenses and part numbers are platform spe-

ciﬁc and are noted in the Ordering Information section

of this SPD.

DESCRIPTION

DECnet for OpenVMS on Alpha and I64 allows a suit-

ably conﬁgured OpenVMS system to participate as an

end node. With proper network planning, DECnet net-

works can contain up to 1,023 nodes per network area

and up to 63 areas per network.

DECnet for OpenVMS end node or Extended function

products are licensed separately for OpenVMS systems.

The DECnet for OpenVMS License Product Authoriza-

tion Key (PAK), when registered on an OpenVMS sys-

tem, enables communication between systems using

the DECnet protocols.

DECnet for OpenVMS has been implemented in accor-

dance with Phase IV of the Digital Network Architec-

ture (DNA) product. DECnet for OpenVMS is a lay-

ered product that ships with the Alpha and I64 operat-

ing system. On OpenVMS Alpha systems, the DEC-

net for OpenVMS License provides the right to use the

software product on a single CPU and includes the de-

livery of a License Product Authorization Key (PAK) to

enable DECnet for OpenVMS software. On OpenVMS

I64 systems, the DECnet for OpenVMS license is part

of the Foundation Operating Environment (FOE), the

Enterprise Operating Environment (EOE) and the Mis-

sion Critical Operating Environment (MCOE), which are

licensed on a per processor license basis. DECnet

for OpenVMS is warranted only for use with Phase IV

and DECnet-Plus (formerly DECnet/OSI) products sup-

ported by HP.

DECnet for OpenVMS offers task-to-task communica-

tions, ﬁle management, downline system and task load-

ing, network command terminals, and network resource

sharing capabilities using the Digital Network Architec-

ture (DNA) protocols. DECnet for OpenVMS commu-

nicates with adjacent and nonadjacent Phase IV and

DECnet-Plus nodes.

OpenVMS programs written in MACRO and na-

tive mode high-level languages can use DECnet for

OpenVMS VAX capabilities.

The network functions available to a DECnet for

OpenVMS user depend, in part, on the conﬁguration of

the rest of the network. Each DECnet product offers its

own subset of Digital Network Architecture (DNA) func-

tions and its own set of features to the user. Networks

consisting entirely of DECnet for OpenVMS Phase IV

nodes have all the functions described in this SPD. The

functions available to users on mixed 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

For most applications, task-to-task communication can

be programmed in a transparent manner where the re-

mote task is treated as a full duplex, record-oriented

device. Transparent operation is provided via the fol-

lowing interfaces: System Service calls, Record Man-

agement System (RMS) calls (OPEN, GET, PUT, and

CLOSE) and high-level language I/O statements (which

are mapped to RMS calls). A nontransparent mode of

June 2006

Summary of content (6 pages)

PAGE 1
Software Product Description PRODUCT NAME: HP DECnet for OpenVMS Alpha and OpenVMS I64, Version 8.3 SPD 48.48.11 Note: This Software Product Description (SPD) covers DECnet for OpenVMS on Alpha and I64 platforms. Unless explicitly noted, the features described apply to both platforms. Licenses and part numbers are platform specific and are noted in the Ordering Information section of this SPD.
PAGE 2
HP DECnet for OpenVMS Alpha and OpenVMS I64, Version 8.3 task-to-task communication is offered by means of the System Service interface that extends the capabilities provided by the transparent mode. These capabilities include support for interrupt messages and multiple inbound connect requests. SPD 48.48.11 two OpenVMS systems. Similarly, multikeyed indexed files with variable or fixed length records are supported.
PAGE 3
HP DECnet for OpenVMS Alpha and OpenVMS I64, Version 8.3 This facility is not supported over asynchronous lines. SPD 48.48.11 The Network Control Program (NCP) performs three primary functions: displaying statistical and error information, controlling network components, and testing network operation. These functions can be performed locally or executed at remote Phase IV nodes that support these functions. NCP allows for planning, building, tuning, and controlling DECnet networks.
PAGE 4
HP DECnet for OpenVMS Alpha and OpenVMS I64, Version 8.3 more other adapters in the set remain idle. If the active adapter fails, one of the idle adapters in the set automatically takes over LAN traffic using the same address as the failed adapter. SPD 48.48.11 INSTALLATION For the first installation of this product, HP recommends the purchase of HP’s Installation Services. These services provide for installation of the software product by an experienced HP Software Specialist.
PAGE 5
HP DECnet for OpenVMS Alpha and OpenVMS I64, Version 8.3 HARDWARE REQUIREMENTS SPD 48.48.11 SOFTWARE LICENSING Refer to the HP OpenVMS for Integrity Servers and HP OpenVMS Alpha Operating Systems Software Product Description (SPD 82.35.xx) for hardware requirements and processor support. Reference can be made to the configuration charts listed in the OpenVMS Operating System SPD. For general device or controller descriptions, please refer to the Networks and Communications Buyers Guide.
PAGE 6
HP DECnet for OpenVMS Alpha and OpenVMS I64, Version 8.3 SPD 48.48.11 SOFTWARE PRODUCT SERVICES HP OpenVMS Alpha Licenses End System Extended Function End System to Extended Function Upgrade Support for this product is provided only under a prior version support contract. For more information, contact your local HP office.