HP3000-L Archives

January 2001, Week 5

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:
Gavin Scott <[log in to unmask]>
Reply To:
Gavin Scott <[log in to unmask]>
Date:
Mon, 29 Jan 2001 13:32:59 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (22 lines)
Wayne writes:
> A question that there might not be an answer to is what to do
> about MPE/iX KSAM files in some kind of theoretical port of
> application software.

Eloquence is built on top of a relational DBMS kernel (but with an Image
API), and uses b-tree indexes, so it has always supported the kind of
indexing options you get with KSAM and the Image B-TREE enhancements, so a
logical thing to do with your KSAM type data is to simply make it another
dataset in an Eloquence database.

The doesn't solve the problem of how to get to that data as easily as in a
KSAM file (which can look like an ordinary flat file much of the time), but
any indexed storage mechanism on Unix is probably going to have the same
problems unless its built into the file system.

> Any info (website?) publicly available on the Eloquence software?

www.hp-eloquence.com

G.

ATOM RSS1 RSS2