> john.hornberger said,
>
> [snip] ...
> new intrinsics, namely DBXBEGIN, DBXEND and DBXUNDO that will provide
> logical transaction atomicity to any single or multiple database
> appplication.  This transaction protection is connected to the XM of
> the MPE/iX operating system which will AUTOMATICALLY ROLLBACK any
> transaction that was partially completed as a result of a system problem.
>  Be it a lost connection, loss of power, software crash, etc.
>
> Why doesn't MANMAN or every other application on the HP3000 use this
> feature?  I don't know, you'll have to ask the vendor.  But, this is NOT
> a shortcoming of the DBMS or the OS.  It's a design choice by the vendor.

> A fairly poor choice IMO, but a choice just the same.

[a whole bunch of other stuff (thankfully) snipped] ...

For MANMAN, I don't think it is fair to say it's a "design" choice by the
vendor.  For obvious historical reasons, the "design" of MANMAN was
implemented years before the aforementioned new intrinsics as well as
ownership by the current vendor.  It would be better to say it is an
"upgrade" decision by the vendor, regarding "if" and "when", since
backfitting these new intrinsics will take time and manpower (read
"years").

MANMAN's Inventory Transaction Logs are not an example of the result
the O/S shortcomings.  It is more of an auditing tool.  I've actually met
some accountants and auditing firms that ask why every transaction and
command (i.e. Sales Order, Purchase Order) isn't logged.  But they asking
from the standpoint of auditing (being able to fix blame or error), rather
than the concept of rollback recovery.

Tracy M. Johnson
Measurement Specialties Inc.
Schaevitz Sensors Division