One of our Netware clients gave a *misleading* indication last night
... one I haven't seen before.   (Netware client at IP20198 via
TCP/IP to a VM server at 0.8/1.8).

>09/12/1994 02:43:12 Executing scheduled command now.
>09/12/1994 02:43:12 Session established with server  ADSM: VM
>09/12/1994 02:43:12   Server Version 1, Release 1, Level 0.8
>09/12/1994 02:43:12   Data compression forced on by the server
>09/12/1994 02:43:12   Server date/time: 09/12/1994 02:43:16    Last access: 09/
>09/12/1994 02:43:12 ANS4972E Unable to connect to target NetWare server 'CHNOFF
>Make sure the TSA NLM is loaded on the specified server.
>(duplicate lines omitted)
>09/12/1994 02:43:12 ANS4972E Unable to connect to target NetWare server 'CHNOFF
>Make sure the TSA NLM is loaded on the specified server.
>09/12/1994 02:43:12 Scheduled event 'OVERNIGHT' completed successfully.
>09/12/1994 02:43:12 Sending results for scheduled event 'OVERNIGHT'.
>09/12/1994 02:43:13 Results sent to server for scheduled event 'OVERNIGHT'.

   The Netware administrator assures me TSA(311) was loaded, but that
doesn't bother me quite as much as the "scheduled event completed
successfully" message!  The DSM.OPT file specifies a number of
DOMAINs (11) ... and from the (above) messages, it seems clear that
*none* of them were backed up successfully.  Since this has been a
reliable "trigger" for ADSM success/failure in the past, this is most
distressing :-(

(I don't *know* if this problem existed in IP20145 or not).

Wayne T. Smith
Systems Group -- CAPS        internet: wts AT maine.maine DOT edu
University of Maine System   BITNET/CREN: WTS@MAINE