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)
Currently when a rerun frequency is defined on a job in a job stream that frequency is interpreted differently depending on whether there is a job level earliest start time on the job. Without the earliest start time the rerun frequency is interpr...
Protect or change behavior of RERUN on a waiting application
Rerun on a waiting application is very dangerous : all external predecessors are set to COMPLETE.2 proposals :Not allow REUN on a WAITING application, just allow it on a COMPLETE application.Or change behavior of RERUN on a waiting application to ...
For Dynamic Workload Console (DWC), would like to have an ALL PREDS option. Like in the ispf IWS panels, under a job/operation, option 9 is ALL PREDS option. The only option under DWC is impact view but it can be hard to read.
Handling of jobstream submissions during switchplan
During the execution of the switchplan sometimes the submit of jobstreams fails. The reason is obviuous: the Symphony file is being created at this moment and the submission cannot be handled therefore. Currently users must prevent this from happe...
Provide a parameter to desensitize the triggering of EQQP23I Potential Risk Alert Current functionality: Potential risk alerts trigger when a job on the critical network is late, or on abend even if the critical jobs deadline time is many hours in...
For example the following example job definition (our production includes several job definitions with carets):DK01SV8880_1#JOB001 DOCOMMAND "ECHO \^\^" STREAMLOGON "SCDOM\TTBUU" RECOVERY CONTINUEdoes not execute ECHO ^^, but ECHO \^\^ causing the...
Do not place IBM confidential, company confidential, or personal information into any field.