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 notifications 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.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - incl Orchestration and Performance Management
Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - incl Workload Scheduler
Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Add an option to solve from the "Stuck Online" state, when you don't WANT to STOP the resource
In a DB2 HADR cluster been managed by TSA (SAMP) policy, somehow the hadr database resource was reporting "Stuck Online" state.
Everyghing was fine from DB2 and HADR perspective, Instace was UP, HADR was running normally, both primary and Standby DB were connected and in PEER state. Applications were connected to the database and running as well. Also, running the monitor command manually, was reporting 1 (online).
So, there was no reason to STOP the resource to get rid of the "Stuck Online" been reported on lssam ouput. We just need a way to tell TSA: "Hey TSA, This resouce is FINE now, start monitoring it again"
Only way to get rid of that, on this state was to hack it. killing the IBM.GblResRMd process on the server it was reporting the "stuck online" state.
We are requesting to add an official option to kind of "reset" the rs, without stopping IT, just instruct TSA that the issue is gone, and restart monitoring it again using regular TSA commands.
Do not place IBM confidential, company confidential, or personal information into any field.