HP3000-L Archives

November 1996, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Tue, 26 Nov 1996 20:24:48 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (79 lines)
Wayne writes:
...
> This turned out to be an OS related problem.  Prior to 5.5, opening of STDIN,
...

> > Also, that first time I ran CSM, it compressed some files in the REGO
> > account (Adager).  The next time I ran Adager, it aborted trying to
...
> The file Adager complaining about is ADAGER78.PUB.REGO.  Adager is calling
> HPGETPROCPLABEL with AGAGER78 as the library.  This is a 4.0 only problem. Later
> releases handle HPGETPROCPLABEL correctly.

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

Apparently, CSM failed to intercept the file open done by HPGETPROCPLABEL...
and thus didn't decompress it, which of course caused the loader to
say "this doesn't look like an XL!".

So, it would appear that this CSM problem could affect any XL file (i.e.,
filecode = NMXL) on the system.

> To avoid confusion, 4.0 version of CSM now ignores ADAGER78 for compression as
> of CSM version 1.19.  This workaround is absent for other OS releases, since it
> works.

I hope it ignores all files with filecode NMXL.

BTW, can this problem also occur for group and pub SL files?  (Since they
are accessed via LOADPROC sometimes.)

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?

   How about for:

       dscopy apples:a to fum

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.

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

Inquiring minds want to know... :)

> We appreciate being made aware of unusual situations that come up when using
> CSM. As we would like for those situations to never occur, reality says they
> will and we want to respond as quickly as possible to provide the most trouble
> free product we can.

Nice response!

--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html

ATOM RSS1 RSS2