When one HCM user MCF-disables a configuration, another HCM user of the same configuration will be notified when he connects to the associated IODF the next time. This user's local configuration is also set into MCF-disabled mode.
Scenario: Opening a configuration that was MCF-disabled by another user
- Steps from both scenarios are completed:
Loading an IODF with associated MCF
Opening an MCF-enabled configuration
---> User A is accessing the configuration/IODF
- User A makes additional changes: both logical and physical-only
- User A MCF-disables the configuration (MCF data set is deleted on the host)
and closes the configuration
- User B opens his local configuration (in connected mode)
result: HCM issues a message to user B:
“No Master Configuration File was found on the host for your configuration.
It is therefore currently marked as disabled for MCF sharing.
You may want to re-enable MCF sharing after your configuration is loaded.”
- Standard resync processing without MCF-enabling takes place;
User B sees IODF changes done by user A, but no physical-only changes.
User B may MCF-enable his configuration again.