Re: configuring sqlexecd for remote tcp connections.. problems :(

matthewlenz@gmail.com wrote: > matthewl...@gmail.com wrote: > >>Jonathan Leffler wrote: >> >>>>I'd like to verify my settings with you guys to see if you spot any >>>>issues: >>>> >>>>here are the contents of the $INFORMIXDIR/etc/sqlhosts on the SERVER >>>>after I added the last line: >>>> >>>>demo_on onipcshm on_hostname on_servername>>>>demo_se seipcpip se_hostname sqlexec >>>>tms_se sesoctcp coca sqlserv >>>>local_se seipcpip coca sqlexec >>>>localse_remote setlitcp coca 1526 >>> >>>OK - sorta. Usually, you use a service name, but the number should work >>>too. SCO might use setlitcp, but the previous entry - tms_se - suggests >>>that (a) it might use sesoctcp instead, and (b) there may already be a >>>service ready and waiting. >> >>I'll try 'soc' on both. > > > ON THE SERVER > > i removed my localse_remote and created a new entry: > > remote_se sesoctcp coca sqlserv > > I added: > > sqlserv 1526/tcp > > to the /etc/services file > > running: > > $INFORMIXDIR/lib/sqlexecd remote_se > > resulted in: > > daemon err = 25507: The specified service name or protocol is unknown. > > But it did run before when I was using 'tli'. So the question is can > the sqlexecd use 'tli' and the client use 'soc'? Yes. The underlying communication protocol is identical for TLI and Sockets. The only difference is in the source code level library calls needed to implement the protocols in code. > I modified the remote_se connection to setlitcp and reran the sqlexecd > command above and it started just fine. Keep in mind that there was no > sqlexecd running before I started all this stuff and NO services > listening on 'sqlserv' because that service entry didn't even exist. i > don't know why that tms_se entry was added. I even tried sqlexecd > tms_se and it resulted in the same 25507 error. > > so basically it looks like sco sqlexecd doesn't like 'sesoctcp' but > runs when I use 'setlitcp'. SCO UNIX is System V based so it supports TLI natively and so tlitcp is what IDS is coded to use there. On BSD based platforms (ex: Linux) Sockets is native and so soctcp is supported there. The release notes tell you which protocols are supported in a particular release. <SNIP> > remember I mentioned that when I use dbaccess on the server I have to > use dta@local_se to connect to the database. I have no idea what the > dta part is I thought it was a username. I think this stuff probably > works, but its me not having a clue about informix :( The 'dta@' is the name of the database. For SE it means that on the server there's a directory named dta.dbs containing the database's data and metadata files. Art S. Kagel