or check for previous versions at the Internet Archive. Yahoo! is not affiliated with the authors of this page or responsible for its content.
Software Product Description Software
Product
Description
PRODUCT NAME:
HP X.25 for OpenVMS Alpha and I64 Systems, V2.0
SPD 47.37.16
DESCRIPTION
HP X.25 for OpenVMS enables appropriately cong-
ured systems to connect to an X.25 Packet Switched
Data Network (PSDN) via an X.25 Relay node on the
same Local Area Network (LAN), via a DNA Phase IV
X.25 connector node, or directly using a synchronous
controller card for Alpha.
The product supports communication via PSDNs con-
forming to ITU/TSS recommendation X.25 1980, 1984,
and 1988, or to international standard ISO 8208. Refer
to the SUPPORTED PUBLIC NETWORKS section for
the list of supported PSDNs.
HP X.25 V2.0 supports OpenVMS Operating System
for Alpha version 8.2 and I64 version 8.2 and 8.2-1.
X.25 V2.0 for OpenVMS Alpha contains synchronous
device drivers and is required when using synchronous
communications options.
Note: HP X.25 for OpenVMS I64 does not support syn-
chronous device drivers and synchronous communica-
tions options.
HP X.25 for OpenVMS also provides the device drivers
and specic data link protocol support for HPs syn-
chronous communications options for OpenVMS Alpha
systems.
HP X.25 for OpenVMS software allows the system to:
Connect to other X.25 implementations using RFC
1613 (also known as XOT) via a TCP/IP wide area
network.
Act as a Gateway Access Protocol (GAP) server for
Phase V GAP Clients
Act as an X.25 Connector system for DECnet-Plus
X.25 Access systems
Act as a packetmode DTE connected to a supported
PSDN.
Support ISO 8208 DTE to DTE pointtopoint oper-
ation.
Act as a packetmode DTE connected to a LAN.
Act as an X.25 Relay node conforming to ISO Tech-
nical Report 10029.
Provide an X.25 subnetwork for DECnet-Plus
CONS and CLNS operation.
Provide a DECHDLC pointtopoint data link for
DECnet-Plus CLNS operation.
Act as a combination of the above, chosen on a per
DTE basis.
The following restrictions of HP X.25 for OpenVMS soft-
ware should be noted:
Phase IV GAP Clients (or access nodes) are not sup-
ported.
P.S.I. Access (Phase IV) clients are not supported.
DCE mode is supported for the purposes of point
topoint operation as described in ISO 8208; DCE
mode for emulation of a PSDN is not supported.
Use of the D bit in data packets is not supported.
HP X.25 for OpenVMS I64 does not support syn-
chronous device drivers and synchronous communi-
cations options. The LAPB conguration is not sup-
ported on I64.
July 2005 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0
SPD 47.37.16
HP X.25 for OpenVMS supports the following functions:
Processtoprocess (HP X.25) communication.
X.25 for OpenVMS allows application programs to
access X.25 network services via the standard
OpenVMS QIO system service.
Processtoterminal (X.29) communication.
Through the X.29 QIO programming interface, users
of the OpenVMS system may make outgoing calls
to other HP or nonHP systems or suitable network
PADs accessible via a PSDN.
Terminaltoprocess (X.29) communication.
Remote terminals connected to the PSDN may ac-
cess the OpenVMS host running X.25 by means of
an X.29 Switched Virtual Circuit (SVC) call.
DECnet-Plus Connectionless Network Service.
The product supports the use of the DECHDLC
and X.25 protocols as subnetworks for the OSI
Connectionlessmode Network Service (CLNS).
DECnet-Plus Connection Oriented Network Service.
The product supports the OSI Connection Oriented
Network Service (CONS) for OSI Transport over X.25
subnetworks.
X.25 Mail.
The X.25 Mail utility allows communication across a
PSDN via electronic mail between two systems run-
ning the Mail11 protocol over X.25. Systems that
support Mail11 over X.25 include WAN Support for
HP UNIX®, X.25 for OpenVMS and X.25 installations
of DECnet-Plus for OpenVMS VAX.
Wide Area Network (WAN) Device Drivers
The WAN device drivers support synchronous com-
munications and offer a supported user ($QIO) in-
terface. This version also includes a pseudodriver
(WANDRIVER) that provides a programming inter-
face to the Data Link level for the LAPB, DEC-HDLC,
and LLC2 protocols and an interface to the physi-
cal layer of the synchronous communication devices
supported by the product.
Note: This function is not applicable for X.25 for
OpenVMS I64.
X.25 Relay allows an appropriately congured Open-
VMS system to relay X.25 packets between a Lo-
cal Area Network (LAN) and a synchronous com-
munications link to a Packet Switched Data Network
(PSDN).
X.25 GAP Server allows remote Phase V GAP clients
to connect to a PSDN via the GAP Server node using
the DECnet NSP protocol. The remote X.25 client (or
access node) communicates with the X.25 Server or
X.25 Gateway/Connector node using the Gateway
Access Protocol (GAP) via a DECnet session con-
nection.
The multi-host mode of operation provides the fea-
tures offered by VAX P.S.I. Native and also allows
VAX P.S.I. Access systems to connect to a PSDN as
though directly connected.
XOT or X.25 over TCP/IP allows X.25 applications
on an appropriately congured OpenVMS System to
communicate with other RFC 1613 implementations
over a TCP/IP Wide Area Network.
Features
Conformance to Standards
HP X.25 for OpenVMS complies with the following stan-
dards:
ITU/TSS recommendationsX.25 (1980, 1984, or
1988), X.3, X28, X.29
International standards ISO8208, 7776, 8881,
8802/2, 8878, 8473
Virtual Circuits
HP X.25 for OpenVMS offers communication over both
Permanent Virtual Circuits (PVCs) and Switched Virtual
Circuits (SVCs), and supports up to 4096 virtual circuits
per system. One virtual circuit is used for each incom-
ing or outgoing X.29 terminal connection, for each X.25
call, and for each DECnet-Plus routing circuit and trans-
port connection. The use of PVCs for X.29 communi-
cation is not dened by the 1980 and 1984 ITU/TSS
recommendations, and is not available with HP X.25
for OpenVMS.
Virtual circuits may use X.25 protocol over a LAN con-
nection, over a WAN synchronous communications con-
nection, or may use HP X.25 Client for OpenVMS Al-
pha Systems over a DECnet circuit to a DECnet Gate-
way Access Protocol (GAP) connector node. NOTE that
there is no support for use of more than 512 of the avail-
able virtual circuits by HP X.25 Client for OpenVMS
Alpha Systems with DECnet Gateway Access proto-
col connector nodes. See the HARDWARE REQUIRE-
MENTS section for details of GAP connector nodes and
ISO relay nodes supported.
ProcesstoProcess Communication
The HP X.25 for OpenVMS programming interface al-
lows application programs to access X.25 packet level
services via the standard OpenVMS QIO interface.
Functions include the establishment and clearing of
network connections, data transmission and reception,
sending and receiving of interrupt messages, and reset-
ting of virtual circuits. The interface also provides for the
segmentation and recombination of messages that are
longer than the packet size selected for the circuit.
2 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0
SPD 47.37.16
This interface enables an application program using
OpenVMS System Services to communicate with com-
plementary X.25 software on other HP or nonHP sys-
tems.
Terminal Communications
HP X.25 for OpenVMS supports terminal communica-
tions according to ITU/TSS recommendations X.3, X.28,
and X.29. Only those terminal parameters dened in the
X.3 recommendation are explicitly supported. Network
specic enhancements or extensions to the X.3 param-
eters are available at both the X.29 programming and
the hostbased PAD user interface. Terminal processes
that depend on these extensions may not function cor-
rectly when used on other PSDNs or when accessing
one PSDN via another (for example, international ac-
cess).
The X.29 interactive terminal interface allows re-
mote asynchronous terminals (charactermode DTEs)
connected to the network to communicate with the
OpenVMS system in a manner similar to local termi-
nals. The maximum number of terminals supported on
a OpenVMS Alpha system (both local and X.29 remote)
cannot exceed the number for which the system has
been congured.
When using applications designed for interactive, local
terminal operations, transmission delays or PAD param-
eter settings can cause inconsistencies between incom-
ing X.29 trafc and the applications operation. It may
be necessary to make modications to the application
user interface or alter PAD parameter settings.
The X.29 interface includes a programming capability
for the support of specic X.29 signaling requirements,
including modication of PAD parameters.
Accounting
Accounting information is collected and is made avail-
able to the user via a report writing utility.
For incoming X.29 calls, no information can be retrieved
relating to the process or account onto which a user is
logged.
Security
An extensive security facility is provided. Control of re-
mote access to the system (incoming security) and local
access to the network (outgoing security) are supported.
Incoming and outgoing security can be based on any
c