Considerations for OS/390 and zSeries SYSPLEX exploitation

 

DB2 Connect™ provides load balancing and fault-tolerance when routing connections to multiple Sysplexes. When connected to a DB2® for OS/390® and z/OS® database server running in a data sharing environment, DB2 Connect will spread the workload amongst the different DB2 subsystems comprising the data sharing group, based on the system load information provided by the Workload Manager (WLM).

DB2 Connect receives a prioritized list of Sysplex members from the WLM. Each Sysplex returns weighted priority information for each connection address. This list is then used by DB2 Connect to handle the incoming CONNECT requests by distributing them among the Sysplex members with the highest assigned priorities. For load balancing, the list of Sysplex weighted priority information is obtained during each connection. If the DB2 Connect connection concentrator is enabled, this list is also used when determining where to send each transaction.

Note: OS/390 and z/OS Distributed Data Facility (DDF) configuration does not need to be changed to take advantage of the DB2 Connect Sysplex exploitation.

DB2 Connect also provides fault-tolerance by attempting to connect to an alternate sysplex machine in the event of a connection failure. An error will only be returned to the application if all known connections have failed.

DB2 Connect Sysplex is designed with agent pooling in mind. With Sysplex enabled, DB2 Connect routes connections to another DDF member in the event that the connection to a participating member is lost. The reroute is accomplished according to a Sysplex server list.

With the addition of the concentrator, DB2 Connect now has the ability to balance the workload at transaction boundaries. The DB2 Connect concentrator must be enabled for this to work.

Parent topic: DB2 Connect Sysplex support

Parent topic: DB2 Connect