You should be able to say COMPRESS=NO on the dsmc archive command.  
compressalways option acts only when compress=yes is in effect.  In that
case compa=no shouldn't skip any files -- if you have evidence that it
does, please report a bug to IBM.  What compa=no should do is to cause the
current transaction to be cancelled and rolled back (a major waste of
resources which is why compa is in the v3 clients and defaults to yes).
Then all the files which were part of that transaction are resent without
compression until the the growing file is sent.  At that point a new
transaction is started with compression back on.

Bill Colwell
The Charles Stark Draper Laboratory
Cambridge Ma.


_________________________Reply Header_________________________
Author: ADSM-L AT vm.marist DOT edu
Subject: Turn off compression for single files?
01-30-1998 10:10 AM

Hello again, we run a script each night to do exports of our Oracle dbs.
The resulting export files are archived to ADSM using dsmc archive. But,
the script compresses these files and then ADSM compresses them again
because we have compression on for the clients. The double compression
causes the files to grow. What would be helpful is an option on archive for
COMPression=NO but the only option that seems to be allowed is
compressalways which is either yes to archive a file that grows or no to
skip it, well, I don't want to skip it. Turning compression off in the
export script is not an option. Any ideas? Thanks.

Al Cheski