HP3000-L Archives

April 1995, 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:
Peggy Lacy <[log in to unmask]>
Reply To:
Peggy Lacy <[log in to unmask]>
Date:
Wed, 5 Apr 1995 21:10:47 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
[log in to unmask] wrote:
>
> In my attempt to access IMAGE/SQL on our HP3000 ( MPE/iX 4.5) from IMPROMPTU
> with the ODBC driver that came with IMAGE/SQL, I get the following message:
>
>      PC Sockets error: 10022 (PCSockets !1)
>
> I can not locate this message in any reference manual.  Can anybody help me?
>
> My PC is running with Tumpet WINSOCK. Here is my LastUser syntax in ODBC.INI:
>
> LastUser=#mpeix/STELLANS:SIGADBE.MGEORGES.SIGA01,ws#,MGEORGES/?.SIGA01/?
>
> TIA!
>
> Georges Bourgeg <[log in to unmask]>
 
PC Sockets error is a WINSOCK error code which equates to Berkeley
Sockets equivalent EINVAL or invalid argument.  This is an error
at the network level and probably has nothing to do with your
ODBC.INI file.  I am not familiar with a TCP-IP vendor called
Tumpet, but I would check your protocol.ini or net.cfg file for
packet size settings.
 
You might want to create an SQLX trace which will let you know
if you ever get out onto the net at all.  If you are using the
G.0 connection architecture, you can bring up your listener
with debug as well, i.e.,
  ANSTART ARPA DEBUG
 
Look in the readme.hp file for information on tracing.
>

ATOM RSS1 RSS2