Re: pb/informix interface

Greetings Walter, Your suggestion below was a wonderful idea and we did try this but we couldn't get any connects using tcp/ip addresses only. Currently the powerbuilder group is out of the shope for the next few days so I haven't been able to confirm that they don't do anything weird before the connection attempt. Any other possibilities? Do you know which inets work and which ones don't? From examination of the inet structures this looks like a feature instead of a bug but I suppose that is point of view. George Rachor Beaverton, Oregon george@racsys.rt.rain.com On Fri, 1 Nov 1996, Walter S. Tyszka wrote: } On 10/31/96 George Rachor wrote: } } > I'm no powerbuilder expert but I'm curious to know if anyone else has } > encountered this problem. } > } > We have Powerbuilder running on Client pc's connected to Informix Online 7.12 } > running on SCO Openserver. } > } > As the domain names expand we have run into a limit in connecting from one } > system to another. } > } > We started out with connections like this one below: } > system.domain.com } > } > This is where powerbuilder connects to the Unix system without problem. } > Our problem begins as we introduce subdomains. } > It turns out that there is a structure within the INET (driver for } > pb to Informix) that is limited to 18 bytes. As we expand to } > attempt to connect to : } > system.sub.domain.com } > we are limited to connecting to : } > system.sub.domain. } > } > and we fail to connect. Has anyone managed some sort of workaround to this? I } > supposed sombody a long time ago that 18 characters was plenty for a system name } > but it doesn't cut it now. } > } > Any ideas? } > } > George Rachor } > Beaverton, OR } > } > george@racsys.rt.rain.com } > } > -- } > George Rachor Jr. Beaverton, OR } > } George, } } This bug seems to appear from time to time (and version to version). } The last time that I saw a similar bug was in version 5.03.UC1 for } SCO UNIX 3.2.4.2, and the domain name limit was 15 characters. } } One possible work around might be to use the tcp-ip address rather } than the node_name.domain_name combination. } } For example, rather than using database_name@system.sub.domain.com } you might try database_name@111.222.333.444 (assuming 111.222.333.444 } to be the tcp-ip address of the system.sub.domain.com node). } You may need to disable DNS name translations, or use the tcp-ip } address in place of the host name in the sqlhosts file (or registry), } but this might work for you. } } -- } Regards, } } Walter S. Tyszka (wstyszka@ingr.com) * Standard disclaimers apply * }