This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
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.
Maybe a new option on resetrsrc command. . . .
Idea priority | Medium |
RFE ID | 41285 |
RFE URL | |
RFE Product | Tivoli System Automation for Multiplatforms (SA MP) |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Cloud
Product family - Workload Automation and Control Desk
Product - Tivoli System Automation for Multiplatforms (SA MP)
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - ITSM Automation and Control Desk
Product - Tivoli System Automation for Multiplatforms (SA MP)
Weiterhin Wichtig
(GSE Tagung 2016)
Same would be nice for the other way, when a resource is in "failed offline" state and only needs to be monitored again without to reset it.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - ITSM Automation and Control Desk
Product - Tivoli System Automation for Multiplatforms (SA MP)
For recording keeping, the previous attributes were:
Brand - Tivoli
Product family - Automation
Product - Tivoli System Automation for Multiplatforms (SA MP)