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)
IWA - Dynamic Agent job persistance on "no resource found" error
Add the ability to define jobs that run on a dynamic agent to not error if there is no resource found to run the job. Currently, if all agents defined for the job are down, the job results in an error and must be manually rerun. Add the ability for the job to remain in "Wait" until an agent is up and able to accept the job.
If the job changed to rerun on error, it would also rerun when different, application errors are encountered, which is not desirable. This would add the ability to define the action taken if the job is not able to start due to the "no resource found that meets criteria" error, separate from general application errors. You should be able to define this at the job AND dynamic agent/dynamic pool level so all jobs on a given agent/pool do not have to be changed.
Do not place IBM confidential, company confidential, or personal information into any field.