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)
Workload Scheduler support for linux parameter "vsyscall=none isses"
see ticket IBM support request TS005150482:IBM Workload Scheduler 9.5 Fixpack 3 - with linux parameter "vsyscall=none isses" every TWS command freezes------------------------------------------environment:TWS Client Version 5 Fickpack 03operatingSy...
Fix extranneous text created in Job Stream Descriptions.
Before 9.4 Jobdescriptions if blank did not show up in composer dump files. Now all the blank descriptions when the JobStream is editted change to "Automatically added by composer"This has the following negative consequences:1. Dump files are mu...
The job description cannot be displayed in the job flow view.
My client wants to see the job description in the job flow view.The job description is not be displayed, but the user wants to see it in the view.Since the description contains useful information which is the user want to see in the job steam flow.
Variable Passing Database Jobs need to print the output value of the processed statement in logs of its subsequent E-Business jobs
In our environment, we are having database jobs defined. For database jobs which is executing SQL statement with SELECT command , we could see the output of that query has been printed in that job log. They are variable passing jobs where the outp...
passing File name with job as paramater to the job script , Job should take name of the file which is getting satisfy using file base dependency
we have event base scheduling to pass file name, where name of the fill will be the file which is getting satisfy with file dependency but here problme is FTA is dependent on Master for event part.Instead of this if we can pass file name in norma...
Oracle E-Business Plugin for Workload Scheduler - Job isn't terminated in Oracle upon termination in IWS.
After submission, when the job is running and is reported in EXEC status in IBM Workload Scheduler, you can stop it if necessary, by using the kill command. The kill command stops the job in IBM Workload Scheduler, but not in the Oracle E-Business...
We have more than one team that manages the production environment and in most of the time each team takes care of a group of applications running under IWS. Using standards for Job, JobStream and Resource names we managed to create filters that c...
Do not place IBM confidential, company confidential, or personal information into any field.