[Info-vax] ZIP, UNZIP and BACKUP/COMPARE reporting %BACKUP-E-VERIFYERR

[Steven Schweda]

Hein, Nashua NH wrote:
> On Sep 10, 9:24 am, Steven Schweda <sms.antin... at gmail.com> wrote:
> > Hein, Nashua NH wrote:

> > > $ZIP -vv btw does a fun thing! I like it ! (That's two vees, not a
> > > double you :-)

> I was referring to (on eisner)  ...
>
> $ zip -vv tmp tmp.txt
> Get RMS defaults.  getjpi sts = %x00000001.
>                Default: deq =      5, mbc =   0, mbf =   0.
> Open callback.  ID = 2, deq =      5, mbc = 127, mbf =   2.
> Open callback.  ID = 2, deq =      5, mbc = 127, mbf =   2.
> Open callback.  ID = 1, deq =      5, mbc = 127, mbf =   2.
> Open callback.  ID = 3, deq =      5, mbc = 127, mbf =   2.
> updating: tmp.txtOpen callback.  ID = 2, deq =      5, mbc = 127, mbf
> =   2.
> Open callback.  ID = 4, deq =      5, mbc = 127, mbf =   2.
>         (in=4) (out=4) (stored 0%)
> total bytes=4, compressed=4 -> 0% savings

   Oh, _that_ fun thing.  It's all described in the
(self-documenting) source code (and even in [.vms]NOTES.TXT).
With all the things which could influence the RMS parameters,
I decided that _I_ needed a diagnostic message to tell me what
happened.  (Formatting could use some improvement, I suppose,
but it beats nothing.)

> >                Default: deq =      5, [...]

Good for tiny test cases, but you'll be sorry if you do that
with a large archive.

   As shown, the same parameters are used for all purposes,
but those ID values are available if anyone decides that some
particular role deserves special treatment.  My main goal was
"better-than-it-was" I/O speed, which may still be
sub-optimal.