Assuming that you are experiencing the problem described in APAR PQ12677 (the
one Jerry mentioned yesterday), then yes, doing what you suggest is one of the
two recommended circumventions:

1) Set COMPRESSALWAYS NO in dsm.opt (i.e. set "Continue compressing if object
grows" to NO).

2) Turn off caching on the disk pool, then use MOVE DATA on each disk pool
volume to clean off the existing cached files.

Regards,

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com



ADSM-L AT VM.MARIST DOT EDU on 07/22/98 04:46:09 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: ANR0534W


Has anyone tried leaving both compression and caching on but setting
"Continue compressing if object grows" to NO? If so, does that
prevent the ANR0534W?

David EHresman