This is an IBM Automation portal for Cloud Management 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).
Shape the future of IBM!
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:
Search existing ideas
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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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 - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Jnext Enhancement - Bring objects from DB to Plan without Jnext
1) We want to isolate any faulty FTAs from the current plan without the need of scratching it or refreshing it.
If we find some FTAs are having issues after the generation of production plan which causes impact to the master, we should have some commands to immediately ignore those FTAs from current plan to avoid the master being impacted and later reset those FTAs (resetFTA) and bring back in to the current plan.
2) We would like to have the Jnext day as a job or command to be submitted any time to have the database objects reflected in current plan without any impact to the production plan.
Instead of executing Jnext Plan (- no remove) every time to update and bring in DB objects in to current plan, it would be good to have a small enhancement to TWS to have the ability to run a simple command to bring the required DB objects like newly created CPU in to current plan.
Do not place IBM confidential, company confidential, or personal information into any field.