HP-UX SNAplus2 R7 APPC Application Suite User's Guide

APING
Using APING
5 APING
APPC Ping (
APING) is a program that exchanges data packets with a partner computer and measures how long the
data transfer takes.
APING
is often the first program configured and run after configuring SNAplus2 because it is a
simple way to check connectivity between your local SNAplus2 computer and remote computers.
APING
includes one transaction program—
APING, the requester program. (There is no separate executable program
for the partner program for
APING
because it is built into SNAplus2.)
Note
It is possible to disable the
APING partner program that is built into SNAplus2 by using
the snapadmin define_node command. To do this, ensure that the node is inactive,
then set the ptf_flags parameter to external_apingd. (For more information about the
snapadmin define_node command, refer to the HP-UX SNAplus2 Administration
Command Reference.)
Use
APING to determine whether you can establish a session between two computers. If session allocation fails,
APING
displays extensive error information. You can also use
APING to get an approximate measure of the session
setup time between two computers, and of the throughput and turnaround time on that APPC session.
5.1 APING Configuration
No configuration is required for the
APING application.
5.2 Using APING
Use the following command syntax to invoke
APING:
aping Options RemoteSystemID
The RemoteSystemID can be either a CPI-C symbolic destination name, a fully qualified LU name,oran
ANAME
alias.Ifan
ANAME alias conflicts with a CPI-C symbolic destination name, the APPC Application Suite uses the
CPI-C symbolic destination name. For more information, see Section 1.2.2, Configuring Your System.
The simplest way to use
APING is to specify only the RemoteSystemID. For example, you can start
APING with the
following command:
aping RemoteSystemID
Running the APING
program results in a session allocation that is timed. When the session allocation is complete,
APING sends 100 bytes to the partner computer and receives the same number of bytes.
APING then displays how
long it took to complete the transfer. Because the first timing usually includes process start up time on the partner
side, the data exchange occurs twice.
The following example shows some additional parameters that can be used with
APING (for more information about
these parameters, see Section 5.2.1, APING Parameters and Options):
aping -s 10000 -i 2 -c 4 RemoteSystemID
35