was a
bad API that was provided by IBM as a part of DB2. This problem was fixed
over a year ago for us.
Matt
-Original Message-
From: Henrry Aranda [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 09, 2002 6:23 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM S/390 performance
[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: TSM S/390 performance
Date: Mon, 9 Dec 2002 07:58:05 -0500
Hi Henrrry,
I had a similar type problem. It was traced back to a DB2
backup.
It was a matter of the TSM server getting a bad size estimate and not
properly saving enough dis
: [EMAIL PROTECTED]
Subject:TSM S/390 performance
Hi list,
environ is TSM server 4.1.2.12 on S/390 with 3494 library connected
via FICON, 3590E tape drives, 60+ SQL Servers using TDP 2.2 and Oracle
server on AIX 5.1 with 1,5TB of backup data (no Oracle TDP is being used),
the 390 is connected
Hi list,
environ is TSM server 4.1.2.12 on S/390 with 3494 library connected
via FICON, 3590E tape drives, 60+ SQL Servers using TDP 2.2 and Oracle
server on AIX 5.1 with 1,5TB of backup data (no Oracle TDP is being used),
the 390 is connected via gigabit ethernet to the clients, the issue is when
