Very Computer

Hi informix'ers
can I connect my online 5.0 UNIX database from my online 7.1 NT machine..?
I edit the sqlhosts registry on NT adding new key for my unix database but
when I connect from dbaccess giving me error message 908 attempt to connect
to databse server failed...?

any hints...

thanks...

Quote:> Hi informix'ers
> can I connect my online 5.0 UNIX database from my online 7.1 NT machine..?
> I edit the sqlhosts registry on NT adding new key for my unix database but
> when I connect from dbaccess giving me error message 908 attempt to connect
> to databse server failed...?

> any hints...

> thanks...

Do you have the INFORMIX-STAR product loaded on the UNIX node?
Do the entries in your etc/services match on both machines?
The default service name used in version 5.x was sqlexec on port 1525/tcp,
but the default service name used in version 7.x seems to be turbo.

For example:
In the /etc/services file on the UNIX node -
sqlexec         1525/tcp        # Informix network daemon

In the \WINNT35\system32\drivers\etc\SERVICES file on the NT node -
turbo           1525/tcp        # Informix-OnLine Dynamic Server

You must make the service name and the port number match on both nodes.

For example:
In the /etc/services file on the UNIX node -
turbo           1525/tcp        # Informix network daemon

In the \WINNT35\system32\drivers\etc\SERVICES file on the NT node -
turbo           1525/tcp        # Informix-OnLine Dynamic Server

Note: You may need to re-boot after you change an entry in the services file.

You will also need to make sure that the $INFORMIXDIR/etc/sqlhosts file
on the UNIX node contains entries for the NT node.

For example:
In the $INFORMIXDIR/etc/sqlhosts file on the UNIX node -
# dbservername  nettype         hostname        servicename
#----------------------------------------------------------
ol_mypc         olsoctcp        mypc            turbo

Note: The dbservername needs to match the DBSERVERNAME entry in the
      onconfig file on the NT node.
      The nettype should be either olsoctcp or onsoctcp (I believe that
      these are the only two valid choises on NT).
      The hostname needs to match the node name of the NT machine and
      should also match the entry in the etc/hosts file on both machines.
      The servicename must match the entry in the etc/services file on
      both machines (see notes above).

You will also need to make sure that the sqlexecd process is running on the
UNIX side.  Furthermore, if the entry in the /etc/services file on the UNIX
node lists a service name other than sqlexec, you will need to make sure
that the sqlexecd process is started using the correct service name.
If you start the sqlexecd process on the UNIX node without passing it a
service name it will use the default service name of 'sqlexec'.  If you
want the sqlexecd process to use the 'turbo' service you must pass it that
service name when you start the process.

For example:

# $INFORMIXDIR/lib/sqlexecd turbo
or
# $INFORMIXDIR/lib/sqlexecd turbo -l logfile_name

There is no sqlexecd process to worry about on the NT node (because those
nice folks at Informix have added the network connectivity to the OnLine
Engine product).  You will need to make sure that you have the correct
data in your registry thou.

--
Regards,

: Hi informix'ers
: can I connect my online 5.0 UNIX database from my online 7.1 NT machine..?
: I edit the sqlhosts registry on NT adding new key for my unix database but
: when I connect from dbaccess giving me error message 908 attempt to connect
: to databse server failed...?

: any hints...

: thanks...

On the NT, you have to set the sqlhosts information in the registry by
using either setnet.exe or by using regedt32 to edit the registry.  The
registry needs to have HOST, SERVICE, and PROTOCOL entries. I don't
fully trust setnet....sometimes I have to go to the registry to edit
it manually.

You also need to edit the services file \winnt35\system32\drivers\etc\services
to make sure that the service is there.  Try using ilogin.exe to test the
connection.  If you manually enter all the data in the connection info in
ilogin, I believe it will take that info first without going to the registry.

Takes a little tweaking....

Joe
--
---------------------------------------------------------------------------

---------------------------------------------------------------------------