At 11:16 AM 29/09/2003 +0000, you wrote:

>Hi Walter
>
>I got the same idea, BUT 1) It makes no sense, if I dont know the
>result of the backup. The solution to this could be to check/store
>the %errorlevel% 2) What if some client calls gbak directing the
>backupfile to a zip disk?
>
>Generely our problem is that we support the software we deliver.
>When/if some geek (the hardware supplier :-) ) modifies the server
>resulting in stopping cron, then the tape will be backing up OLD
>data! I need to know when the last gbak was run, even if someone is
>running it from the client.

Couldn't you just have the daemon add a record to a text file when the gbak
either completes or abends? You can declare this file inside the database
as an EXTERNAL FILE - that can be queried by the clients via the database,
without need for any share.

heLen