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...
Today we can set limits at Workstation level and Job Stream Level. However if we have to have a combined sub limit for multiple job streams, it is hard to achieve. Requirement is for grouping of job streams and setting a limit on them.
To be able to disable ALL task share within pre-defined report
Within pre-defined reports we need the ability to disable ALL share task. If not able to have this ability customers can share many tasks created with all causing many pages of reports to appear even if they don't belong to you. Currently there is...
In TWS 9.1 is announced a new type of predecessors who allow waits for at predecessor, which is not in the plan at Make-plan time. But this new type is only deliveret to TWSz in TWS version 9.1. Please also deliver the mandatory predecessor type f...
Update the twsinst script that comes with fixpack 9.4 so that either the temporary directory is not hardcoded as /tmp
Please update the twsinst script that comes with the fixpack install so that the TWA_TEMP variable is either an option or points to the /tmp instead of /tmp. Filling the temp file system has an impact on other applications on the server and not j...
Kill Zombie Jobs: Add functionality to be able to recover from a corrupted Jobtable on an FTA
When an FTA crashes and gets a corrupted Jobtable and the Jobtable must be removed, jobs that were in EXEC status before the crash remain in EXEC state and take run slots against the server limit, and job stream limit if applicable, even after the...
IWS/About specification change of message notification from MDM
User has troubled job management due to mailman down of Domain Manager. Case No : TS001488604.As a result of the analysis, the cause was found to be an overflow of the Domain Manager message file (. Msg).While stopping some FTAs during periodic ...
Have the ability to put user made flags against jobs on any workastation, in any job stream to be able to monitor these jobs in DWC filtering against this flag.Like the CRITICAL flag, but without prioritisation.
Do not place IBM confidential, company confidential, or personal information into any field.