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)
To connect to Kubernetes, connection information was given in a config file. How will we need to proceed in the multi-cluster working structure?
We have two kubernates clusters in production environment. We want the plugin to have the ability to deploy jobs into multiple clusters. You can think of this process as a load-balancer. Currently, we can only give a single kubernates cluster conf...
Due to administrative rules we are forced to run multiple IWSz Systems in parallel on one SYSPLEX. When migrating IWSz we are using BUILDSSX REBUILD and SSCMNAME TEMPORARY to avoid IPLs. After migration we are restarting IWSz with SSCMNAME PERMANE...
Due to administrative rules we are forced to run multiple IWSz Systems in parallel on one SYSPLEX. So we have to start tracker STCs for each of our multiple IWSz controllers on every system of the SYSPLEX. As the tracker STCs all do the same work ...
In the near future, Peoplesoft will discontinue support for LLE tuxedo connections, and we'll need to migrate to SSL tuxedo connections (see attached)
Presently, in workload scheduler, an extended psagent workstation cannot talk to a peoplesoft t...
Allow ABEND of FAILED jobs in USERJOBS to be marked as SUCC or CANCELED
Starting 9.4 when a JOB gets put into USRJOBS Operations cannot cancel or mark is as SUCC when it fails. Hence in every console it shows up as an issue even after the issue is resolved. This can make the automated or manual management of batch dif...
if we add the job in expired stream while saving it should send / flash the warning message to operator.
It should flash a warning message in TDWC/CLI while saving the job in expired jobstream, There is high possibility to add a job inside an expired stream which will be happening globally on all TWS projects.
Do not place IBM confidential, company confidential, or personal information into any field.