Conference orarep::nomahs::dbintegrator_public_public

Jean-Paul,

You must have version 3.1a??  The next release, which is now if field test, includes
32 bit PC Data Gateway servers for Intel NT and for Alpha NT.  When installed on NT
systems PC Gateway can run as an NT service.  What data do you plan
to access?  We only include a SQL Server ODBC driver on our Alpha kit, though
more may be available elsewhere.

Have you actually tried to install the 16 bit Intel PC Data Gateway server on
your Alpha NT system?  I've not tried this, but have heard that many Intel images
(including PC Gateway server) will run interpretively on Alpha.

-chipper

Sorry
about
my
last
reply.

I use DECwindows notes which, apparently, makes
replies longer then 80 column/line.

Curriosity got the best of me.  I tried installing
some of the 16 bit PC Data Server components on an
Alpha running NT 3.15.  I did not have easy access to
a complete kit, so I did not do a complete install, but
what I tried worked.  Next I ran the 16 bit, Intel
agent on the Alpha.  I didn't try to fetch any data,
but the Agent came up.

So again I ask, did you actually try to use the 16
bit Intel images, or did you logically assume
that Intel images wouldn't work on Alpha?

You might need to use the 16 bit ODBC Administrator
since the 16 bit Executor will be using the 16 bit
ODBC registration database.  Also, I would strongly recommend
that you stick to 16 bit drivers when using 16 bit
PC Data Gateway.  Though some 32 bit drivers might
seem to work, this is NOT a support configuration and
we have seen errors with the SQL Server 32 bit ODBC driver
when used with 16 bit PC Data Gateway server.

And now that I have said all of the above, you might
still rather sign up as an FT2 field test site and
get the native, 32 bit Alpha images.

Hello,

After unpacking the exe file on a windows95 PC, I manage to copy the files to
 the ALPHA WINDOWS NT platform.
I install successively DBI gateway for PC data and ODBC provided with DBI.
The client part starts successfully, but when running the executor, I get the 
followinf error :


WSACONREFUSED, error while connecting to ...
Failed to initialize network environment.


I think we better go ahead to use the ALPHA field test version of the gateway
 server.

Could you let me know how I can apply to get this version.

Thanks.


Jean-Paul.

WSACONREFUSED, error while connecting to ...
Failed to initialize network environment.


Are you convinced that your TCP/IP environment
is set up / configured correctly?  If yes (as in
you can PING yourself and PING your Alpha from
the machine where the client is installed), do
you have NT workstation as opposed to NT server
installed?  If NT workstation, any change you have
attempted to exceed the 10 connect limit?

The error above can come about under a number of
different circumstances.  If I assume correctly
that you have never run PC Gateway server successfully,
the first thing I would check would be TCP/IP
configuration.

-chipper

    
    Hi Jean-Paul,
    
    Additionally we can make the ft kit available to you. Could you send
    both your surface mail and email addresses plus phone number info to
    [email protected]?  I could then pass the info on to our ft admin
    folks and send you a pointer to the files.  This has to be for internal
    digital use only - if not then their are ft agreements that need to be
    signed, etc.
    
    Thanks,
    	
    dan

We fix the TCP/IP problem. The TCP/IP address was not set properly.
It is possible now to run the agent and executor on the alpha platform.
However I experienced a new error which is probably due to a wrong version of
ODBC.DLL, maybe we still have the 32 bits version.


-->
SQL> ATTACH 'FILENAME/TYPE=ODBC/NODE=LAPOST/DATABASE=ORFDB';
%SQL-F-ERRATTDEC, Error attaching to database /TYPE=ODBC/NODE=LAPOST/DATABASE=OR
FDB
-DBI-E-ATTACHERR, Error attaching database, Connect string='/TYPE=ODBC/NODE=LAPO
ST/DATABASE=ORFDB'
-RDB-E-BAD_DB_FORMAT, /DATABASE=ORFDB/DBKEY_DEFAULT_MODE=READ_ONLY/NOAUTOCOMMIT/
NODE=LAPOST/NOENFORCE_ALL_TXN/PORT_NUMBER=4299/TRANSPORT_TYPE=TCP/TX_MODE=WARN_1
PC/TYPE=ODBC does not reference a database known to DEC DBI Gateway
-LDRV-E-CANT_CONNDB, Can NOT connect to database /DATABASE=ORFDB/DBKEY_DEFAULT_M
ODE=READ_ONLY/NOAUTOCOMMIT/NODE=LAPOST/NOENFORCE_ALL_TXN/PORT_NUMBER=4299/TRANSP
ORT_TYPE=TCP/TX_MODE=WARN_1PC/TYPE=ODBC
-LDRV-E-ODBC_CONNECT_EN, Network connection has ended
-LDRV-E-UDB_SUPP, [Microsoft][ODBC DLL] Data source name not found and no defaul
t driver specified


Thanks.

Jean-Paul.

    Hi Dan,

    I send all mail details via a separate mail.
    
    Thanks,
    	
     Jean-Paul.

>>However I experienced a new error which is probably due to a wrong version of
>>ODBC.DLL, maybe we still have the 32 bits version.

Glad to hear that things are moving forward.  Time invested in sorting out
the TCP/IP problem was well spent as this will need to be right for
you to use the native 32 bit FT images when they arrive.

If you have used the 32 bit ODBC administrator to create data source
ORFDB the error you have posted would likely result.  However, this error
could also result for other reasons, such as using the wrong name for the
/DATABASE qualifier, etc.  If you have disk space and time to play, you
should be able to copy the self expanding ODBC 16 bit archive to your Alpha
NT workstation, expand and install it.  (It won't over write the 32 bit
administrator - the 2 can co-exist.)  Use the 16 bit administrator to
redefine your data source, then use your new data source name in your
attach string.

Or, if you are busy and not in a hurry, you can just wait for the
32 bit images to show up.  But note, you need to be sure that the
account that runs the PC Data Gateway server can "see" your ODBC
data source definitions.  A way to be sure that this happesn is
to use the same account to create the ODBC data source definitions
as that from which you run the PC Gateway server.  Now if you
elect to run the PC Gateway server as an NT service.....(We
can save that for another day.)