>> On Tue, 7 Apr 2009 14:41:24 -0400, Thomas Denier <Thomas.Denier AT 
>> JEFFERSONHOSPITAL DOT ORG> said:


> I am in the process of planning a TSM configuration for dual data
> centers. I expect to have one instance of the TSM server code at
> each data center dedicated to the library manager function for the
> automatic tape library at that site. Based on reports from other
> sites that have set up library managers, I expect a database size of
> about 200 megabytes for each library manager. I expect to be using
> TSM Version 6. The documentation indicates that the minimum size for
> the active log is 2 gigabytes. This size will double if I mirror the
> active log, as I would prefer. Is there any way to avoid the
> absurdity of an active log 20 times as big as the database it
> supports?

Yes.  You can set the log size to something not-stupid.  I think that
the docs are out of date: by mid-beta they had fixed that.

It's especially a pain in the patoot to have a ludicrous log size
because you have to fiddle with the log every time the database
manager starts.

Now, the TSM server tries to conserve connections and resources, which
means that, when it's not doing anything, there are no DB connections.
Good.

And they've tuned the DB2 instance so that, when there are no
connections going, the DBM shuts down.  Good again.

But if you make the DBM startup ridiculously long by forcing it to
sniff around and carve out a brand new 2G log every startup, then you
get... unpleasant side effects. :)



- Allen S. Rout