HP DECnet SNA Gateway for Synchronous Transport, V1.4

HP DECnet SNA Gateway for SPD 25.C6.07
Synchronous Transport, Version 1.4
OpenVMS systems in order to facilitate debugging func-
tions where IBM Interconnect application programs are
developed using the DECnet SNA Programming Inter-
face products.
Gateway management software includes DECnet style
network management tools for configuring, control-
ling, monitoring, and troubleshooting HP DECnet SNA
Gateway-ST. These activities are generally performed
by the HP system manager responsible for the desig-
nated load host node. Most management functions are
performed from a node on the HP network rather than
at or on the Gateway itself.
Management of the DECnet SNA Gateway-ST should
be viewed as part of the HP environment, while manage-
ment of the synchronous circuits connecting the DECnet
SNA Gateway to the IBM network is a joint responsibility
of the IBM and HP system managers.
DECnet SNA gateway management software allows a
HP system operator to bootstrap or restart a DECnet
SNA Gateway remotely and provide configuration and
initialization facilities for the DECnet SNA Gateway.
Problem Isolation and Determination Tools for the
Gateway
In addition to event logging and error counters, a wide
range of fault isolation tools are included.
Trace capabilities SNATRACE and NETTRACE for
OpenVMS are provided with HP DECnet SNA Gateway-
ST to help debug application programs as well as assist
in identifying system problems. An operator can run a
trace at the Circuit, Physical Unit (PU), or Session level,
and then format the data on a specified HP system. The
trace features are helpful in identifying an error for re-
medial action.
A snapshot monitoring utility is provided to display on
HP host-controlled terminal the status of the gateway’s
buffer availability, the number of SNA sessions currently
in progress, and other information that pertains to both
the DECnet and SNA network.
If an irrecoverable error should occur during operation
of the DECnet SNA Gateway system, a memory im-
age may be dumped to a designated Ethernet-attached
OpenVMS load host. This memory image may then be
provided to your HP support personnel for problem di-
agnosis.
INSTALLATION
Only experienced customers should attempt installation
of this product. Installation services from HP is recom-
mended for all other customers. These services provide
for installation of the software product by an experienced
software specialist.
HARDWARE REQUIREMENTS
In Ethernet LANs
• Itanium, Alpha and VAX system configurations as
specified in the OpenVMS Operating System for I64,
Alpha and VAX Software Product Description (SPD
82.35.xx and 25.01.xx) to act as load host
• DEC MicroServer (DEMSA-Ax or DEMSB-Ax) and
appropriate adapter cables as described in the Com-
munications Hardware Requirements section of this
Software Product Description
• Bell System compatible modems, or, in Europe, PTT-
approved modems
• VT series terminal for diagnostic use
Processors Supported
For information about supported processors, refer to
the OpenVMS Operating System for I64, Alpha and
VAX Software Product Description (SPD 82.35.xx and
25.01.xx).
Processors Not Supported
VAX-11/730, VAX-11/750, VAX-11/780, VAX-11/782,
VAX-11/785, VAXstation 8000.
Disk Space Requirements (Block Cluster Size = 1)
Disk space required for installation:
OpenVMS I64 11,800 blocks
(5.9 MB)
OpenVMS Alpha 11,800 blocks
(5.9 MB)
OpenVMS VAX 11,800 blocks
(5.9 MB)
Disk space required for use (permanent):
OpenVMS I64 7,923 blocks
(3.961 MB)
OpenVMS Alpha 3,536 blocks
(1,768 KB)
OpenVMS VAX 2,674 blocks
(1,337 KB)
These counts refer to the disk space required on the
system disk. The sizes are approximate; actual sizes
may vary depending on the user’s system environment,
configuration, and software options.
3