You can use virtual addresses and the sysplex distributor feature
of TCPIP. It will workload balance the connections based on
feedback from WLM. It does require a fair amount of TCPIP setup but
does work well once done. After the mainframe work is completed,
there are changes required in the DB2 Connect node and DCS database
definitions as well.
From: Donna Domovic [mailto:[login to unmask email]
Sent: Friday, September 15, 2017 11:22 AM
To: [login to unmask email]
Subject: [DB2-L] - DB2 Connect load balancing
We are running DB2 Connect on 1 server and would like to have it
connect to a 2 member data sharing group on z/OS. We'd like to have
the connections round robined or load balanced between the 2 DB2
members on the mainframe (each is on a different CPU).
We know that we can set a primary and secondary node in the DB2
Connect Configuration but this seems to provide fail over if the
primary DB2 subsystem is down not load balancing.
Is there some way to configure DB2 Connect on the server to load
balance requests as they come in so that they are split between the
2 DB2 members on the mainframe?
[login to unmask email]<mailto:[login to unmask email]>
-----End Original Message-----