The INCRBYDATE option is not intended to be used exclusively.  It is designed
to perform quick
'partial' incrementals between full incrementals.  For example a INCRBYDATE
could be run
weekdays when the backup window is smaller and then a full dsmc incremental run
on the
weekend.  The full incremental would do the re-binds of any changes to the MC
and expire any
deleted files.

Very simply -INCRBYDATE takes the date of the last successful incremental
backup and any files
with a newer date/time stamp are backed up.   It is not full proof but it does
a fair job of finding most
files which have changed.  The unqualified 'dsmc incremental' should be used if
you want to make
sure that you can get the entire system back to that date.

David Derk
ADSM Client Development

> when You're using the parameter -INCRBYD with the OS/2 ADSM-client
> V2.R1L06, there are some restrictions. That is, in an incremental by date,
> files are not expired or re-bound on the server, and the copy mode
> frequency attribute of the management class is ignored.
>
> What does this mean more precisely, and how can you bypass these
> restrictions...?