John,

>Actually, the dsmSendObj() call in the API _requires_ the caller to
>send an estimate of the size of the object in a structure called the
>ObjAttr.  The parameter description states "It is important that you
>try to be as accurate as possible on this size, because the ADSM
>server used this attribute for efficient space allocation and object
>placement within its storage resources".  Therefore, if a poor
>estimate is sent by the client, it is the clients fault.  The server will
>do what it can do, but only when good data is presented.

You are correct and in fact the SQL Agent does set the estimated size
on the dsmSendObj() call.  However, it does not always set this value correctly
(especially  for DBs larger than 4GB) which leads to the symptom Johan is
seeing.
This  problem will be corrected  in the first PTF.

The best way to circumvent  this problem is to backup your large DBs directly
to tape.

Chris Zaremba
ADSM Agent Development
internet  zaremba AT us.ibm DOT com