About this task
This subcommand sets the controlling database for one or more releases. You must be in the build_mgr, dcm_mgr, or ccm_admin role to use this subcommand.
ccm release -cdb|-controlling_database -local -component component_name
ccm release -cdb|-controlling_database -handover database_spec
-component component_name
ccm release -cdb|-controlling_database -accept database_spec
-component component_name
ccm release -cdb|-controlling_database -local release_spec...
ccm release -cdb|-controlling_database -handover database_spec
release_spec...
ccm release -cdb|-controlling_database -accept database_spec
release_spec...
- -component component_name
- Specifies to set the controlling database for releases with the specified component name. An empty string applies the change to releases with the null component name.
- database_spec
- Specifies that DCM updates are accepted from a specific database. See Database specification for details.
- -handover database_spec
- Specifies to hand over control of the release to the specified database. You can set the database_spec to a single database definition. See Database specification for details. You can only use this option when the release is locally controlled. See "Setting up a DCM database" in Rational Synergy Distributed.
- -local
- Specifies that control of the database is to be handled by the local database. The object is no longer updated by DCM replication from another database. See "Setting up a DCM database" in Rational Synergy Distributed.