HP3000-L Archives

February 2000, Week 2

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:
"FAIRCHILD,CRAIG (HP-Cupertino,ex1)" <[log in to unmask]>
Reply To:
FAIRCHILD,CRAIG (HP-Cupertino,ex1)
Date:
Tue, 8 Feb 2000 18:29:12 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
Hi Kim

> -----Original Message-----
> 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.

Although this question has been answered several times quite accurately,
I'll go ahead and verify these previous answers as someone from HP.

Image has not yet adopted large file capability to extend the size of Image
databases. Through the use of jumbo datasets Image already has the
capability to grow database sizes beyond the 4GB boundary. At some point in
the future the Image team may make use of large files as the underlying
technology behind their large databases, but this is not the case in release
6.5.

One of the main objectives of the large files capability introduced in
release 6.5 was actually to compliment jumbo datasets! The idea was to allow
worry free report generation (using tools like Supertool) and easily
sortable extracts of databases, even when the size of these reports goes
beyond 4GB.

I hope this helps.

Take Care,
Craig Fairchild
MPE/iX Large File Project Lead

ATOM RSS1 RSS2