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)
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...
On a job creation (e.g. executable type), under environment tab we have , Standard input, Standard output, Standard error. This capabilities allows to provide a path to send the joblog. Allthough for job types like "SAP JOB ON DYNAMIC WORKSTATIONS...
9.5 DWC Monitor Workload: To be able to edit column definition for Job when editing task for object type Job Stream
In the 9.5 DWC, under Monitor Workload, when editing a saved task for object type Job Stream, the column definitions are only applicable to job stream. Our customers would like be able to select column definitions for both job streams and jobs in ...
System : IBM Workload Scheduler and Dynamic Workload consoleActor : DWC users We use DWC RestAPI to interact with IWSz for monitoring and batch operations (submit, restart jobs, etc.) for Mainframe as well as Distributed jobs. Also application tea...
There might be possibilities that a scheduler adds some specific time frame to a jobstream(Ex : to run 2 months), If a normal daily job added on the stream by mistake in between this 2 months, Job will run only till the date mentioned in the sched...
If a recurring job scheduled to run 15 mins in 2 hours, There should be a monitor to check if that job runs 8 times in 2 hours. Or like hourly monitor if there is no 4 triggers. This will help globally to all customers to check if critical recurri...
Do not place IBM confidential, company confidential, or personal information into any field.