I prefer not to use dynamic dataset's on Omnidex enhanced databases. It has
just never seemed like a good idea to me to allow the database engine to
make changes on the fly like that when Omnidex needs to know exactly where a
particular record is in the file at all times.

So as part of my procedures for making a capacity change on a database, I
stream a job that deletes, installs and indexes the database from scratch.
Reindexing does not, or at least did not in the past, resize the index files
to match any capacity changes you made.

*disclaimer : I have not used the following utilites much myself

You can also use the capchk.util.disc command to monitor the index files and
the cap.util.disc to manage the size of the index files based on % full.


> -----Original Message-----
> From: Leonard S. Berkowitz
> [mailto:[log in to unmask]]
> Sent: Thursday, August 15, 2002 10:01 AM
> To: [log in to unmask]
> Subject: Omnidex files
>
>
> Does anyone have a method to monitor the rising EOF of the
> Omnidex files
> (file code of -411) so that preventative action can be taken
> before these
> files fill up?
>
> We hit the fan last night on one of these files. Until the
> horse was stolen
> from the barn, under the apparent misbelief that these files were
> self-adjusting, we were not monitoring these files. Now we
> have to start,
> and I'd prefer not to reinvent the axle.
>
> Thanks.
> --
> Leonard S. Berkowitz
> Perot Health Care Systems
> (Harvard Pilgrim Health Care account)
> voice: 617-509-1212
> fax: 617-509-1955
> pager: 781-226-2431
>
> * 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 *