Command Manager does not automatically lock a project or configuration when it executes statements. To avoid metadata corruption, you can use the following Metadata Lock Management statements in any Command Manager scripts that make changes to a project or server configuration.
 

Metadata lock management

1) Lock Project statement :  Locks a project in the metadata.
LOCK PROJECT "project_name" [FORCE] [PERMANENTLY];
where:     PROJECT "project_name" is the name of the project to be locked, of type string.  FORCE forces the project to lock.
2) Unlock Project statement. :  Unlocks a project in the metadata. UNLOCK PROJECT project_name [FORCE];
where:   PROJECT "project_name" is the name of the project to be unlocked, of type string.
3) Lock Configuration statement : 
Locks the project source configuration in the metadata.
LOCK CONFIGURATION [FORCE] [PERMANENTLY];
where: 

• FORCE forces the configuration to lock.
  
• PERMANENTLY locks the configuration permanently. Only the user who creates the lock can remove it.
  

4) Unlock Configuration statement :  
Unlocks the project source configuration in the metadata.
UNLOCK CONFIGURATION [FORCE];
where: FORCE forces the configuration to unlock.
5) List Lock Properties statement:
Lists all the lock properties for a given project or the project source configuration.
LIST [ALL] PROPERTIES FOR LOCK IN (CONFIGURATION | PROJECT "project_name");
where PROJECT "project_name" is the name of the project for which lock properties are to be listed, of type string. 
KB439903