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)
add feature so that jobs in USERJOBS can trigger events for total duration
There is a significant portion of jobs that get placed into USERJOBS that are hung. We need a way to trigger events for total duration of the job, such as at 24h duration, or 72h duration. Currently there are 2 limitations in TWS that are preventing us from doing this: currently duration events are created with a timer starting when the job starts runnning and timing out before the job completes; there is no event generated to begin the timer for jobs in USERJOBS, so a start event could be created when jobs are placed into USERJOBS but then the second limitation comes in that the timer would need to be set to diffent time-outs for each job depending on when they started and there is no way to parameterize the time-out value in this way.
Do not place IBM confidential, company confidential, or personal information into any field.