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





"Rushforth, Tim" <TRushfor AT CITY.WINNIPEG.MB DOT CA> on 02/07/2001 11:40:38 AM

Please respond to "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: Failed Schedules Show Completed Successful



>--Win2K:  APAR IC27196  There are other cases where scheduled backups fail
>but are reported as COMPLETED successfully back to the server.  This is
>fixed in 4.1.2.

It is my understanding that basically anything that should cause a schedule
to show up as failed will not.  IE. the client will display message
"Scheduled event 'DAILYBACKUP' completed successfully." and send that result
to the server.

See APARS, IC27409 AND IC28653 for more info.

This definitely does not only apply to WIN2K - possibly all platforms.  I
have seen it on Solaris and NT as with WIN2K.

Any ANSxxxxE message that you may get on the client may not show the
schduled as failing.  Some examples are, server out of storage space, i/o
error reading file on client, archive a file in use ........

I have seen this on 3.7.201 and 4.11.16.

I think this is fixed on 4.12 - but I just did a test where I put an invalid
Drive letter in the Domain Statment, ran a scheduled incremental and the
schedule completed successfully.  I have seen postings in the past that this
should give a failed schedule.

Can Tivoli comment on this?

Can they clarify what the problems actually are, what versions they are
fixed on etc?

These are major issues for customers if schedules are showing as completed
successfully but actually are not.  The only workaround is to monitor each
client's logs individually.

Tim Rushforth
City of Winnipeg