HP3000-L Archives

December 1996, 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:
Deane Bell <[log in to unmask]>
Reply To:
Deane Bell <[log in to unmask]>
Date:
Tue, 31 Dec 1996 09:49:43 -0800
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (94 lines)
Kirby -
  Another alternative is the product called DataNow! previously sold by a
company known as COSMOSOFT and now sold by Idaho Computer Systems.  We use
the same software vendor as you and had the same response re adding 3-rd
party indexing keys.  Our database is as large as yours, and we routinely
report across multiple datasets and across multiple databases with minimal
effects on our on-line users.  Prior to purchasing DataNow! we did some
benchmarking (not a rigorous test, mind you) and took one of our 2-hour
(run-time) QUERY reports, converted it to cobol using QGEN and it produced
the same data in 20 minutes.  We then converted it to DataNow! and got the
same data in 2 minutes.  Needless to say, we've very happy with the tool.
It's easy to learn, runs on either PCs or HP terminals, and our use goes
well beyond reporting ... it's also used for various database maintenance
activities.  We have no business attachment to DataNow! other than being a
very satisfied customer.  Give me a call and I'll be happy to answer
further questions.  Because we use the same pharmacy system vendor, we're
happy to share currently written reports/programs with you, gratis as part
of the 'user community'.

 Deane Bell      Computer Services Coordinator, Affiliate Instructor
 The University of Washington           Vmail      : (206) 548-6009
 Medical Centers Pharmacy               switchboard: (206) 548-6060
 1959 N.E. Pacific Street, Box 356015   facsimile  : (206) 548-4901
 Seattle, WA  98195-6015  U.S.A.        internet   : [log in to unmask]

Date:    Mon, 30 Dec 1996 16:12:18 GMT
From:    Mark Landin <[log in to unmask]>
Subject: Re: Non-invasive way to expand IMAGE keys??

In article <[log in to unmask]>,
[log in to unmask] says...
>
>We use our HP 3000 for a third-party pharmacy prescription
>application.  It's really a turn-key system which is why I am a
>relatively unsophisticated MPE person.  We have a single IMAGE databse
>with over 30 detail sets that contains almost a million entries in the
>largest set.  The problem is that most of the "fields" are not usable
>as key fields for QUERY reports which means that a serial read takes
>15-20 minutes and consumes 100% of the CPU and 85% of the disk
>resources which means that these reports can really only be run after
>normal working hours.  The vendor has indicated that use of ANY
>indexing scheme that modifies the database by so much as a single byte
>will void our software support contract.  Since this application is
>mission-critical to our department I have taken this warning to heart>and
not tried to use programs like Omnidex.
What I am wondering is if
>there are any ways that a relatively non-tech person can set something
>up as an indexing scheme to get around the inherent lack of keys.  I
>am getting more and more requests for ad-hoc reports that I can't
>respond to without  more keys.  I have even wondered if the future
>release of b-tree indices will help me, but I think they will only
>exist for IMAGE/SQL databases.  Any and all help appreciated.
>
>Kirby Stiening, Pharmacy Information Systems Supervisor
>University of Virginia Health Sciences Center
>Charlottesville VA
>804-982-0373

YOu may have a couple of choices:

1) KSAM files could be used to be external indices into your data. You
would
have to insure that the KSAM files are kept up-to-date somehow. This could
be
as simple as a nightly re-indexing job or as complex as modifying all your
DB
update routines to also update the KSAM file appropriately, depending on
how
static the data is.

Your KSAM records would have basically two fields: the first field would
be the
item or attribute in the dataset that you want to index (let's say it's
price...) and the second field would be the primary key (say, product
code). If
you wanted to index by more than 1 attribute, you would need at least 3
fields
per record: 1) index item name, 2) index item value, and 3) primary key
value.

 2) Buy SUPRTOOL and continue doing serial reads....but many times more
quickly. SUPRTOOL is a very handy product. Get it from Robelle.

------------------------------


------------------------------------------------------------------------------
 Deane Bell      Computer Services Coordinator, Affiliate Instructor
 The University of Washington           Vmail      : (206) 548-6009
 Medical Centers Pharmacy               switchboard: (206) 548-6060
 1959 N.E. Pacific Street, Box 356015   facsimile  : (206) 548-4901
 Seattle, WA  98195-6015  U.S.A.        internet   : [log in to unmask]
------------------------------------------------------------------------------

ATOM RSS1 RSS2