Working on a Mart › Model Lock › Lock Behavior

Lock Behavior

When you edit a catalog entry, locks are applied automatically to appropriate levels in the catalog to prevent other users from editing the entry. When the edit is complete, the locks are removed or downgraded automatically.

The following scenarios explain the behavior of locks when you edit a catalog entry:

• When you load a model, Shared Lock is applied to the model and Existence Lock is applied to the parent entry up to the mart. After the model is loaded, Shared Lock is replaced with Existence Lock.
• When you initially save a model, Update Lock is applied to the model. After the model is saved, Update Lock is replaced with Existence Lock.
• When you incrementally save a model, Update Lock is applied to all the versions created between the opened version and the newly created version. After the model is saved, Update Lock is replaced with Existence Lock.
• When you delete a model, Exclusive Lock is applied to the model. After the model is deleted, the lock is dropped.
• When you delete a user, the locks that the user had applied are deleted.
• When you rename a library, Update Lock is applied to the library. After the library is renamed, the lock is removed.
• When you load models for version compare, Shared Lock is applied to the root model. After the model is loaded, Shared Lock is removed.
• When you merge or import objects during version compare, Update Lock is applied to the root model. When the merge or import is complete, Update Lock is removed.

  Note: This is indicated under the following sections on Catalog Manager and mart Open dialog box respectively:

  • Locks
  • Lock Information