As I mention in my comments above, setting up HADR (High Availability Disaster Recovery) with DB2 is pretty simple, especially if you are going Active/Passive with your nodes. You do not gain automatic failover per se. You would use the
db2 takeover hadr on database <database-name> command for a normal takeover for maintenance and a
db2 takeover hadr on database <database-name> by force in the case of a hard fail of the active node. This article is a good one for how to set that up. (I know it is about Rational Jazz, but it has the steps for how to configure simple HADR without db2haicu).
It sounds like you want automated failover. This means moving up the levels of HADR to start using db2haicu and TSA. Ember Crooks' blog has a part 1, part 2, and a part 3 that shows to set this up. This gets a little trickier because it involves another layer between the OS and the database that needs to be configured and it must know about IP addresses, ports, a virtual IP address, etc. But the benefit is that this extra layer checks to make sure your active nodes stay active, and if not, it fails over to a passive node.
I would also recommend (you and the DBA's) watching this replay from the DB2NightShow. Vikram Khatri from IBM goes through a set of slides that take HADR from its simplest to its most complex, based on what you are trying to do (ie, from active/passive on the same LPAR all the way up to multiple active/active phyiscal nodes with load balancing, etc.)
I'm guessing between Ember's blog and the DB2NightShow link you'll find what you are looking for. However, don't discount the first link. You could set up simple HADR without db2haicu and always "automate" failover with some scripts or something. It might be simpler than db2haicu until you can figure db2haicu out.