thanks - one question I have on that flash:
We have several win2000 Clients stil running with 5.3.6.4
and some WinNT Systems running possibly 5.1.8.2.
Reading this flash I interpret those clients not affected by that problem
-- aren't they ?

If not -- those win2000 and NT Klients are affected but not fixed
then it is surely to avoid 'COMPRESSALWAYS NO'  ... so it is a 'must'
to have the 'COMPRESSALWAYS YES' set for those old ones ?

regards
Rainer


Andrew Raibeck schrieb:

okay - you could change the COMPRESSALWAYS to 'NO', the default is at

'YES'

Otherwise already compressed files normally grow with the tsm compression
and so 'COMPRESSALWAYS NO' can disable compression for those files.

Using EXCLUDE.COMPRESSION is better performance-wise for known file
specifications that do not compress well, since COMPRESSALWAYS NO will
require redrive of the transaction if the file does not compress well.

Since we're talking about COMPRESSALWAYS NO, make sure you keep this flash
in mind before implementing it:
http://www-01.ibm.com/support/docview.wss?uid=swg21322625

Best regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html


The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

--
------------------------------------------------------------------------
Rainer Wolf                          eMail:       rainer.wolf AT uni-ulm DOT de
kiz - Abt. Infrastruktur           Tel/Fax:      ++49 731 50-22482/22471
Universitaet Ulm                     wwweb:        http://kiz.uni-ulm.de