David,
        No, you don't need to reinitialize the database - you're doing a full
database dump and a partial database reload (as you suspected the -t
parameter tells ADSM just to load those tables).  Just make sure when
you shut down ADSM before the dump to do it with a HALT QUIESCE so you
don't have to do a database audit after the reload - that is a VERY
painful process.  You will get checkpoint messages on the database load
but, after awhile they're intermittent so you can't use that as an
indicator.  I'd also recommend using a non-ADSM utility (i.e. DSS or FDR
on MVS) to do physical dumps of your ADSM database, logfiles, and all
other files (other than disk storage pools) before you start the
database reload - ADSM is not very forgiving on the reload syntax and I
ended up having to restore the whole database and recovery log to rerun
the reload because I had a PARM statement syntax error on the load and
it would not let me rerun it.   I'm not sure how long you're job will
run but I can't imagine it running longer than the reload I did  - our
db was about 6.2 GB and the partial reload took a little under 7 hours.

Good luck !!!

Tim Pittson
tpittson AT himail.hcc DOT com

>----------
>From:  David Ong[SMTP:david AT BABYONG.NSC DOT COM]
>Sent:  Thursday, September 26, 1996 3:52 PM
>To:    Multiple recipients of list ADSM-L
>Subject:       Re: (Fwd) Reduction of Database
>
>Tim,
>
>Thanks for the reply. I wonder if you can clarify a couple of things for me?
>In
>II08975, the instruction to dump & load the db does not include
>re-initializing
>the db with a dsmserv install command. It seems to imply that the -t option
>used
>will simply dump & load the particular tables involved. Is this what you mean
>by
>partial reload in your note?
>
>Also, as far as progress messages go, I am looking for some indication that
>the
>reload is still going ok as opposed to simply waiting for the process to end
>in
>5 or 10 or 20 hours.
>