IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity.

Additional Information:
  • The shorter URL for this site is:

  • To view our roadmaps:

  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Refresh all DVM's sharing the same map dataset

In multi-LPAR environments, we will have a single DVM subsystem running across more than one LPAR. When maps are created in DVM, we would want all instances of DVM that are sharing the same map dataset to be refreshed.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 24 2020
  • Under Review
Why is it useful?
  • reduces development overhead

  • reduces administration overhead

  • introduces the concept of a global catalog

  • introduces automation into the product

  • improves usability for administrators and developers

How should it work?

When a change occurs to a given data mapping local to an existing DVM Server, when there are > 1 DVM Servers participating in a configuration, that change should be propogated to all other servers upon a verified committed change.

The mechanism needs to check for locks, access to other DVM Servers to ensure that any locks on the mapped data are not preventing changes from occurring. All DVM servers should be accessed, with changes and success/failure logged across all DVM Servers OR a designated Master Server.

This introduces a form of replication that needs to ensure consistency of data and changes and may facilitate the need for a DVM Backup utility that has the abiliyt to capture a point in time snapshot of a vlalid good source library and restore across all particating servers. If such a utility is created, it should allow online backups and restores at Library and individual mapping level.

Idea Priority Medium
Priority Justification This is high because developers should not have different steps depending on whether DVM is running on a single LPAR or multiple
Customer Name Joe Carroll
  • Attach files

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions