Hi,

yes, that's what our server is doing as well.
It takes about 2 hrs to unload our 10GB database (80% used) to a 3590 drive.
It writes a lot of messages, then suddenly stops with this messages
but still is heavily working on disk.
It takes about 45 minutes without messages before the unloaddb successfuly
ends.

HTH
Thomas Rupp


-----Ursprüngliche Nachricht-----
Von: Justin Bleistein [mailto:justin.bleistein AT SUNGARD DOT COM] 
Gesendet: Donnerstag, 16. Jänner 2003 16:00
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: tsm database unload question


Hey Fellow TSMer's,

      We were attempting to perform a database unload of a 55 gig TSM
database yesterday. During the unload the output on the screen said:
"number database entries unloaded". How do you find out how many database
entries a database has in total. Unfortunately the TSM database unload
operation does not provide you with much as far as number of number
progress output or an animated bar or something. If there's a formula we
could use to find out how many entries there are or ballpark that would be
great. This way when we try this again we can pin out a better time line.

      Also after 7 hours and 400 million dumped database entries later the
unload operating just paused.... Any ideas?. Any suggestions would be
appreciated thanks!.

--Justin Richard Bleistein
Unix Systems Administrator (Sungard eSourcing)