I have two TSM servers Win2K at 4.1.5 and AIX 433 at 4.1.4.5 with clients
at 4.1.3 across the board. I get this error for the Windows clients
consistantly but not the AIX clients. I have reported this to Tivoli but
their first line support person is insisting that there is a comms loss
which will be relfected in the tsm error log (but isn't). This error occurs
when doing the FIRST incremental or an archive and doesn't appear to occur
in subsequent incrementals.  If anyone has an apar or reference that I can
pass back to the Tivoli support person, I would appreciate it.

George Lesho
AFC Enterprises






"Rushforth, Tim" <TRushfor AT CITY.WINNIPEG.MB DOT CA>@VM.MARIST.EDU> on
01/09/2002 03:06:10 PM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: George Lesho/Partners/AFC)
Fax to:
Subject:  Re: Return code=4 on scheduled backap


When I tested the 4.2.1.15 client, the bug was fixed.  Are you sure it is
not a real failed schedule?

Any error messages in dsmerror.log or previously in dsmsched.log?

Tim Rushforth
City of Winnipeg