Are you referring to the "file grew with compression and unable to allocate
additional space" problem when going to cached diskpools ? ? ?
If so, run with client settings "compression yes" "compressalways no", if
the file grows with compression it will be sent uncompressed.  (famous last
words...)

Had this bite me in the @$$ with TDP/R3... because they switched and started
to ignore the client's compressalways setting.
in TDP/R3 3.2.0.11 they have started to pre-allocate at 110% actual client
size over on the tsm server and generally this is enough to cover files that
grow with compression... IN THE EVENT this isn't enough, there is an
environment variable  XINT_TSMOFFSET which has a default value of 10 (the
extra 10% of pre-allocation to occur)

I don't know if the Domino agent ignores the client's compressalways setting
like the TDP/R3...
and if it does, I don't know if Tivoli is going to roll out this
XINT_TSMOFFSET environment variable...
Uhmmm, this environment variable is in a Unix client environment...

Try checking your "compressalways" setting and if it is no/off, try it with
on/yes and see if that works to let you get back to using a cached
diskpool... remember, you'll need a run or two to get the diskpool filled
back with cached copies of files before you can really know if things will
work or not.

Dwight