Steve Almes writes

Well, I had a real problem with this.  I enabled it on several of my
production databases and had database corruption on all of them.  I don't
know what I'm doing wrong.  I'm on MPEiX 5.5 with the Y2K patches on a 957.
I should probably go to 6.0 at least, shouldn't I???
-----------------------------------------------------------------
Well you can go on 6.0 until the end of the week and then it's unsupported.
You really should go on 6.5 with your 957.  It's been out a long time and
will work ok.  You really should go to DDX.  It works and works well.  Just
set your max cap to an impossibly large number, a good increment (we use 5%)
and let it go.  As far as the database corruption, check the e-mail from Jon
Bale from 5 years ago about the problem.

--------------------------------------------------------------------
We have developed a fix for TurboIMAGE that removes this defect.
Patches will be created for MPE/iX 5.0 and MPE/iX 5.5.  The MPE/iX 5.0
patch is TurboIMAGE version C.06.23 and has Patch ID TIXKX11.  The patch
for MPE/iX 5.5 is TurboIMAGE version C.07.07, has Patch ID TIXKX13, and
is built on the version of IMAGE released on MPE/iX 5.5 Express 3.
Customers who use DDX and think they may be susceptible to the problem
described (see below) can request either of these beta patches from the
HP Response Center.

Jon Bale CSY

Check your version of Image with Query using the Version command.  If
overall version is C.07.07 or greater, you have no DDX problems on 5.5

Mike Berkowitz
Guess? Inc.

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