To:           ADSM-L AT VM.MARIST DOT EDU

>Hello !
>
>We are about to install SAP/R3 on AIX machine, running DB2.
>
>I read the following red books: "Using ADSM to backup DataBases" and
>"DB2 for AIX R/3 admin guide". I understood all the backup methods and
>the way it works. I didn't find any information on how to configure the
>Management class and the copy groups. Is there any recomondation for
>this ?
>
>Regarding auto scheduling: Do I have to run a command sched. from ADSM ?
>
>Regards
> *--*--*--*--*--*--*--*--*--*--*--*--*--*
>
>          Malkit Hayun
>          Application Engineer
>          UDI - Unique Data International Ltd.
>          ISRAEL
>
>          E-mail:       malkit AT udi.co DOT il
>
>          Voice:        +972-3-9512064
>          Fax:          +972-3-9512065
>    Mobile:       +972-50-611050
>
>    *--*--*--*--*--*--*--*--*--*--*--*--*--*

Malkit, I'm behind on email so someone else might have answered this already.
I thought we had stuff in the redbook on the management class considerations;
I wonder if you have the -02 version.  With DB2 V2 unique names are used so
ADSM only ever gets one active copy of the object.  Therefore, you can't use
regular adsm versioning to control the expiration of the objects.  DB2 has
a utility to query and delete objects from adsm, called db2adutl.  When you
delete an object using db2adutl, a delete object api call is sent to adsm,
adsm marks the file inactive, and will delete it when adsm file expiration
processing next runs.  For all this to work properly, you need to use
a management class with zero inactive copies and 1 active copy.

For scheduling, you don't have to use adsm scheduling, but you can.  If you
use adsm scheduling, just schedule a client os command, and either enter the
db2 command as the action, or a script name that will run on aix that contains
the commands you want to run.
thanks,
Cyndie Behrens (IBM San Jose)