That is the opposite of the bug that I mentionied. The bug I mentioned is
if the schedule fails on 3.7 or 4.1 (fixed in 4.12) then the client will say
the event completed successfully and send those results to the server. So
this means that you could have schedules that are failing and not know it
unless you are checking the local schedule and error logs.
A simple test that anyone can do to see if they are affected by this is to
setup a schedule to perform a selective backup of a filespace that does not
exist on the client. TSM should report this as a failed event (and it does
on 3.1.06 and 4.1.2) but reports as successfull with 3.7-4.11.16)
4.11.16 Client:
----------------------------------------------------------------------------
-----
02/08/2001 09:41:33 Selective Backup function invoked.
02/08/2001 09:41:38 ANS1228E Sending of object 'J:\*' failed
02/08/2001 09:41:38 ANS1063E Invalid path specification
02/08/2001 09:41:40 --- SCHEDULEREC STATUS BEGIN
02/08/2001 09:41:40 --- SCHEDULEREC OBJECT END @310 02/08/2001 09:44:19
02/08/2001 09:41:40 Scheduled event '@310' completed successfully.
----------------------------------------------------------------------------
-----
4.12 Client
----------------------------------------------------------------------------
-----
02/08/2001 09:44:43 Selective Backup function invoked.
02/08/2001 09:44:44 ANS1228E Sending of object 'J:\*' failed
02/08/2001 09:44:44 ANS1063E Invalid path specification
02/08/2001 09:44:46 --- SCHEDULEREC STATUS BEGIN
02/08/2001 09:44:46 --- SCHEDULEREC OBJECT END @309 02/08/2001 09:44:00
02/08/2001 09:44:46 ANS1512E Scheduled event '@309' failed. Return code =
4.
----------------------------------------------------------------------------
-----
The above is just an example, but basically anything that will cause a
schedule to fail will not report as failed on the buggy clients.
Tim Rushforth
City of Winnipeg
-----Original Message-----
From: George Lesho [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 07, 2001 2:52 PM
To: [EMAIL PROTECTED]
Subject: Re: Failed Schedules Show Completed Successful
I am new to the list... I occasionally have shedules show failed when, in
fact,
they were sucessful. If these schedules used the SQL-BackTrack for Informix
agent, I have debug turned on and it shows sucessful completion (exit=0) and
the
dsmaccnt.log shows a "1" for normal exit (sucsess) and the usual amount of
backup data. Using 3.7.3.6 on 4.3.2 server and
3.7.2 clients on mostly 4.3.2 clients but also some NT / Novell clients.
Thanks
for any tips.
George Lesho
Storage Admin
AFC Enterprises
