David,

You stated:

"One archive job we did usually ran for 2 hours. When we went to 4.1.2 it
took over 15 hours... Not acceptable of course! So we went back to 4.1.0
and
the archive ran okay.  IBM Support is still working on this.  I seems that
no one else in the ADSM-L AT VM.MARIST DOT EDU <mailto:ADSM-L AT VM.MARIST DOT 
EDU>
land
was having this trouble."

The statement about no one else having that problem is not accurate.

We have a large CAD server whose archive job normally runs for a couple of
hours and sends about 30 GB.

After upgrading to TSM 4.1.2, the last run of that job had sent only 1 GB
after running for over 30 hours.  Also, the DB cache hit percentage which
is normally in the 98.8%-99.1% range was driven down to less than 97.5%.

There is a problem there and it is on my list to call that in also.

Tab Trepagnier
TSM Administrator
Laitram Corporation