Re: Domino connection to DB2 in an high availability shop

Now, if you are looking for a "better solution"

There should be DB2 connections defined for both the local system
(assuming that is the primary connection). and the "remote system" (the
backup).

The application could be coded so if the connection to the local system
fails, the remote is attempted.

OR....

Since you likely have a solution such as

Domino A clustered to Domino b

DB2 A system and DB2 B system.

It would make sense to have the application read the host name on startup
then set the preferred connection based on that.

So Domino B would always attempt to connect DB system B first.


Walter Scanlan
Senior Software Engineer
Office: 507-286-6088
Cell: 507-990-4539




From:
Walter Scanlan/Rochester/IBM@IBMUS
To:
Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>
Cc:
domino400-bounces+wscanlan=us.ibm.com@xxxxxxxxxxxx, Lotus Domino on the
iSeries / AS400 <domino400@xxxxxxxxxxxx>
Date:
02/15/2011 08:20 AM
Subject:
Re: Domino connection to DB2 in an high availability shop
Sent by:
domino400-bounces+wscanlan=us.ibm.com@xxxxxxxxxxxx



If you are using LSXLC, that relies on the SQCLI code to make the
connection
That OS code uses the WRKDBDIRE entries to make a connection
(host name lookups are never used).

For Domino to "see" a change the LSX application would need to open the
connection again
and on open the WRKDBDIRE entire would need to have been
updated.
AND, a DRDA connection must exist for that connection if
not local.

Walter Scanlan
Senior Software Engineer
Office: 507-286-6088
Cell: 507-990-4539




From:
rob@xxxxxxxxx
To:
Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>
Date:
02/15/2011 08:10 AM
Subject:
Re: Domino connection to DB2 in an high availability shop
Sent by:
domino400-bounces+wscanlan=us.ibm.com@xxxxxxxxxxxx



The out of Domino test simply uses STRSQL from the command line.
Within Domino it uses the ODBC connection classes with Lotus Script. Do
you need samples?


Rob Berendt