> # Committing Changes

> A commit operation saves the pending database for all application peers and releases the lock for all switches.

> In general, the commit function does not start a session; only a lock function starts a session. However, an empty commit is allowed if configuration changes are not previously made. In this case, a commit operation results in a session that acquires locks and distributes the current database.

> When you commit configuration changes to a feature using the CFS infrastructure, you receive a notification about one of the following responses:

> - One or more external switches report a successful status—The application applies the changes locally and releases the fabric lock.
> - None of the external switches report a successful state—The application considers this state a failure and does not apply the changes to any switch in the fabric. The fabric lock is not released.

> Copyright 2010-2013, Cisco Systems, Inc. All rights reserved.