We have seen this behavior in an API client that we have written,
and we have verified that (a) COMPRESSION is set to NO and (b) we
are sending exactly the same number of bytes that we say we are
sending. We have determined that there is essentially a race
condition when there are multiple sessions writing to the disk
pool. If, at a given point in time, four clients contact the
server and announce the intention to write a 100MB, the server
checks at the beginning of each of the four sendObj() calls. If
there is 150MB of space available in the diskpool at the time
that each sendObj() call happens (API programmers forgive me if
I've gotten the calls slightly incorrect, I've not written the
API client, only assisted as the TSM admin), the server gives
each of the four clients the OK to send the data. Of course, they
will all likely fail, as they will fill up the 150MB availables
space before any *one* of the clients finishes.

This has been one of the frustrating aspects of the TSM BA client
not being written with the TSM API. Clearly the BA client does
not encounter this problem, yet there is no straightforward
method to solve the problem with the API. I believe that the TDP
products are all written with the API, so I am not surprised to
hear that they suffer from this problem, as well.

AFAIK, the best we have been able to get from support is the
admission that the error message is inaccurate, or at the very
least misleading.

 -- Tom

Thomas A. La Porte
DreamWorks SKG
tlaporte AT anim.dreamworks DOT com

On Fri, 26 Apr 2002, Tomas Hrouda wrote:

>Gerhardt,
>
>sending of incorrect filesize obviously happens (by my experiences) when
>commpression is turned on and compressed file grows up to original file. Try
>to use no compression or COMPRESSALWAYS NO to avoid bad file size prediction
>by client. It was discussed here sometimes in the past.
>
>Hope this helps.
>Tom
>
>-----Original Message-----
>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
>Gerhard Wolkerstorfer
>Sent: Friday, April 26, 2002 12:39 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Antwort: Re: Antwort: ANR0534W - size estimate exceeded
>
>
>Zlatko,
>you are right, BUT......when the TDP sends an incorrect Filesize to the TSM
>Server, the maxsize Parameter won't work
>(TDP sends 100 Byte - the server will let the File go to the diskpool, but
>the
>file will indeed have 20 Gb, which will fill up your diskpool and bring up
>the
>message indicated (storage exceeded))
>
>And for tracing purposes I wanted to know, if there is any possibility to
>check
>the filesize, which the client is sending to the server.
>
>Gerhard Wolkerstorfer
>
>
>
>
>
>acit AT ATTGLOBAL DOT NET (Zlatko Krastev) am 26.04.2002 11:34:22
>
>Bitte antworten an ADSM-L AT VM.MARIST DOT EDU
>
>An:   ADSM-L AT VM.MARIST DOT EDU
>Kopie:     (Blindkopie: Gerhard Wolkerstorfer/DEBIS/EDVG/AT)
>
>Thema:    Re: Antwort: ANR0534W - size estimate exceeded
>
>
>
>Isabel, Gerhard,
>
>you can set MAXSIze parameter of the disk pool. I usually set it about
>30-60% of the diskpool size (or better pool free size, i.e. size -
>highmig). Files larger than this would bypass the diskpool and go down the
>hierarchy (next stgpool). For this might be tape pool, i.e. file will go
>direct to tape.
>
>Zlatko Krastev
>IT Consultant
>
>
>
>
>Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>To:     ADSM-L AT VM.MARIST DOT EDU
>cc:
>
>Subject:        Antwort: ANR0534W - size estimate exceeded
>
>Isabel,
>we still have this problem regarding to the TDP Informix.
>It seems, that the TDP (sometimes ?) isn't sending the correct Filesize
>and the
>File (DB Backup) exceeds your DISKPOOL and cannot swap to the Tapepool.
>If the TDP would send the correct Filesize, TSM would possibly go direct
>to tape
>and the problem wouldn't come.
>
>Question: How can I check the Filesize and/or Filename, the client is
>sending to
>the server ??
>
>MfG
>Gerhard Wolkerstorfer
>
>
>
>
>
>Isabel.Gerhardt AT FERNUNI-HAGEN DOT DE (Isabel Gerhardt) am 26.04.2002 
>09:17:44
>
>Bitte antworten an ADSM-L AT VM.MARIST DOT EDU
>
>An:   ADSM-L AT VM.MARIST DOT EDU
>Kopie:     (Blindkopie: Gerhard Wolkerstorfer/DEBIS/EDVG/AT)
>
>Thema:    ANR0534W - size estimate exceeded
>
>
>
>Hi Listmembers,
>
>we recently started to recieve following errors:
>
>04/23/02 20:30:29     ANR0534W Transaction failed for session 10000 for
>node
>                       <NODE1> (WinNT)
>                       - size estimate exceeded and server is unable to
>obtain
>                       additional space in storage pool <DISKPOOL>.
>04/24/02 20:38:19     ANR0534W Transaction failed for session 173 for
>node
>                       <NODE2> (TDP Infmx AIX42) - size estimate
>                       exceeded and server is unable to obtain
>additional space
>                       in storage pool <DISKPOOL>.
>
>From previous Messeges of the List I checked, that the Diskpool has
>caching disabled and the clients have no compression allowed.
>
>I was away from work for a while and meanwhile a serverupdate has been
>done.
>If anyone can point me to the source of this error, please help!
>
>Thanks in advance,
>Isabel Gerhardt
>
>Server:
>Storage Management Server for AIX-RS/6000 - Version 4, Release 1, Level
>5.0
>AIX 4.3
>
>Node1:
>     PLATFORM_NAME: WinNT
>   CLIENT_OS_LEVEL: 5.00
>    CLIENT_VERSION: 4
>    CLIENT_RELEASE: 2
>      CLIENT_LEVEL: 1
>   CLIENT_SUBLEVEL: 20
>
>Node2:
>     PLATFORM_NAME: TDP Infmx AIX42
>   CLIENT_OS_LEVEL: 4.3
>   CLIENT_VERSION: 4
>    CLIENT_RELEASE: 2
>      CLIENT_LEVEL: 0
>   CLIENT_SUBLEVEL: 0
>
>