----------
From:   Bryan O'Halloran[SMTP:[log in to unmask]]
Sent:   Wednesday, May 29, 1996 1:18 AM
To:     Multiple recipients of list HP3000-L
Subject:        Does ODBC work.
 
We have been trying to use ODBC for a while without success.  We have tried
Ethernet and Token Ring media. We have tried WfW 3.11 and Novell Winsocks.
We seems to be running the latest ODBC client and patch level 50.05  We
have tried as many variations as we can with no success even though the
various PCs can see the HP3000s (PING, Reflection etc). The error message
we get is "Logon Error 4053".
 
Bryan,
 
HP's ODBC does indeed work with the HP3000 with both Allbase and Image/SQL.
We have used it quite successfully using both the Reflection Network Series
(3000 Connection w/TCP) and with Windows 95 TCP/IP (although RNS is faster).
 
The Logon Error 4053 might be attributed to your ODBC.INI file settings which should
look something like this:
 
[INTERXSQ]
Driver=C:\WINDOWS\SYSTEM\allbase.dll
Description=Interex Medical Supply (Test Bed)
LastUser=#mpeix/idp950a.idpnet.com:interxsq.joe.tech,
        ws#<sess>,<user>/<upass>.<acct>/<apass>               (this line a continuation)
DefaultIsolation=RR
 
This is the one I use for my Interact columns when using ODBC.  The format of the
Lastuser line, which is the one that gets messed up most is:
 
   #mpeix               Indicates an MPE computer - an HP3000, as opposed to HP-UX
   /nodename                 The node.domain of the HP3000 which should be the one used
                                        when using Reflection over a network, or the IP node.domain
                                        name.  If not using Probe, then it should be resolvable with
                                        either through a local HOSTS file or DNS.
   :dbenvname                This is the DBEnvironment name for the Allbase database or
                                        the one used with Image/SQL previously created.
   ,ws                            This indicates "Windows Sockets" - there are other values
                                        which are listed in the PC/API.  Use the appropriate
                                        parameter for your network protocol.  If using RNS or Windows
                                        TCP/IP - use Windows Sockets.
   #<sess>,<user>...      This is a standard logon string, as used in :HELLO, optionally
                                        with passwords imbedded.
 
Basically, the areas you should be concerned with is this string (ensuring that this
is formatted correctly), and the network protocol used.  If the ODBC.INI parameters are
not created correctly, then you will not be able to log on.  If the network protocol does
not match the network parameter in the LastUser item, then you will not be able to
connect.
 
Also, ensure that the correct "listener" is started.  For Windows Sockets, use
 
    :ANSTART ARPA
 
If using Netware IPX/SPX, the parameter for ANSTART is NETWARE.  These are also
listed in the PC/API manual.  A listener is required to ensure a connection, and the
proper listener needs to be running which matches what the client is running.
 
Hope this helps...
 
Best Regards,
Joe Geiser