Hello all TurboIMAGE and Image/SQL users:

I noticed that the following was recently published by HP
under "Database News":
================================

HP Eloquence is a relational database which features
TurboIMAGE compatibility extensions, making it an invaluable
tool for HP e3000 transition projects for small to mid-range
customers. HP Eloquence has been evaluated by HP and its
SIGSoftvend partners, and technically endorsed by SigIMAGE's
Image/SQL Advisory Committee (ISAC). It is supported on HP-UX, Windows/NT
and Linux.

More information is available at
http://www.hp-eloquence.com/
==================================

It is correct that the ISAC endorsed HP Eloquence as the
best solution for some customers that are planning to
migrate.  But reflecting on the final abbreviated published
version as I see it now, I would like to clarify and expand
a bit on what "technically endorsed" means in this case;
i.e.:  Following is full text of the endorsement that was
reviewed by the ISAC and forwarded to HP by me.  Note there
are a couple caveats which may be important to some sites:
--------------------------------------------

The ISAC supports HP Eloquence as the best solution for
small to medium MPE customers that are planning to migrate
as recommended by HP;  with the understanding and caveat
that HP will work with appropriate third-parties to make
the HP Eloquence "infrastructure" more robust;  and that
HP will lay out for the MPE user community how long and
in what fashion HP as a company will "stand behind" the
product.
--------------------------------------------

There was no agreement or even informal understanding that
HP would always include the full text of the ISAC endorsement
every time it was mentioned.  However, I wanted to make sure
that all IMAGE users are aware of the entire "package".

In saying the above I do not mean to in any way, shape, or
form cast negative aspertions or etc. on HP Eloquence.  It
really does appear to be a very good product;  it even has
some features that are not currently supported by the "real"
TurboIMAGE;  For example: Read-only DB Locks.  And I believe
HP already has efforts underway to make the HP Eloquence
"infrastructure" more robust.

But given that sites who DO decide to migrate to other
platforms probably do not want to repeat that experience any
more often than necessary, I also believe it was and is a
fair request to ask HP to indicate how long and in what way
HP as a company will stand behind the product.  I've been
rather busy with "real work" lately and have not been able
to keep up with everything as well as I would have liked.
So it's possible I may have missed an "HP will stand behind
HP Eloquence" type statement.  All I can say is I haven't
noticed any specifics on that yet (if anybody else has,
please give me a pointer).

Finally, please note that the above endorsement was not meant
to imply that I think all IMAGE users should migrate;  quite
the contrary...  But that's a whole 'nother OpenMPE story...
:-)

Ken Sletten
SIGImage/SQL Chair
Member, OpenMPE Inc. BoD

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