At 11:35 AM -0400 8/8/2003, Wyell Grunwald wrote:
>What about this approach:
>
>If a dataset is going to cross over the 4 GB barrier, scan to see if there are other jumbo datasets out there.  If there are, convert it to a Jumbo,

This is the approach Adager takes.

Ditto for the case where there are ALREADY some LargeFile datasets.

In either of these two cases, the route has been "staked", so to speak,
and things are clear.  There is no further decision to be made.


>otherwise make it a LFDS if Image is at the correct level.
>
>Which brings up a good question - is it possible to have both jumbo's and LFDS in the same database ?

No.  Adager checks for that and, if it detects jumbo datasets on IMAGE
version c.10.05 or newer, it recommends that you use Adager's
"use LargeFiles" command to convert the whole database to "LargeFiles
format" (datasets smaller than 4 GB stay the same).

The challenge is a database that does NOT have jumbos (provided the user
is on TurboIMAGE version c.10.05 or newer).

When a "vanilla" dataset "needs" to grow beyond 4 GB, do I make it into
a Jumbo (by default) or into a LargeFile dataset (by default)?

The challenge is the "default" part.  "Specifying, explicitly, one or
the other" makes my life simpler but complicates the interface.

I don't want to complicate the interface for you.

Thank you,

  _______________
 |               |
 |               |
 |            r  |  Alfredo                     [log in to unmask]
 |          e    |                           http://www.adager.com
 |        g      |  F. Alfredo Rego
 |      a        |  Manager, R & D Labs
 |    d          |  Adager Corporation
 |  A            |  Sun Valley, Idaho 83353-3000            U.S.A.
 |               |
 |_______________|

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *