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)
I'm wondering if additional information can be provided when message EQQCP21I is generated. It would be helpful if the list of predecessors on the critical path that caused the message to be generated could be captured some where along with the es...
In order to allow to understand in detail the load induced by PIF jobs on the TWS consumption, we wish to be able to have an option to activate a detailed log of the CPU cost of each PIF. In addition, in order to quantify the quality of TSO users'...
TWS is very sensitive to the point that even a small increase in SAN disk I/O wait, delays job execution
Constant read/write of data by TWS into .msg queues makes TWS very sensitive, even a small increase of 8-10 msecs in disk I/O wait time starts queueing up messages in Intercom.msg and eventually delaying job execution.
Support extended characters in user name of IBM Workload Scheduler product
Government of Alberta User Name standards include a dot "." in the user name. IWS Installer limits the User name can contain alphanumeric, dash (-), and underscore (_) characters. Requesting extension of this limitation to include other extended c...
Couldn't extract "Spool List Recipient" details from r3tool
Unable to extract "Spool List Recipient" details from r3tool. When we define email ID for a SAP job , this detail is missing when we take the back of that job using r3tool.But when we define the email ID for the step information in "Spool Request"...
Need IWS MQ Request/Response to be able to match remote application behavior
The current design of the IWS MQ Plugin for the Request/Response action expects the remote application to reply with the message id from the request on the correlation id of the response. We need the IWS MQ Plugin enhanced to be able to match the ...
IWS CPU usage improvement for ETT data set CLOSE events
Each IWS tracker subsystem on z/OS gets control during data set CLOSE processing in order to check, if this event is related to an ETT-defined data set (ETT = Event Triggered Tracking) in the EQQDSLST-file.If EQQDSLST contains many entries (severa...
Do not place IBM confidential, company confidential, or personal information into any field.