HP3000-L Archives

October 2008, 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:
Wyell Grunwald <[log in to unmask]>
Reply To:
Date:
Wed, 8 Oct 2008 19:30:43 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (9 lines)
Dear kind HP3000L listeners,
I have a problem with OMNIDEX at this location.  We have AMISYS, which comes with OMNIDEX, and there are many OMNIDEX indexes on our databases.  In every other location I have worked, OMNIDEX indexes are maintained "on the fly", but at this location, we run a complete re-index every night.  During the day, any new adds to the datasets don't get reflected in the OMNIDEX indexes.  I have manuals on OMNIDEX, which I have examined closely, which are excellent references on how to set up indexes, re-index, etc. but say nothing about how to turn on automatic updating of OMNIDEX indexes via regular DBPUT, DBUPDATE, and DBDELETE calls at the sys level.  I must stress that we can do partial key lookups in QUICK screens during the day just fine (new updates excluded).
Also, anything we do in SUPRTOOL does not update the OMNIDEX indexes.  
Is there any way to read in SUPRTOOL using OMNIDEX indexes ?
Wyell Grunwald

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2