Ken Paul warns sites on 6.0 of a potential problem:

> Since the beginning of the year we (Adager) have dealt with
> at least 2 sites who have experienced system failures/hangs
> and upon rebooting there machines have had problems with
> their IMAGE databases.  ......
>
> .....  he believes that there is a corner case bug within
> the new XM code for 6.0 which he is now going to develop a
> patch.
> .....  a new feature on 6.0 (and only 6.0) within the XM which
> would prevent the problem from happening.
>
> By default this option is disabled when you install 6.0 and
> if you enable it for your volume sets then you should not
> experience the problem mentioned above .......
>
> showchkptstat <volset-name>
>
> alterchkptstat <volset-name> ENABLE|DISABLE
> ......
> 1.  I feel that the users should know of a potential data
> corruption problem (no matter how obscure .....
>
> 2.  I really don't want to fix more databases than I have to
> and also have the VERY UNPLEASANT task of telling a user
> that some of their data is gone from their IMAGE database.

Since potentially losing data from your IMAGE database is about
as serious a problem as one can have on a 3000, I expect
everyone (including HP) should thank Ken Paul for his service to
the user community in posting the above.  Especially since the
apparent fix only involves issuing a standard 6.0 VOLUTIL
command (O.K.:  and probably rebooting...).

I trust HP will make sure a patch that fixes this or a warning to do
the above is sent out with all copies of 6.0 / 6.5 that are shipped
from here on out...

Ken Sletten
SIGIMAGE Chair