We experienced this problem in the early versions of the Solaris ADSM client.
The ADSM client was unable to determine it's own IP-adress, and therefore the 
DSMC SCHEDULE command,
which contacts the server and gives it's "call-back" IP-address, gives an 
incorrect IP-address ("garbage") to
the server.

This problem was fixed in version 2.1.02 of the Solaris Client code (i think), 
but I would recommend downloading
the latest code (V. 2.1.03) from the IBM FTP server.

Dag B. Skogli,
Telenor Teamco AS,
Oslo, Norway.


>Hi,

>I have a Solaris 2.4 ADSM (version 2, release 1) client named mistral 
>(hostname)
>and when attempting a scheduled (server prompted) backup of files to the ADSM
>server (an OS/2 host w/ ADSM 1.2), I get the following errors:

>   06/28/1996 09:10:01      ANR8212W Unable to resolve address for 
> \157\177\154\120
>                            \157E\060.
>   06/28/1996 09:10:01      ANR2716E Schedule prompter was not able to contact
>                            client MISTRAL using type 1 
> (\157\177\154\120\157E\060 1501).
>   06/28/1996 09:11:12      ANR8212W Unable to resolve address for 
> \157\177\154\120\157E\060.

>I sent this message to ADSM support, but never received a response because the
>support person went on vacation and did not notify anyone of the fact.

>I tried stopping and restarting the scheduler/client, but no luck. Has anyone
>seen these errors before? Anyone have a solution?

>Thank your for your assistance.                         John
>---
>John Edwards
>Georgia Institute of Technology, Atlanta Georgia, 30332
>Internet: john.edwards AT oit.gatech DOT edu