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 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.