Informix - Problem description
Problem IT20079 | Status: Closed |
BETTER HANDLING OF INFORMIXSQLHOSTS ENVIRONMENT VARIABLE ON WINDOWS CLIENT APIS | |
product: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problem description: | |
Since Informix server version 12.10, client version 4.10, 'server' and 'client' components on Windows platforms would look up connection information different ways: - server components (server itself, db*.exe and on*.exe utilities) would use a 'sqlhosts' file, like on UNIX/Linux platforms, typically pointed to by INFORMIXSQLHOSTS environment variable if not the default %INFORMIXDIR%/etc/sqlhosts file - client components (anything contained in Client-SDK or I-Connect, except for dbaccess) would continue looking up the registry, relying on INFORMIXSQLHOSTS variable pointing to \servername holding this registry (typically the local host). As, for instance, the Informix command shell environment has the INFORMIXSQLHOSTS variable set up, for 'server' utilities, any 'client' component started from such environment (or another one having INFORMIXSQLHOSTS environment variable set in a similar way) would be confused and not work properly. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Windows * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to CSDK version 4.10.xC9 when available. * **************************************************************** | |
Local Fix: | |
If possible, have the default %INFORMIXDIR%/etc/sqlhosts file instead of a per-server or otherwise named sqlhosts file, so no INFORMIXSQLHOSTS variable would be required and couldn't confuse anything. | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.04.2017 10.07.2017 10.07.2017 |
Problem solved at the following versions (IBM BugInfos) | |
4.10.xC9 | |
Problem solved according to the fixlist(s) of the following version(s) |