Adding more space to Image would only suffice in the short term. When I
first changed from Image to Turbo Image years ago, HP changed some of the
pointers from 16bit to 32bit. I believe the saying then, before PA-RISC,
what are you going to do with a Image DB with 4G records? Well Jumbo sets
gives you more room to accomplish the 4G record limit. But until HP again
changes the underlying structure, having more space will only make you cry
when you hit the 4G limit. Of course you can have larger and larger records
to bypass this limit, but I think you DB would begin to look a little funny.
So until users start hitting the limits, HP will probably tinker with
structure changes within the Labs, until they come up with something that
answers the need and allows forward conversion without major problems.

James

> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of B T Vikram Kumar
> Sent: Tuesday, February 08, 2000 10:09 PM
> To: [log in to unmask]
> Subject: Re: MPE iX Release 6.5
>
>
> Currently Image supports dataset file sizes upto 80GB. And wait
> for a while for
> >80 GB to ???? GB
>
> Regards,
> Vikram
>
> Kim Heckler wrote:
>
> > In some HP documentation on 6.5, new features,  it reads:
> >
> > "Support of fixed length records and KSAM files of up to 128 Gbytes."
> >
> > No mention of Image (plain vanilla, not jumbo datasets).  Is
> Image included
> > in the above statement?  I don't get any answers from my local HP reps.
> >
> > Can someone from HP comment on this question?  PLEASE.
> >
> > Thank you.
>