Hello,

We are a reseller of the HP 3000 and are trying to make strategic
decisions about using the machine for future development.

First let me say that I have been a big supporter of the HP in the
past, but have waited a long time for some of these things.  If nobody
on the list has come up with a reasonable work around, it looks like
we will have to look elsewhere for future development.  I am using
Allbase for some of these functions, but the new systems make Allbase
cost significantly higher than before.  So we are forced to use
ImageSQL, but only if we can overcome these problems.

1) Will HP ever support a date type in Image that works with ODBC and
Query?  (K8 doesn't work in Query, or DBFIND and is inconsistant
across ODBC drivers).
2) Will HP ever support BLOB fields or atleast treat some nXn
structures as BLOB fields?  (ODBC drivers that are not HP's support
some of this, but the ImageSQL maps do not, so ISQL is a problem and
so is Query).

Also, we have been trying to use FTP as a replacement for RJE as many
of our partners (non-HP) support both.  But the HP FTP has some
distinct compatability problems.  Most FTP clients send the entire GET
or PUT command string to the host for interpretation.  This allows
LOGON and other commands to be sent after the filename on the
commands.  The HP FTP Client only sends the commands up to the 3rd
space.  For example:

PUT XYZ "LOGIN BOB"

is sent as

PUT XYZ "LOGIN

This means that we have to use PC's to transmit using FTP.

Has anyone else encountered this problem or has anyone figured out a
work around?

That's all for now.

Rgds
Mel
[log in to unmask]

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