Stan writes:

...

>BTW, that's not Adager's problem...it was calling a legitimate intrinsic
>(HPGETPROCPLABEL) on a file that CSM should have decompressed automatically
>(ADAGER78).

Yes, it is definitely NOT Adager's problem.  It is a 4.0 OS related problem
and it is corrected with release 5.0.
We are very sorry if our previous message implied that this was an Adager
problem that was not our intention.

>Out of curiousity, what happens when a compressed file is accessed
>from a remote system?
>E.g.:
>  System A has compressed file APPLES.PUB.SALES
>  User on system B does:
>      DSLINE A
>      remote
>      hello mgr.sales
>      :         (to "switch" back to B)
>      file foo = apples:A
>           or
>      file foo = apples;dev=A#DISC
>   print *foo
>Does the file open trigger decompression?

Yes, it triggers auto decompression.

>How about for:
>dscopy apples:a to fum

Yes, it also triggers auto decompression.

>What happens when a compressed file is STOREd?  I can see two
>possible answers:
>
>1) it's stored compressed, which is good if you are simply backing up
>your machine, but bad if you are sending the tape to another site that
>doesn't have CSM.
>
>2) it's decompressed, which is somewhat bad if you are simply backing up
>your machine, but good if you are sending the tape to another site that
>doesn't have CSM.

It's stored compressed.  This is key to CSM, since it promotes faster backup,
restore, and disaster recovery times.  In addition, we provide a FREE
standalone decompression program.

Here is a quote straight from the "frequently asked questions" section of our
CSM manual:

"What if I restore a compressed file to a different system that does not have
CSM?"

Relax, the standalone decompression program is free and you can use it on any
system,  use it to decompress files.  In fact, it is a good idea to always
store off the standalone decompression program with your backup."


>Does a RESTORE onto a compressed file trigger a decompression prior to
>purging it?

At this moment, yes.

The OS will be enhanced with a 5.0/5.5 patch and future release to address
such issues.  Namely: LISTF and LISTFILE will show HSM attributes: compressed
or migrated.  PURGE, COPY, or RENAME of a compressed or migrated file will not
trigger automatic decompression or demigration.  In addition, new item for
FINFO, FLABELINFO, and FFILEINFO will be available for programs to query HSM
attributes.

Best Regards,

Wayne Sharp
SolutionSoft Systems, Inc.