Skip to Main Content
Cloud Management and AIOps

Shape the future of IBM!

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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)

  • Tivoli Application Dependency Discovery Manager - TADDM

If you encounter any issues accessing the Ideas portals, please send email describing the issue to for resolution.

For more information about IBM's Ideas program visit

Status Planned for future release
Created by Guest
Created on Oct 18, 2021

Filetransfer-plugin for IWS 9.5.x does not support datasets on z/OS (MVS) that are migrated by DFHSM

In TWS 9.3 everything is working fine. When a dataset on z/OS is migrated by DFHSM (the storage-administrator of MVS / z/OS) and TWS (agent or MDM) is trying to upload to, or download from, z/OS, the filetransfer-plugin does an alloc of this dataset and it is recalled automatically. Since IWS 9.5 the filetransferplugin only does an inquiry (or check in the catalog) and it sees that the dataset is not on disk, but has status MIGRAT1 of MIGRAT2 and the filetransfer fails (directory not found or dataset is not eligable for FTP). I believe this change in code for the FTP-plugin is not workable for customers that use IWS together with z/OS. DFHSM is standard MVS-software en controles different kinds of files on z/OS. When I file isn't referred for a certain amount of days, DFHSM will migrate this file. In our case, files are migrated when not referred for 7 days. This will prevent this file is backupped (our daily full backup) for 23 times while it's unchanged. For our site this change in IWS-code is really inconvenient, because we use this a lot and it's a loss of functionality. For now we have to build a workaround on our own, that will make an extract from IWS-database for all jobs, filter this extract on dataset-level and issue a HSEND RECALL-command for all this datasets, to prevent some critical jobs within our company will fail because IWS cannot cope with migrated dataset. We hope this loss of functionality (problem) will be fixed in the near future. Hopefully through a fixpack for IWS 9.5
Idea priority Urgent