db2haicu branches to maintenance mode.Also menu navigation can be heavy or lead to dead ends(RIMS)

From PMR 90884,077,649: Issue #2: db2haicu branches to maintenance mode when a partial config is in place. A complete db2 / TSA solution includes: 1. DBM CFG parm CLUSTER_MGR being set to TSA 2. the presence of file ~/sqllib/cfg/db2ha.sys Page 4 of 8 3. TSA objects On occasion during testing some or all of these elements may have been left behind from earlier configuration attempts. (e.g. the TSA domain was removed). db2haicu sees the presence of either the file or Cluster_Mgr parm and branches into Maintenance mode. From here we have no way of using db2haicu to create the resource group for this instance, we receive no message explaining why we branched into Maintenance mode. We are caught in a scenario where we have defined all the pieces and it now instructs us to complete the standby? but there is nothing we can do. With experience and a better understanding, we now either manually clean up or run db2haicu ?delete. We feel either additional validation prior to branching to maintenance mode, or add an item to the menu : add/remove db2 instance. Issue #3: db2haicu menu navigation can be heavy or lead to dead ends. On a cluster equipped with 4 network cards per host the definition of Public Networks is clunky. If each host is equipped with en0, en1, en2, en3 and our solution only uses en0 and en2 we will still have to cycle through and configure en1 and en3 only to answer NO to Are you sure you want to add them. Example illustrated bellow: ? Enter the name of the network for the network interface card: en1 on cluster node: r59t1c4 1. db2_public_network_0 2. Create a new public network for this network interface card. Page 6 of 8 3. Create a new private network for this network interface card. Enter selection: 2 Are you sure you want to add the network interface card en1 on cluster node r59t1c4 to the network db2_public_network_1? [1] 1. Yes 2. No 2 Enter the name of the network for the network interface card: en1 on cluster node: r59t2c4 1. db2_public_network_0 2. Create a new public network for this network interface card. 3. Create a new private network for this network interface card. Enter selection: 2 Are you sure you want to add the network interface card en1 on cluster node r59t2c4 to the network db2_public_network_1? [1] 1. Yes 2. No 2 ? We feel it should be: ?Do you want to add en1 on r59t1c4 and en1 on r59t2c4 to db2_public_network_1?? where db2_public_network_1 is the next available number. It would be even better if we could provide the name. Early on we would define 4 networks, then come to define the HADR VIP and could not remember if network_1 was the en3, or network_2 was the en1??? We must then issue external lsequ -s 'Name like '%'' commands to figure out the mapping of cards/segments to db2_public_network names.