HP3000-L Archives

September 1999, 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:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Tue, 14 Sep 1999 12:00:34 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
Nick asks:

> > >What are the KSAMXL limits concerning :
> > >- maximum record size
> > >- maximum number of records
> > >- maximum number of sectors

> Costas, while i don't KNOW the answers I believe that:
>
> 1.  Why should KSAMXL limits be any different than those for any
> other file?

Because KSAMXL has to keep key information in *addition* to the
user-supplied data all in one file.  Thus, it's clear at the outset
that the maximum number of records (of a given record size) will
be less for a KSAMXL file than for a flat file.  Remember, that
key information includes the B-tree (or whatever) structure/pointers!

Similarly, since there's extra code manipulating this, it's a
reasonable question to ask what the maximum record size is.

However, all of the questions can be answered by any user with a
little trial an error (e.g., repeated BUILD commands).
A minute or less would have shown that you can BUILD a flat
file *or* a KSAMXL file with a maximum record size of
16383 "words" or 32767 bytes.

I'll leave the other two for Costas to try. :)

--
Stan Sieler                                          [log in to unmask]
                                         http://www.allegro.com/sieler/

ATOM RSS1 RSS2