Had the same problem, turns out the scheduler on the client wasn't
     running.


______________________________ Reply Separator _________________________________
Subject: Unknown TCPIP Failure
Author:  Henk ten Have <hthta AT SARA DOT NL> at ~Internet
Date:    9/1/97 4:45 PM


After starting a scheduled backup for some host's which are not accessible
(i.e. ping doesn't response), the following happens:

for a host who had never access to the server nothing is found in the
  actlog and a "q event" shows the status "Pending" when the schedule starts
  and "Missed" when the schedule ends;

for a host which did have access to the server (so the server knows its
  TCP-address), the following is found in the actlog:

09/01/97   12:52:35  ANR9999D tcpcomm.c(356): Unknown TCPIP Failure.
09/01/97   12:52:35  ANR2716E Schedule prompter was not able to contact client
                      SNS_DENKER_SURFNET_C using type 1 (145.41.6.14 1501).
09/01/97   12:54:51  ANR9999D tcpcomm.c(356): Unknown TCPIP Failure.
                     ........
                     ........
09/01/97   13:47:00  ANR9999D tcpcomm.c(356): Unknown TCPIP Failure.
09/01/97   13:49:16  ANR9999D tcpcomm.c(356): Unknown TCPIP Failure.

 and "q event" shows the status "Started" when the schedule starts and
 "Missed" when the schedule ends;
 So every 2 minuts there is an ANR9999D message given, that makes 30
 messages in one hour for every "previous known" inaccessible host.

Question: is it possible to get more clearness in the message and to get also
          less messages?

(running ADSM V2.1.0.13 on a SP2 (AIX 4.1.4.0) using 3494 with 4 3590 units,
 backup/archive client's 2.1.0.6 on AIX 3.2, AIX 4.1.4, SunOs, Solaris,
 IRIX, Win95, WinNT, HSM client's 2.1.0.6 on AIX 4.1.4.0)

Regards,

Henk ten Have                   SARA, Academic Computing Services Amsterdam
Systems Programmer              Kruislaan 415
E-mail: hthta AT sara DOT nl           1098 SJ Amsterdam
Phone : +31205923000            The Netherlands