For filesystems you can do a QUERY FILESYSTEM FORMAT=DETAILED.  I believe
that the backup completion date is only updated after a successfully
completed incremental backup of the filesystem.
..Paul

Paul Zarnowski                     Phone:   607/255-4757
Cornell Information Technologies   Fax:     607/255-6523
Cornell University                 US Mail: 315 CCC, Ithaca, NY 14853-2601
--
On Tue, 17 Sep 1996 12:47:12 GMT Marc den said:
On Tue, 17 Sep 1996 12:47:12 GMT Marc den said:
>
>We are implementing a large ADSM/MVS server, with HP-UX, Windows-NT
>and Netware clients. All clients have regular files and
>Oracle databases.
>We designed a solution and are implementing it now.
>Key design options are :
>
> 1. All backups are scheduled
> 2. Oracle backups are performed by
>    scheduled Unix scripts (or Rexx on NT and Netware)
> 3. Central (MVS) checking of success/failure using a
>    REXX procedure on a 'scheduled event' list.
>
>All is going rather well, except for 1 important issue :
>If the scheduled event is a client script, then
>it is shown as 'completed' (and result field = blank)
>even if the client script found an error situation.
>
>We know return codes are not documented, and there are plans for
>'Central Logging', but we would like a (temporary) solution now.
>
>We only need a 'trick' that a client script could use to
>force eg. any non-blank value in the result field in the
>(detailed) event list, that our MVS REXX procedure will pickup.
>We need it on HP-UX and NT (and Netware, to a lesser extend).
>
>A possibility would be to put a 'wait' in the client script
>and force a timeout, but we're interested in other ways.
>Did anybody find other solutions ?
>
>Regards