Though I have already responded to Jim, I am posting the replies here as well
in case
others on the list are interested..


>1. Is there an automated method for purging old objects from the IS and DS
>filespaces after they get to be x number of days old?  I don't relish the
>thought of having to manually delete the old objects every week or so.

     We do have plans to provide a much better way to delete old backup versions
     of Exchange data...we just were unable to contain that in our first
release.  A date
     filter on the delete command  is one possible approach though we are
working
     on the design of an even better solution.  You can look for improved
functionality
     in this area in our next release.   Until then, you can automate the
deletion by redirecting the
     output of a cmd line query to a file and then writing a script/bat file
to process the query output
     and issue the delete commands for objects older than a certain date.


>2. Is there a command to tell for sure what management class was used for an
>Exchange backup?  I have the "include * mcname" line in my dsm.opt file but
>would like to tell for sure that it actually used it.

   We do not currently offer a mechanism to view the management class to which
exchange backup
   objects are bound through the agent interface (GUI or cmd line).  However,
if you are using a
   Version 3 ADSM server, an easy way to confirm the management class to which
objects are bound
    is to use the SELECT admin command to issue a query against the server
database.
   The following sample command should give you what you want:

    select FILESPACE_NAME,HL_NAME,LL_NAME,CLASS_NAME from BACKUPS where
NODE_NAME='your_node'

   Another option you can use is to turn on an API trace by adding the
following to your agent options file:

   TRACEFLAGS API
   TRACEFILE trace.out

   This will show the management class for each object sent to the ADSM server
during a backup.

Chris Zaremba
ADSM Agent Development
internet  zaremba AT us.ibm DOT com