Informix Connect
Tom
Informix SE (v7.23) wants to talk via (SETLITCP). Any new ODBC driver
I try wants to talk via (SESOCTCP). Does anyone know if an old
version of Informix Connect will talk via TLI? The oldest I can find
on IBM's website is v2.80.TC1. And it won't talk TLI either.
Thanks in advance,
Tom
Paul Watson
tli is what the server is supposed to be using, check the release
notes
--
Paul Watson #
Oninit Ltd # Growing old is mandatory
Tel: +44 1436 672201 # Growing up is optional
Fax: +44 1436 678693 #
Mob: +44 7818 003457 #
www.oninit.com #
Dave Kosenko
wrote:
If memory serves, on the Windows side you could never specify TLI as
Windows did not support it. I also seem to recall that the
combination you are using (TLI on the Unix side, SOC on the Windows
side) should work just fine, as what matters is the underlying
protocol (TCP). TLI and sockets (SOC) are just different libraries
for getting to the TCP layer.
Perhaps you should provide info on how the connection problem is
manifesting...
Dave
Paul Watson
way before winsock was in existence.
With tli/soc it's often easier to think in terms of the OSI model,
soc/tli would be the application layer, tcp the transportation
layer, ip the network layer. But bear in mind tcp/ip is only a four
layer model and does not map directly to the OSI model
--
Tom
What I've done:
---------------
In my sqlhosts file on my SCO server, I changed:
pei setlitcp eptsco sqlexec
pei2 setlitcp eptsco sqlexe2
to:
pei setlitcp eptsco sqlexec
pei2 setlitcp eptsco sqlexe2
pei3 sesoctcp eptsco sqlexe3
pei4 sesoctcp eptsco sqlexe4
I've checked to see what I have running, and I only
have two processes. One is "pei", and the other is
"pei2".
In my services file on my SCO server, I changed:
no Informix entries
to:
sqlexec 1525/tcp # INFORMIX SQLexec DAEMON
sqlexe2 1526/tcp # INFORMIX SQLexec DAEMON
sqlexe3 1527/tcp # INFORMIX SQLexec DAEMON
sqlexe4 1528/tcp # INFORMIX SQLexec DAEMON
I added these lines to my services file on my XP client:
sqlexec 1525/tcp # Informix SE server
sqlexe2 1526/tcp # Informix SE server
sqlexe3 1527/tcp # Informix SE server
sqlexe4 1528/tcp # Informix SE server
When I tried just substituting 'soc' for 'tli', it broke the app.
When I try to connect via ODBC, using Informix Connect:
(I used v2.81.TC2 initially, then I tried v2.80.TC1 with
same results.)
------------------------------------------------------------------------------------------------
When I run Setnet32...
Environment TAB
INFORMIXDIR=C:\Program Files\Informix\Connect\
INFORMIXSERVER=pei
INFORMIXSQLHOSTS=
Server Information TAB
IBM Informix Server - <pei>
Hostname - <server's IP address>
Protocolname - <sesoctcp>
Service Name - <1525>
Options - <empty>
Host Information TAB
Current Host - <server's IP address>
User Name - <informix>
Password Option - <password>
Password - <informix's password>
About Setnet32
9.53 2.81.TC2
When I run ILogin Demo...
Login parameters
Server pei
Hostname server's IP address
Servicename 1525
Protocolname sesoctcp
Username informix
Password informix's password
Stores Database Stores7 <or one of my databases>
I get an error message...
Message from ILogin Demo
Database: Sqlcode = -908
Refer to informix Find Error utility or
Informix Error Messages manual for
more details on this Error number.
Using Connect's Find Error, I get:
Attempt to connect to database server (servername)
failed.
The program or application is trying to access
another database server but has failed. Note the
server name in the current statement.
The desired database server is unavailable, or
the network is down or is congested. Ask your
DBA and system administrator to verify that the
server and network are operational. If the
network is congested, use the environment
variables INFORMIXCONTIME and INFORMIXCONRETRY
to tune connection timing. For information
on setting these environment variables, see
the Informix Guide to SQL: Reference.
This message appears in Version 6.0 and later versions.
..........
The server is up and running, as I'm running a
telnet session to it at the same time I'm doing
the above. The server itself shouldn't be
too burdened, as there are only three other
people who use it only occasionally. And I
don't THINK the network is a problem, as I
don't have a response time problem with my
telnet sessions. (Or my talking to our AS/400's
DB2 db either. (In a different building.))
..........
If I change the IP address to the hostname <eptsco>,
I get an error -930. Find Error says:
Cannot connect to database server servername.
The application is trying to access another
computer system but failed. Note the server
name in the current statement. Ask your network
administrator and DBA to check that the network
is operational and that the particular database
server is active. This message appears with
Version 6.0 and later.
-930 Cannot connect to remote host sitename.
INFORMIX-STAR or INFORMIX-NET is trying to
access another computer system but has failed.
Note the site name in the current statement.
Contact your network administrator, and ask for
a check that the network is operational and
that the particular site is active. This
message appears in database servers prior to
Version 6.0.
..........
This makes me think that I'm getting to the
"box", when I use the IP address, but not the
Informix engine. Would you agree?
When I try to connect using Data Direct:
----------------------------------------------------------------------
ODBC Informix Driver Setup
General TAB
Data Soutce Name: PentDDtax
Description: Pent tax db
tax
Connection TAB
Database List: emtpy
Default User Name: informix Use Default Login = unchecked
Host Name: server's IP address
Service Name: 1525
Server Name: pei
Protocol type: sesoctcp
Logon to INFORMIX window...
Database Name: tax
Host Name: server's IP address
User Name: informix
Password: informix's password
Warning window...
[DataDirect][ODBC Informix driver]Invalid attribute
in connection string: Description.[DataDirect][ODBC
Informix driver][Informix]Attempt to connect to database
server (pei) failed.
[DataDirect][ODBC Informix driver]Connection refused
If I check the "Use Default Login" checkbox, and
try to test the connection, I get:
Test Connection Error
[DataDirect][ODBC Informix driver][Informix]Attempt
to connect to database server (pei) failed.
Then I click on "OK", and I get:
Test Connection Error
[DataDirect][ODBC Informix driver][Informix]Connection
refused
Then I click on "OK", and I get:
[DataDirect][ODBC Informix driver]Invalid attribute
in connection string: Description.
other
--------
While looking for info that would help me, I
did come across a couple responses to questions
similar to my problem. The responses mentioned
something about permission for remote access.
I don't have a clue how to check this, assuming
it's really even a consideration.
Thanks so much for your help...
Tom
Paul Watson
have a Sco box.
Have you started sqlexecd ?
I would expect the Unix end to be
pei setlitcp eptsco sqlexec
with a line in /etc/services for sqlexec
at the PC end I tend to start with DBPing if it doesn't just work.
If DBPing doesn't work then nothing else will
Tom wrote:
>
> Great. Here goes...
>
[cutting]
> When I run Setnet32...
>
> Environment TAB
> INFORMIXDIR=C:\Program Files\Informix\Connect\
> INFORMIXSERVER=pei
> INFORMIXSQLHOSTS=
>
> Server Information TAB
> IBM Informix Server - <pei>
> Hostname - <server's IP address>
> Protocolname - <sesoctcp>
> Service Name - <1525>
> Options - <empty>
>
> Host Information TAB
> Current Host - <server's IP address>
> User Name - <informix>
> Password Option - <password>
> Password - <informix's password>
>
> About Setnet32
> 9.53 2.81.TC2
Looks OK, I tend to run regcopy after changing setnet32
>
> When I run ILogin Demo...
>
> Login parameters
> Server pei
> Hostname server's IP address
> Servicename 1525
> Protocolname sesoctcp
> Username informix
> Password informix's password
> Stores Database Stores7 <or one of my databases>
>
> I get an error message...
>
> Message from ILogin Demo
> Database: Sqlcode = -908
> Refer to informix Find Error utility or
Is sqlexecd listening on the port, you can use netstat -a on server
to check.
[cutting]
Art S. Kagel
NO NO NO NO
under the hood SOC and TLI are the SAME protocol, TCP/IP. The only difference
is the call level interface. Mist systems derived from BSD use the Sockets
library API while those derived from AT&T System V.4 use the TLI API. However,
they are COMPLETELY communications compatible and neither will know that the
other is using a different API. On the SCO UNIX (based on System V) use the
setlitcp definitions, on the PC in setnet32 and/or the ODBC setup (based on
Berkley Sockets likely because MS would not license TLI from a competitor) use
sesoctcp. Use the same port numbers/service names on both systems. ALL will
be well!
Art S. Kagel
Paul Watson
by Mircosoft
--
Tom
wrote:
>What does the release notes say the connection should be? I don't
>have a Sco box.
I don't understand what you mean.
>
>Have you started sqlexecd ?
Yes.
>
>I would expect the Unix end to be
>
>pei setlitcp eptsco sqlexec
>
>with a line in /etc/services for sqlexec
>
You mean like:
sqlexec 1525/tcp # INFORMIX SQLexec DAEMON
sqlexe2 1526/tcp # INFORMIX SQLexec DAEMON
sqlexe3 1527/tcp # INFORMIX SQLexec DAEMON
sqlexe4 1528/tcp # INFORMIX SQLexec DAEMON
>at the PC end I tend to start with DBPing if it doesn't just work.
>If DBPing doesn't work then nothing else will
Under the TCPIP TAB
[ ip found ] 0
9:18:35 AM : Ping IP 10.254.2.10 [ ip found ] 0 RoundTrip Time 7 ms
Packet Size 11 bytes Hello There
9:18:35 AM : Fully Qualified HostName: 10.254.2.10
9:18:35 AM : This Host has no Aliases
9:18:35 AM : Host IP Address(s) retrieved
In Service and Port information
(note - only service name worked, not port #)
9:19:57 AM : Service Name retrieved Sucessfully!
9:19:57 AM : This Service has no Aliases
Under the Native Connect TAB
SQLSTATE = 08004
SQLCODE = -908
08004 means "Data source rejected establishment of connection"?
Under the COM+ TAB
DSN=PentIBMtax;UID=informix;PWD=########
ATTEMPTING TO MAKE A CONNECTION
CONNECTION FAILED
-2147217843
[Informix][Informix ODBC Driver][Informix]Attempt to connect to
database server (pei) failed.
Under the ODBC TAB
9:26:11 AM : SQLAllocEnv Successful
9:26:11 AM : SQLAllocConnect Successful
9:27:33 AM : There was an error within SQLConnect!
9:27:33 AM : SQLState = 08004
9:27:33 AM : Native Error = -908
9:27:33 AM : Error Message = [Informix][Informix ODBC
Driver][Informix]Attempt to connect to database server (pei) failed.
In the release notes I found:
The IBM Informix TCP listener thread binds to a particular IP
address/port.
It listens for incoming calls addressed to only one IP address. If
there are
multiple IP addresses configured on the system, a TLI client will
not be able
to connect to the server. (If DNS is configured to resolve the
hostname on a
rotary of the four IP addresses, you do not know which of those
addresses
has been selected by the IBM Informix TCP listener).
The solution is that in the \$INFORMIXDIR/etc/sqlhosts file, use
"*hostname"
instead of "hostname". It will make the IBM Informix TCP listener
bind to
INADDR_ANY instead of a particular address.
Is this something that I need to worry about?
My impression is that we're the proverbial "this close". But whether
we are or not, I don't really know. Is there something that I should
have done on the SCO box? Is there something about "remote
connections" that I have to enable?
Thanks for all your help, it is appreciated.
Tom
Clive Eisen
> On Tue, 20 Apr 2004 21:33:28 +0100, Paul Watson <pa...@oninit.com>
> wrote:
snip
>
> My impression is that we're the proverbial "this close". But whether
> we are or not, I don't really know. Is there something that I should
> have done on the SCO box? Is there something about "remote
> connections" that I have to enable?
>
snip
>>Is sqlexecd listening on the port, you can use netstat -a on server
>>to check.
>>
I didnt see your answer to this
On the windows box try
telnet 1.2.3.4 1525
and see if you actually can connect
wher you put the ip address of your SCO box in place of 1.2.3.4
Paul Watson
>
> On Tue, 20 Apr 2004 21:33:28 +0100, Paul Watson <pa...@oninit.com>
> wrote:
>
> >What does the release notes say the connection should be? I don't
> >have a Sco box.
>
> I don't understand what you mean.
In $INFORMIXDIR/release/*/*/ there should be a number of files,
look for the engine release note and see what the connection should be
>
> >
> >Have you started sqlexecd ?
>
> Yes.
Did you export the environment when you started it. When you run
netstat -a can you see the listener on the port? Is it the port
you are expecting? Telnet to <ip> <port>, you should get a
connection closed message.
The ODBC testing will not work 'cos of the above. It's not something
dumb like a mixture of case is it?
>
> Under the COM+ TAB
> DSN=PentIBMtax;UID=informix;PWD=########
> ATTEMPTING TO MAKE A CONNECTION
> CONNECTION FAILED
> -2147217843
> [Informix][Informix ODBC Driver][Informix]Attempt to connect to
> database server (pei) failed.
[cutting]
Tom
wrote:
>What does the release notes say the connection should be? I don't
When I check for sqlexecd running, I use:
ps -eaf | grep sqlexec
and I see two processes running. "pei" and "pei2".
When I use the netstat -a command, I see:
eptsco.sqlexec
eptsco.sqlexe2
in the Local Address column, and the state for both is "LISTEN".
in the Foreign Address column I see "*.*".
>
>[cutting]
Tom
wrote:
>Tom wrote:
>>
>> On Tue, 20 Apr 2004 21:33:28 +0100, Paul Watson <pa...@oninit.com>
>> wrote:
>>
>> >What does the release notes say the connection should be? I don't
>> >have a Sco box.
>>
>> I don't understand what you mean.
>
>In $INFORMIXDIR/release/*/*/ there should be a number of files,
>look for the engine release note and see what the connection should be
>
>>
>> >
>> >Have you started sqlexecd ?
>>
>> Yes.
>
>Did you export the environment when you started it. When you run
>netstat -a can you see the listener on the port? Is it the port
>you are expecting? Telnet to <ip> <port>, you should get a
>connection closed message.
>
No, but it was running when I telneted into it. (It's set up to
bounce itself every night.)
As I mentioned in my earlier msg, I see both "pei" and "pei2" when I
use the netstat -a command. But nowhere do I see any mention of what
port they're listening on.
As for telnetting to it:
C:\
> telnet 10.254.2.10 1525
Connecting To 10.254.2.10...Could not open connection to the host, on
port 1525: Connect failed
Tom
wrote:
>Tom wrote:
>>
>> On Tue, 20 Apr 2004 21:33:28 +0100, Paul Watson <pa...@oninit.com>
>> wrote:
>>
>> >What does the release notes say the connection should be? I don't
>> >have a Sco box.
>>
>> I don't understand what you mean.
>
>In $INFORMIXDIR/release/*/*/ there should be a number of files,
>look for the engine release note and see what the connection should be
>
Looking in SE_7.2, it says one should use "tli" for tcp.
Clive Eisen
> As for telnetting to it:
>
> C:\
>
>>telnet 10.254.2.10 1525
>
> Connecting To 10.254.2.10...Could not open connection to the host, on
> port 1525: Connect failed
Anything in the informix log when you start sqlexecd?
Paul Watson
--
Tom
wrote:
>Have you got a firewall in the way ???
>
Not between me and this box. We are both behind our firewall.
Tom
How do I tell? I don't know if the process is being started with
logging or not. And even if it is, I don't know where to look for the
log. (It's just been way too long since I've played with this... :( )
Paul Watson
--
Paul Watson
Tom wrote:
>
> On Wed, 21 Apr 2004 17:33:48 +0100, Clive Eisen
> <cl...@serendipita.com> wrote:
>
> >Tom wrote:
> >> On Wed, 21 Apr 2004 16:15:36 +0100, Paul Watson <pa...@oninit.com>
> >> wrote:
> >snip
> >> As for telnetting to it:
> >>
> >> C:\
> >>
> >>>telnet 10.254.2.10 1525
> >>
> >> Connecting To 10.254.2.10...Could not open connection to the host, on
> >> port 1525: Connect failed
> >It ain't listening
> >
> >Anything in the informix log when you start sqlexecd?
>
> How do I tell? I don't know if the process is being started with
> logging or not. And even if it is, I don't know where to look for the
> log. (It's just been way too long since I've played with this... :( )
--
Art S. Kagel
> I thought SCO Unix was originally based on Xenix which was owned (??) by
> Mircosoft
SCO Xenix and SCO UNIX are different code bases. SCO Xenix WAS derived from
the original MS Xenix for IBM XT, but SCO UNIX was a pure port of System V.4.
Art S. Kagel
Tom
with it at all. (I had to ask one of the other guys where the heck it
was so I could check it!) I wanted to check, just to make sure that
Gateway didn't do anything with it. They didn't.
On Wed, 21 Apr 2004 17:55:02 +0100, Paul Watson <pa...@oninit.com>
Tom
What file would that be, and where do I find it?
(I've tried going thru the docs, but I can't find anything that says
one can find the log if it's running, as in my case. You just have to
know.)
On Wed, 21 Apr 2004 17:55:37 +0100, Paul Watson <pa...@oninit.com>
Paul Watson
in $INFORMIXDIR/lib AFAIR
--
Art S. Kagel
> So I need to look in the file that starts the sqlexecd processes. What file
> would that be, and where do I find it?
Usually it's placed in the system startup (rc) script either in /etc/rc,
/etc/rc<something>, or in /etc/init.d and linked to a link in /etc/rc.
Art S. Kagel
Tom
ftp client doesn't convert the Unix EOL characters to Windows, I'm
having to screw with it by hand. (I need it to look reasonably
normal, so I can read the darn thing.)
I'm working on it...
Art S. Kagel
Use WordPad instead of notepad. WordPad understands UNIX format text files.
Usually it's in \Program Files\Windows NT\Accessories for Win2000, but a
search for wordpad.exe will find it.
Art S. Kagel
Tom
I'm not finding anything that looks like it cranks up sqlexec. But
then I don't claim to be able to read Unix. Any chance you could
narrow it down a tad further? Or give me an idea of what I should be
looking for?
On Wed, 21 Apr 2004 14:25:48 -0400, "Art S. Kagel"
Paul Watson
Tom wrote:
>
> I found it, er, them. I have an rc, rc0, rc1, rc2 and rc3. Since my
> ftp client doesn't convert the Unix EOL characters to Windows, I'm
> having to screw with it by hand. (I need it to look reasonably
> normal, so I can read the darn thing.)
>
> I'm working on it...
>
[cutting]
Paul Watson
link back to /etc/init.d If they don't I'd expect it to be
in /etc/rc2.d and hopefully called something like S80informix
--
Tom
#!/bin/ksh
# S90informixse
# startup/shutdown informix standard engine daemon
#
# *******************************************************************
#
# VER DATE WHO COMMENTS
#
# 1.0 03-03-1996 CXT First write.
# 1.1 01-02-1997 CXT Change default informix server name to
standard "pei".
# ******************* STANDARD ENGINE 7 PROCESS *********************
case $1 in # test 1st
argument
start ) INFORMIXDIR=${INFORMIXDIR:-"/usr/informix"} # set informix
dir
export INFORMIXDIR # export
variable
SQLEXEC=$INFORMIXDIR/lib/sqlexec # define engine
export SQLEXEC # export
variable
INFORMIXSERVER=pei # define server
export INFORMIXSERVER # export
variable
$INFORMIXDIR/lib/sqlexecd $INFORMIXSERVER # run the
daemon
INFORMIXSERVER=pei2 # define
server
export INFORMIXSERVER # export
variable
$INFORMIXDIR/lib/sqlexecd $INFORMIXSERVER # run the
daemon
;; # terminator
stop ) ;; # do nothing if
shutdown
esac # end-case test
# ******************* END OF SCRIPT *********************************
It doesn't look like it is logging to me.
On Wed, 21 Apr 2004 14:25:48 -0400, "Art S. Kagel"
Art S. Kagel
> I think I got it...
Yes, that's it.
No, it's not. If it was the line would look like:
$INFORMIXDIR/lib/sqlexecd -l $INFORMIXDIR/sqexecd.log $INFORMIXSERVER
if memory serves (it's been awhile).
Art S. Kagel
Paul Watson
/usr/informix/lib/sqlexecd pei -l /tmp/mylogfile
--
Paul Watson
root[luey_net]: ps -ef | egrep sqle
root 13860 13849 0 21:04:20 pts/2 0:00 egrep sqle
root 10305 1 0 Mar 19 ? 0:00 /home/informix/lib/sqlexecd
luey_net
cutting from netstat -a
luey.oninit.com.lueynet *.* 0 0 0 0
LISTEN
cutting from sqlhosts
luey_net setlitcp luey lueynet
luey_920 ontlitcp luey luey920
root[luey_net]: egrep luey /etc/services
lueynet 1531/tcp
luey920 1533/tcp
luey731 1534/tcp
--
Tom
$INFORMIXDIR/lib/sqlexecd $INFORMIXSERVER # run the daemon
$INFORMIXDIR/lib/sqlexecd $INFORMIXSERVER # run the daemon
to:
$INFORMIXDIR/lib/sqlexecd $INFORMIXSERVER -l /tmp/pei.log # run
the daemon
$INFORMIXDIR/lib/sqlexecd $INFORMIXSERVER -l /tmp/pei2.log # run
the daemon
This should get me logging, no?
On Wed, 21 Apr 2004 20:55:49 +0100, Paul Watson <pa...@oninit.com>
Tom
On Wed, 21 Apr 2004 21:02:53 +0100, Paul Watson <pa...@oninit.com>
David Williams
"Tom" <tsm...@eastpointcity.org> wrote in message
news:cs3d80pgv33947suj...@4ax.com...
Go to http://www.iiug.org/software/index_JAVA.html
get jselect and use it to connect using the port NUMBER rather than a
name.
This eliminates the translation from service name to port number.
Then try it from on the machine using the machine name from
uname -a
and the port NUMBER
This eliminates the translation from machine name to ip address on the
client as well.
malcolm
Malcolm
"Art S. Kagel" <ka...@bloomberg.net> wrote in message news:<pan.2004.04.21.13...@bloomberg.net>...
Tom
2004-04-21 23:19:56.370000 Starting Daemon INFORMIX-SQL Version
7.23.UC13
Command Line = /usr/informix/lib/sqlexecd pei -l /tmp/pei.log
INFORMIXDIR = /usr/informix
dbservername = pei
nettype = setlitcp
hostname = eptsco
servicename = sqlexec
options =
2004-04-21 23:33:59.840000 sqlexec eptsco informix -p(null)
2004-04-21 23:34:02.340000 sqlexec eptsco informix -p(null)
2004-04-21 23:34:34.100000 sqlexec eptsco informix -p(null)
2004-04-21 23:36:28.270000 sqlexec eptsco informix -p(null)
2004-04-21 23:36:52.370000 sqlexec eptsco informix -p(null)
2004-04-21 23:39:20.860000 sqlexec eptsco informix -p(null)
2004-04-21 23:39:33.140000 sqlexec eptsco informix -p(null)
2004-04-21 23:40:52.890000 sqlexec eptsco informix -p(null)
2004-04-21 23:41:22.680000 sqlexec eptsco informix -p(null)
2004-04-21 23:42:01.200000 sqlexec eptsco informix -p(null)
2004-04-21 23:42:07.650000 sqlexec eptsco informix -p(null)
2004-04-21 23:42:59.320000 sqlexec eptsco informix -p(null)
2004-04-21 23:45:48.410000 sqlexec eptsco informix -p(null)
2004-04-21 23:49:32.880000 sqlexec eptsco informix -p(null)
2004-04-21 23:58:35.200000 sqlexec eptsco informix -p(null)
2004-04-21 23:58:36.300000 sqlexec eptsco informix -p(null)
2004-04-21 23:58:38.550000 sqlexec eptsco informix -p(null)
2004-04-21 23:58:42.470000 sqlexec eptsco informix -p(null)
2004-04-21 23:58:44.570000 sqlexec eptsco informix -p(null)
2004-04-21 23:58:48.160000 sqlexec eptsco informix -p(null)
2004-04-21 23:58:49.630000 sqlexec eptsco informix -p(null)
2004-04-21 23:58:55.250000 sqlexec eptsco informix -p(null)
2004-04-21 23:58:56.860000 sqlexec eptsco informix -p(null)
2004-04-21 23:58:59.510000 sqlexec eptsco informix -p(null)
2004-04-21 23:59:00.320000 sqlexec eptsco informix -p(null)
2004-04-21 23:59:02.350000 sqlexec eptsco informix -p(null)
2004-04-21 23:59:04.280000 sqlexec eptsco informix -p(null)
2004-04-21 23:59:06.800000 sqlexec eptsco informix -p(null)
2004-04-22 01:00:03.890000 sqlexec eptsco informix -p(null)
And here is the "pei2" log:
2004-04-21 23:19:56.400000 Starting Daemon INFORMIX-SQL Version
7.23.UC13
Command Line = /usr/informix/lib/sqlexecd pei2 -l /tmp/pei2.log
INFORMIXDIR = /usr/informix
dbservername = pei2
nettype = setlitcp
hostname = eptsco
servicename = sqlexe2
options =
So far, I can't get anything to flush out into the log. I keep trying
to connect, and failing, but the log isn't growing. Perhaps if I shut
Informix down? If so, how would I do that? In the meantime, I'll try
connecting a while longer, to see if any buffer(s) get flushed.
Tom
On Wed, 21 Apr 2004 17:33:48 +0100, Clive Eisen
<cl...@serendipita.com> wrote:
Tom
2004-04-22 23:19:55.060000 Starting Daemon INFORMIX-SQL Version
7.23.UC13
Command Line = /usr/informix/lib/sqlexecd pei -l /tmp/pei.log
INFORMIXDIR = /usr/informix
dbservername = pei
nettype = setlitcp
hostname = eptsco
servicename = sqlexec
options =
2004-04-22 23:33:45.560000 sqlexec eptsco informix -p(null)
2004-04-22 23:33:48.900000 sqlexec eptsco informix -p(null)
2004-04-22 23:34:21.780000 sqlexec eptsco informix -p(null)
2004-04-22 23:36:20.420000 sqlexec eptsco informix -p(null)
2004-04-22 23:36:45.330000 sqlexec eptsco informix -p(null)
2004-04-22 23:39:16.680000 sqlexec eptsco informix -p(null)
2004-04-22 23:39:30.420000 sqlexec eptsco informix -p(null)
2004-04-22 23:41:06.390000 sqlexec eptsco informix -p(null)
2004-04-22 23:41:37.690000 sqlexec eptsco informix -p(null)
2004-04-22 23:42:17.600000 sqlexec eptsco informix -p(null)
2004-04-22 23:42:24.620000 sqlexec eptsco informix -p(null)
2004-04-22 23:43:19.480000 sqlexec eptsco informix -p(null)
2004-04-22 23:46:11.960000 sqlexec eptsco informix -p(null)
2004-04-22 23:49:59.610000 sqlexec eptsco informix -p(null)
2004-04-22 23:58:47.760000 sqlexec eptsco informix -p(null)
2004-04-22 23:58:48.810000 sqlexec eptsco informix -p(null)
2004-04-22 23:58:51.110000 sqlexec eptsco informix -p(null)
2004-04-22 23:58:55.000000 sqlexec eptsco informix -p(null)
2004-04-22 23:58:56.650000 sqlexec eptsco informix -p(null)
2004-04-22 23:58:59.580000 sqlexec eptsco informix -p(null)
2004-04-22 23:59:00.740000 sqlexec eptsco informix -p(null)
2004-04-22 23:59:06.090000 sqlexec eptsco informix -p(null)
2004-04-22 23:59:07.600000 sqlexec eptsco informix -p(null)
2004-04-22 23:59:09.390000 sqlexec eptsco informix -p(null)
2004-04-22 23:59:10.320000 sqlexec eptsco informix -p(null)
2004-04-22 23:59:12.580000 sqlexec eptsco informix -p(null)
2004-04-22 23:59:14.820000 sqlexec eptsco informix -p(null)
2004-04-22 23:59:17.730000 sqlexec eptsco informix -p(null)
2004-04-23 01:00:04.000000 sqlexec eptsco informix -p(null)
And here's the "pei2" log:
2004-04-21 23:19:56.400000 Starting Daemon INFORMIX-SQL Version
7.23.UC13
Command Line = /usr/informix/lib/sqlexecd pei2 -l /tmp/pei2.log
INFORMIXDIR = /usr/informix
dbservername = pei2
nettype = setlitcp
hostname = eptsco
servicename = sqlexe2
options =
2004-04-22 23:19:55.100000 Starting Daemon INFORMIX-SQL Version
7.23.UC13
Command Line = /usr/informix/lib/sqlexecd pei2 -l /tmp/pei2.log
INFORMIXDIR = /usr/informix
dbservername = pei2
nettype = setlitcp
hostname = eptsco
servicename = sqlexe2
options =
What now?
Thanks,
Tom
Alessandro Monti
> (I used v2.81.TC2 initially, then I tried v2.80.TC1 with
> same results.)
works with SE 7.2 (on SCO)
> --------------------------------------------------------------------------
----------------------
> When I run Setnet32...
>
> Environment TAB
> INFORMIXDIR=C:\Program Files\Informix\Connect\
> INFORMIXSERVER=pei
> INFORMIXSQLHOSTS=
>
You can put also
DBPATH=/usr/db/
(the directory "up" the dir with the isam files)
I'm not an expert, but i've accessed various DB even with Access, with a
little work and test, but always with these old drivers.
Hope this helps.
By
Alessandro Monti