HP3000-L Archives

May 1999, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Wed, 5 May 1999 12:47:59 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (91 lines)
Get in touch with [log in to unmask] They developped ODBCLink/SE for HP and
have a good knowledge of the product.

daniel a écrit:

> I'm trying to connect my excel2000 to a Image/SQL Database
> (DBBSW.ADMSII.SOMA9000).
>
> Version Information
>
> We use MPE/iX 6.0
> With Image/SQL version : HP36385B B.G2.07
> ODBClink SE-32 version E.56 (5.56)
>
> The steps I followed.
>
> I followed the ODBClink/SE reference manual during the installation.
>
> I first steamed the job as it was done in the manual.
>
> #J236   EXEC QUIET  10S LP       MON 11:27A  ODBCLNSE,MANAGER.SYS
> . And it running  nice and quiet!
>
> The next step I took, was downloading the ODBCSE32.EXE file from our HP3000
> server.
>
> I installed the client like this:
>
> Driver     : odbclink - 32 se
> Database connection name : DBBSW
> Database name  : DBBSW
> Server name / IP address : 192.0.0.1 (The IP address of our HP3000 server)
> Logon session   : ODBC
> Logon username  : MGR
> Logon account   : SOMA9000
> Logon group   : ADMSII
> Logon password  : <Empty>
>
> The database, username, group and the account exist, the password for the
> user, account and group are not filled, so I do not have to put any
> passwords to access the database.
>
> So I tested it from Excel (MS-Query) and I got the following error:
> 27008 Database Environment alias not found (or something like that)
>
> So I took a deep breath and I started over and over again searching trough
> almost 15 kilos of paperwork from HP, and in the end I found, that you are
> able to set a DBE alias with netutil.
> So I did that as follows:
>
> Alias Name: dbbsw
> Database Server Type: ALLBASE/SQL
> DBEnvironment Name on Server: dbbsw.admsii.soma9000
> Server Node Name: 192.0.0.1
> Machine Type: HP3000 S900
> Datacomm Type: NS
>
> I tested it with Excel and with ODBCUTSE DBBSW and I got an error telling me
> that the server node name (That is the server name, isn't it ?) must begin
> with an alpha character.
> So I was thinking, if SERVER NODE NAME is equal to the system name, OK, lets
> edit the HOSTS.NET.SYS file and add this new entry
> 192.0.0.1 HP3000 IMAGESQLSVR
> I also added an entry for our HP9000 system and I was able to make a
> connection with
> telnet using only the hostname as specified in HOSTS.NET.SYS
> So the host file was working as it should be (how nice!)
> So I changed the ALIAS of DBBSW and replaced 192.0.0.1 with HP3000. I also
> changed the database name on the client in DBBSW (It was
> DBBSW.ADMSII.SOMA9000). And wow, as if it was a miracle, it worked, well for
> 5 seconds that is. . .
>
> When I tried it again in excel (and with ODBCUTSE) I got the following
> error:
>
> 1/SYS/ODBCSE:odbcutse dbbsw
> MB Foster ODBC Utility Version E.56.12
> Connecting to DBEnvironment dbbsw...
> [Allbase]NetIPC Error: Socket name not found. (DBERR 30037)
>
> Well, and this is more or less the point where my brain crashed.
>
> Does somebody knows what I'm doing wrong?
> Can somebody give me a hint?
>
> If any additional information is required, please mail me and you get it
> a.s.a.p.
> Greetings
> Daniel O.A. van Doorn
> [log in to unmask]

ATOM RSS1 RSS2