This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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 - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
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
Do not place IBM confidential, company confidential, or personal information into any field.