Setting the controlling database for a process rule

About this task

This subcommand sets DCM to either hand over to a specified database, accept updates only from a specified database, or take local control.

ccm pr|process_rule|ut|update_temp|update_template|rt|recon_temp|
      reconfigure_template -cdb|-controlling_database -local 
      process_rule_spec...
ccm pr|process_rule|ut|update_temp|update_template|rt|recon_temp|
      reconfigure_template -cdb|-controlling_database 
      -handover database_spec process_rule_spec...
ccm pr|process_rule|ut|update_temp|update_template|rt|recon_temp|
      reconfigure_template -cdb|-controlling_database -accept database_spec 
      process_rule_spec...
-accept database_spec
Specifies to accept DCM updates from a specified database. You can set the database_spec to a single database definition. See Database specification for details about using database_spec.
-handover database_spec
Specifies that control of the object is handed over from the current database to the specified database. The default value when creating a DCM database definition is a blank string. This means that when you hand over control to a spoke via a hub database, you must specify the hub database_spec for the database_spec value. The specified database_spec must be either a known DCM database definition for which a generate is permitted, or a blank string. A blank string means that control can’t be handed over to that database.
LINK: A detailed description of this option is in "Controlling database and handover of control" section.
-local
Specifies to take local control of the specified process rules.

Example

About this task

  • Set the controlling database to use the 2.1-patch1:Insulated Development process rule.

    ccm pr -controlling_database -accept A "2.1-patch1:Insulated Development"


Feedback