Sheelagh Treweek wrote:

(2) Another example of one I am getting nowhere fast with is the Solaris client
failing to perform "prompted" scheduled sessions. This worked at ADSM 1.2; two
clients that we updated to ADSM 2.1 immediately failed with messages like:

19-10-1995 03:00:01      ANR8212W Unable to resolve address for <junk chars>.
19-10-1995 03:00:01      ANR2716E Schedule prompter was not able to contact
                          client
                          OXMAIL3 using type 1 (<junk chars> 53794).
19-10-1995 03:01:08      ANR8212W Unable to resolve address for <junk chars>.


     We have a similar problem with the new Solaris V2 R2 L01 client.
     Our local IBM support has told us, that APAR IC11775 has been opened
     on Nov. 2nd (!) against this problem.

     Christian Moser,           Internet: christian.moser AT schering DOT de
     SCHERING AG, 13342 Berlin, Tel.: (030)4681356 Fax: (030)46916719