windows odbc connection to connection manager grou

I have 3 connection manager (Linux) instances whose SLA's are in a group in sqlhosts (group option c=1). When I run dbaccess on any of those machines, the SLA group is listed as an option, and I can connect to the group (it will round-robin my connection to one of the connection managers). Now that it is working on the servers themselves, I'd like to get it to work on my windows PC. I've added the SLA for each server as well as the SLA group into the system via Setnet32. When creating an ODBC connection, I'm using the following information: Server Name: sla_cm_grp Host Name: - Service: - Protocol: group Options: c=1 When I try to test the connection, I get the error: "[Informix][Informix ODBC Driver][Informix]Server sla_cm_grp is not listed as a dbserver name in sqlhosts" If I use any of the connection managers directly I can connect just fine, I just can't get it to connect to the group. Is this option supported by the ODBC framework? I'm using CSDK version 3.50 TC8 on the windows machine. Server is running on Linux, Informix 12.1 -Justin

Justin: See this link for how to configure windows apps to use sqlhsots "groups": http://www-01.ibm.com/support/docview.wss?uid=swg21447622 You have to manually edit the registry to enter the definition of the group since there is no sqlhosts file on the windows side. Also, AFAIK, using groups does not round robin through the group members, it just sequentially tries each group member, in the order they are listed, until one of them responds. Groups are for failover not load balancing (hence the need for Connection Manager). You can make it kind of round-robin/load-balancing by using the environment variables INFORMIX_CONTIME and INFORMIX_CONRETRY to configure how long the client will wait for a response from SOME group member before returning an error and how many retries the client will make within that time. Indirectly that will configure the time the client waits for each member before trying to connect to the next member of the group. Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Thu, Jun 6, 2013 at 5:22 PM, Justin Killen < jkillen@allamericanasphalt.com> wrote: > I have 3 connection manager (Linux) instances whose SLA's are in a group in > sqlhosts (group option c=1). When I run dbaccess on any of those machines, > the > SLA group is listed as an option, and I can connect to the group (it will > round-robin my connection to one of the connection managers). > Now that it is working on the servers themselves, I'd like to get it to > work > on my windows PC. I've added the SLA for each server as well as the SLA > group > into the system via Setnet32. When creating an ODBC connection, I'm using > the > following information: > > Server Name: sla_cm_grp > Host Name: - > Service: - > Protocol: group > Options: c=1 > > When I try to test the connection, I get the error: > "[Informix][Informix ODBC Driver][Informix]Server sla_cm_grp is not listed > as > a dbserver name in sqlhosts" > If I use any of the connection managers directly I can connect just fine, I > just can't get it to connect to the group. Is this option supported by the > ODBC framework? > > I'm using CSDK version 3.50 TC8 on the windows machine. Server is running > on > Linux, Informix 12.1 > > -Justin > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --089e013d1a4a91d12904de834cd0

Art, Thanks - that works great! I think when we deploy the connection setup to the client machines we'll be using registry files anyway, so requiring a few extra keys is no big deal. As for the round-robin, I was under the impression that the option "c=1" setup servers for round-robin distribution, but perhaps I'm mistaken. Round-robin connections to the CM's isn't a requirement for us, so it's not something I'm going to worry about. -Justin -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Art Kagel Sent: Thursday, June 06, 2013 2:50 PM To: ids@iiug.org Subject: Re: windows odbc connection to connection mana.... [30448] Justin: See this link for how to configure windows apps to use sqlhsots "groups": http://www-01.ibm.com/support/docview.wss?uid=swg21447622 You have to manually edit the registry to enter the definition of the group since there is no sqlhosts file on the windows side. Also, AFAIK, using groups does not round robin through the group members, it just sequentially tries each group member, in the order they are listed, until one of them responds. Groups are for failover not load balancing (hence the need for Connection Manager). You can make it kind of round-robin/load-balancing by using the environment variables INFORMIX_CONTIME and INFORMIX_CONRETRY to configure how long the client will wait for a response from SOME group member before returning an error and how many retries the client will make within that time. Indirectly that will configure the time the client waits for each member before trying to connect to the next member of the group. Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Thu, Jun 6, 2013 at 5:22 PM, Justin Killen < jkillen@allamericanasphalt.com> wrote: > I have 3 connection manager (Linux) instances whose SLA's are in a group in > sqlhosts (group option c=1). When I run dbaccess on any of those machines, > the > SLA group is listed as an option, and I can connect to the group (it will > round-robin my connection to one of the connection managers). > Now that it is working on the servers themselves, I'd like to get it to > work > on my windows PC. I've added the SLA for each server as well as the SLA > group > into the system via Setnet32. When creating an ODBC connection, I'm using > the > following information: > > Server Name: sla_cm_grp > Host Name: - > Service: - > Protocol: group > Options: c=1 > > When I try to test the connection, I get the error: > "[Informix][Informix ODBC Driver][Informix]Server sla_cm_grp is not listed > as > a dbserver name in sqlhosts" > If I use any of the connection managers directly I can connect just fine, I > just can't get it to connect to the group. Is this option supported by the > ODBC framework? > > I'm using CSDK version 3.50 TC8 on the windows machine. Server is running > on > Linux, Informix 12.1 > > -Justin > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --089e013d1a4a91d12904de834cd0 ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

You are almost right, c=1 means that instead of every client connecting in the specified order starting with the first listed connection name each client selects one of the connection names at random then cycles through the list if the first one it tries doesn't respond. Not exactly round robin, but it does do some load distribution if not balancing. Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Thu, Jun 6, 2013 at 6:47 PM, Justin Killen < jkillen@allamericanasphalt.com> wrote: > Art, > > Thanks - that works great! I think when we deploy the connection setup to > the > client machines we'll be using registry files anyway, so requiring a few > extra > keys is no big deal. > > As for the round-robin, I was under the impression that the option "c=1" > setup > servers for round-robin distribution, but perhaps I'm mistaken. Round-robin > connections to the CM's isn't a requirement for us, so it's not something > I'm > going to worry about. > > -Justin > > -----Original Message----- > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Art > Kagel > Sent: Thursday, June 06, 2013 2:50 PM > To: ids@iiug.org > Subject: Re: windows odbc connection to connection mana.... [30448] > > Justin: > > See this link for how to configure windows apps to use sqlhsots "groups": > > http://www-01.ibm.com/support/docview.wss?uid=swg21447622 > > You have to manually edit the registry to enter the definition of the group > since there is no sqlhosts file on the windows side. > > Also, AFAIK, using groups does not round robin through the group members, > it just sequentially tries each group member, in the order they are listed, > until one of them responds. Groups are for failover not load balancing > (hence the need for Connection Manager). You can make it kind of > round-robin/load-balancing by using the environment variables > INFORMIX_CONTIME and INFORMIX_CONRETRY to configure how long the client > will wait for a response from SOME group member before returning an error > and how many retries the client will make within that time. Indirectly > that will configure the time the client waits for each member before trying > to connect to the next member of the group. > > Art > > Art S. Kagel > Advanced DataTools (www.advancedatatools.com) > Blog: http://informix-myview.blogspot.com/ > > Disclaimer: Please keep in mind that my own opinions are my own opinions > and do not reflect on my employer, Advanced DataTools, the IIUG, nor any > other organization with which I am associated either explicitly, > implicitly, or by inference. Neither do those opinions reflect those of > other individuals affiliated with any entity with which I am affiliated nor > those of the entities themselves. > > On Thu, Jun 6, 2013 at 5:22 PM, Justin Killen < > jkillen@allamericanasphalt.com> wrote: > > > I have 3 connection manager (Linux) instances whose SLA's are in a group > in > > sqlhosts (group option c=1). When I run dbaccess on any of those > machines, > > the > > SLA group is listed as an option, and I can connect to the group (it will > > round-robin my connection to one of the connection managers). > > Now that it is working on the servers themselves, I'd like to get it to > > work > > on my windows PC. I've added the SLA for each server as well as the SLA > > group > > into the system via Setnet32. When creating an ODBC connection, I'm using > > the > > following information: > > > > Server Name: sla_cm_grp > > Host Name: - > > Service: - > > Protocol: group > > Options: c=1 > > > > When I try to test the connection, I get the error: > > "[Informix][Informix ODBC Driver][Informix]Server sla_cm_grp is not > listed > > as > > a dbserver name in sqlhosts" > > If I use any of the connection managers directly I can connect just > fine, I > > just can't get it to connect to the group. Is this option supported by > the > > ODBC framework? > > > > I'm using CSDK version 3.50 TC8 on the windows machine. Server is running > > on > > Linux, Informix 12.1 > > > > -Justin > > > > > > > > > > > ******************************************************************************* > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > > > --089e013d1a4a91d12904de834cd0 > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --089e01493c1ea0be0604de84f9f1