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.
Why is it useful?
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.
|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|
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 "firstname.lastname@example.org" 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