We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive a notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
If you encounter any issues accessing the Ideas portals, please send email describing the issue to email@example.com for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
Expose or change CritRsctProtMethod in RSCT/TSA for Db2 HADR deployments
When deploying Db2 HADR on PureApplication, IBM TSA automatically gets installed and setup to handle the automatic failover of Db2. TSA is built on RSCT, which is configured with a recommended/default CritRsctProtMethod of 3. This default ensures maximum safety, as it allows for the release/unlocking of any shared resources. Refer to the following technote for more details:
However when Db2 HADR is deployed on PureApplication, there are no shared resources that require release/unlocking. Therefore a value of 5 should be considered as the new default. Or even better, the Db2 pattern type should expose the value of CritRsctProtMethod so it can be changed accordingly by the user deploying Db2 HADR.
When TSA performs a failover of Db2 HADR, the default CritRsctProtMethod of 3 triggers a reboot of the VM that no longer acts as Db2 primary. This reboot does not provide any value, asthere is no need to unlock/release any shared resources with Db2 HADR deployed on PureApplication. However it does lead to more disruption at a time when that is best avoided.
Do not place IBM confidential, company confidential, or personal information into any field.