At 03:30 PM 08/10/2008, Wyell Grunwald wrote:
Dear Wyell,

It would seem that they don't use third-party indexing, which when 
turned on in image it has hooks and specific
dbinfo calls that Suprtool uses to determine the Omnidex indexes. 
There is another way to use for "older" versions
of Omnidex, but I would rather know more about what version of 
Omnidex and version of Image this is. They may
have done this to address some on-line performance issue, however, 
that seems unlikely if they are able to
re-index every night.

Sincerely,

Neil

>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 *

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