Hello all, 

   I usually don't use this number, since I have a lot of retries due to
changing files and so on, and I would have a huge amount of
re-transmitted files. However, I've been testing (with LTO1, but I will
do it again with LTO2) and found out that you should not set this to a
number less than the buffer size of the LTO drive. Doing so will produce
a buffer flush on the drive each time you commit the transaction in
TSM's database.
   Since I was working with IBM LTO drives (64MB buffer) I determined
that 65536 was the smallest number to use. I got my best results using
TXNBYTELIMIT 131072 (128MB).



Regards, 

Paul Gondim van Dongen
MCSE
IBM Certified Deployment Professional -- Tivoli Storage Manager V5.2
VANguard - Value Added Network guardians
http://www.vanguard-it.com.br
+55 81 3225-0353


-----Mensagem original-----
De: Joni Moyer [mailto:joni.moyer AT HIGHMARK DOT COM] 
Enviada em: Monday, July 19, 2004 8:36 AM
Para: ADSM-L AT VM.MARIST DOT EDU
Assunto: txnbytelimit & lto2


Hey Everyone!

I have been looking into tuning client and server parameters for when I
move to an AIX 5.2 TSM server at 5.2.2.5.  I noticed that in an
environment with LTO2, the clients txnbytelimit should be 2097152.  Is
the TSM Performance and Tuning Guide correct?  Thanks!

********************************
Joni Moyer
Highmark
Storage Systems
Work:(717)302-6603
Fax:(717)302-5974
joni.moyer AT highmark DOT com
********************************