[log in to unmask] (Haixu Yang) wrote:
 
>I am trying to setup ODBC to access Image Database, I follow the manual
>(ALLBASE/SQL PC  API) did setup.
>But when I use query tool (msquery) to access the DBE from PC to HP,
>I always get "Logon error:27008".
>
>I suspect I didn't seup ODBC.INI right, would you please point out how
>to fix this?
>
 
I suspect the problem is in your ODBC.INI file too!!!!
 
>Here is the section in ODBC.INI I am using:
>[sysa1]
>Driver=3DC:\WINDOWS\SYSTEM\allbase.dll
>Description=3DPartsdb (sysa1)
>LastUser=3D#mpeix/sysa1:PartsDBE.MGR.YANG,ws#MGR.YANG/SESAME95
>DefaultIsolation=3D
 
Is the group that MGR.YANG homes to "MGR" as well? You might have group and
user mixed up.  Perhaps the fully qualified DBE name is PartsDBE.PUB.YANG.  To
determine the fully qualified name, issue the following command:
 
LISTF [log in to unmask],2
 
>
>and Here is part of message I get
>from DR.DeeBee Log File:
>
>SQLAllocEnv
>       0x00010000
>       SQL_SUCCESS
>SQLAllocConnect
>       0x00010000
>       0x00010000
>       SQL_SUCCESS
>SQLGetInfo
>       0x00010000
>       SQL_DRIVER_ODBC_VER
>       [0]
>       6
>       1
>       SQL_ERROR
>SQLError
>       NULL
>       0x00010000
>       NULL
>       NULL
>       NULL
>       NULL
>       0
>       NULL
>       SQL_SUCCESS_WITH_INFO
>SQLDriverConnect
>       0x00010000
>       0x7001
>       [9]DSN=3Dsysa1
>       SQL_NTS
>       [4]_+=02=02
>       256
>       22729
>       SQL_DRIVER_COMPLETE
>       SQL_ERROR
>SQLError
>       NULL
>       0x00010000
>       NULL
>       [5]S1000
>       20312
>       [19]Logon error: 27008.
>       511
>       19
>       SQL_SUCCESS
 
 
A DBERR 27008 is an Allbase/SQL error which would indicate a problem with the
dbe name (bad name or no alias db file).
 
 
 
>P.S. Here is the list of my configuration
>(1)
>We are running HP3000, MPE Release 5, and use TCP/IP(ARPA) connection.
>version of ALLBASE/SQL is A.F0.41
>Version of HP ALLBASE PC API Library is A.F0.31
>version of HP ALLBASE/SQL ODBC Driver is X.F0.14.a.
 
 
How are you running Allbase/SQL version A.F0.41 on MPE/iX 5.0? You must be
running G0.xx or G1.xx if you are on a release of MPE 5.0.
 
If you are running B.40.00 or C.45.00, HP requires that you are running A.F0.59
or greater of Allbase SQL.  The latest pass of F0 Allbase is F0.74!
 
The PC API versions you mention are rather old.  An the ODBC version is beta.
The latest releases of the Gupta API are:  F0.37 and G0.07.
The latest releases of the ODBC API are:  F0.19, G0.07, G1.02
 
>(2)
>I created a test DBE (sqlsetup.sampledb.sys) and start the ODBCVIEW form  DBE.
>(3)start the listner (anstart arpa debug), I am sure its running by look at
HPDANSLG.PUB.SYS
 
ANSTART ARPA DEBUG
 
Starts the G.0 listener that uses createprocess as part of its connection
architecture as opposed the F.0 server which spawns a job for every connection
request.  So you must be running some version of Allbase G.x on you server.
 
To determine the version of Allbase you are running, logon anywhere and issues
the SQLVER command.
 
Incidentally, the log file you should check if you are using the G.0 listener
is HPDAARLG.PUB.SYS.  HPDANSLG.PUB.SYS is the log file for the F.0
architecture.  NSCONTROL START initiates the server on F0 Allbase as opposed to
ANSTART on Gx.
 
Good Luck!
Peggy Lacy