HP3000-L Archives

April 2000, 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:
Sletten Kenneth W KPWA <[log in to unmask]>
Reply To:
Sletten Kenneth W KPWA <[log in to unmask]>
Date:
Fri, 28 Apr 2000 18:13:59 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
This morning Joseph noted:

> ...... If the dataset's MPE name is XXXDB22 then the
> Jumbo file name will be XXXDB22.001. I suppose
> theoretically you can keep growing until XXXDB22.999.

As in many cases, there is a slight divergence between
theory and reality....    :-)     ---->

Internal TurboIMAGE limits currently restrict the maximum size
of one DETAIL dataset to 80GB or less (depending on Block
Factor), using 4GB JUMBO HFS chunk file "extensions".  With
the pending IMAGE enhancement to move from EntryByName
to 32-bit EntryByNumber (IMAGE will continue to support both
formats), HP could also choose to increase the number of
allowable JUMBO chunk files...  BUT:

HP has indicated that a future release will support using MPE
"Large Files" as IMAGE DETAIL datasets.  Since 128GB
"Large Files" will be in MPE 6.5, my unconfirmed guesstimate
is that HP will likely try and go directly to MPE Large Files in
IMAGE;  *instead of* doing the two-step:
(1)   FIRST:  Increase max number of JUMBO chunk files.
(2)   SHORTLY THEREAFTER:  Go to MPE Large Files.

Ken Sletten
SIGIMAGE Chair

ATOM RSS1 RSS2