Problem connecting to SE 7.1 on SCO
Posted in 1998
Topics: Connectivity: ODBC / JDBC / .NET, Networking & sqlhosts Configuration
Hi, I want to connect windows applications (using ODBC) to a Informix-SE v7.10 database server running on a SCO/Intel platform. The problem is: The communication protocol used by the DBMS on the SCO machine is "setlitcp" (That's what I have in the sqlhosts file). But the Informix Setnet32 utility does not offer this choice in the protocol list, could this explain why the connecting does not work ? To my knowledge this is the only protocol available on the SCO version of SE 7.10. If you can share any ideas on this, please let me know. Thanks for the help, C.Allaire (callaire@ergonet.com) Programmer-analyst Ergonet 7400 Les Galeries D'Anjou Bureau 320 Anjou (Quebec) H1M 3M2
My understanding is that seTLItcp is for unix tcp (transport layer interface or something like that). seSOCtcp is for Windows tcp (Sockets), Leave it to Microsoft to do it thier way! Set your setnet32 protocol to sesoctcp. We are using 7.10 IDS in SCO and access via ODBC.
Shannon Sellers wrote: > > My understanding is that seTLItcp is for unix tcp (transport layer interface > or something like that). > > seSOCtcp is for Windows tcp (Sockets), Leave it to Microsoft to do it thier > way! > > Set your setnet32 protocol to sesoctcp. We are using 7.10 IDS in SCO and > access via ODBC. Noooo! Informix implements its network layer in EITHER BSD style sockets code or SystemV style TLI code depending on which is the native network library for a particular system and therefore more efficient. Almost all modern UNIXes today provide both libraries but one is always implemented as a layer over the other and is therefore inherently at least a little slower. The release notes for your particular release will tell you whether to use <on|se>tlitcp or <on|se>soctcp. It is true that the windows implementations are all Sockets based because that paradigm more closely matches the native windows network layer and there are many sockets implementations for Windows OS's. Art S. Kagel