Modifying DCM settings

You can specify which DCM settings are to be changed. You must specify at least one of the options associated with this command.

About this task

ccm dcm -m|-modify -settings
        [-desc|-description description_of_database]
        [-location location]
        [-admin_info admin_info]
        [-default_add_history|-nodefault_add_history]
        [-default_include_baselines|-nodefault_include_baselines]
        [-ignore_maintain_wa|-noignore_maintain_wa]
        [-update_db_info|-noupdate_db_info]
        [-keep_typedefs|-nokeep_typedefs]
        [-event_log_size log_size]
        [-parallel_checking parallel_check_keyword]
        [-update_releases release_action_keyword]
        [-add_receive_control_transition transition]
        [-remove_receive_control_transition transition]
        [-no_of_generate_times generate_times]
        [-no_of_old_generate_times old_generate_times]
        [-old_generate_time_resolution old_generate_resolution]
        [-update_rft|-noupdate_rft]
-add_receive_control_transition transition
Adds a valid state transition to the Receive Control Transitions list. This added state transition will be allowed when receiving an object that is controlled in the current database. The value that you specify for transition must be in this form:

from_state:to_state

where:

from_state must be a valid state.

to_state must be a valid state for which a transition exists from the specified from_state.

-admin_info admin_info
Specifies the contact information for the database administrator. The admin_info value can be any string that doesn't contain newline characters. For example, phone numbers and email addresses are valid entries.
-default_include_baselines
Specifies that baselines that are associated with transfer set members are included in transfers sets.
-desc|-description description
Specifies a description for this database. The description cannot contain newline characters.
-default_add_history
Specifies that objects that are added to a transfer set are added along with their predecessors.
-event_log_size log_size
Specifies the maximum number of entries in the event log. You can set the log_size option to be any whole number except zero. When the event log list reaches the value that you specify for log_size, each new entry replaces the oldest entry.
-ignore_maintain_wa
Specifies that the projects created by import or XML import (such as during a DCM receive operation) will be created without a maintained work area. You can turn on work area maintenance for a project again by using the ccm wa -wa command.
-keep_typedefs
Specifies that type definitions are kept after a receive operation is completed.
-location location
Specifies the geographic location of the database (for example, Costa Mesa, California). The location can be any string not containing newline characters.
-no_of_generate_times generate_times
Specifies the number of generate times that DCM stores. The value that you specify for generate_times can be any whole number except zero that is greater than or equal to the number of old generate times.
-no_of_old_generate_times old_generate_times
Specifies the number of old generate times that DCM stores. The value that you specify for old_generate_times can be any whole number except zero that is less than or equal to the number of generate times.
-nodefault_add_history
Specifies that objects that are added to a transfer set are added without their predecessors. This is the default.
-nodefault_include_baselines
Specifies that baselines that are associated with transfer set members are excluded from transfers sets. This is the default.
-noignore_maintain_wa
Specifies that projects that were created by import or XML import will have a maintained work area. This is the default.
-nokeep_typedefs
Specifies that type definitions are deleted after a receive operation is completed. This is the default.
-noupdate_db_info
Specifies that DCM database information is not updated during a receive operation.
-noupdate_rtf
Specifies that process rules and their associated folder templates are not updated during a receive operation.
-old_generate_time_resolution old_generate_resolution
Specifies the interval between the old generate times (expressed in units of days). The value that you specify for old_generate_resolution can be any whole number, except zero, that is a floating number.
-parallel_checking (none|created|updated)
Specifies the type of parallel checking that is performed during a DCM receive operation. The values that you can specify, none, created, and updated, are case sensitive.
-remove_receive_control_transition transition
Removes the specified transition from the Receive Control Transitions list. The removed state transition will no longer be allowed when receiving an object that is controlled in the current database. The value that you specify for transition must be in this form:

from_state:to_state

where:

from_state must be a valid state that is in the Receive Control Transitions list.

to_state must be a valid state for which a transition exists from the specified from_state.

-update_db_info
Specifies that DCM database information might be updated during a receive operation. This information is updated from data that is in the DCM Information file. This is the default.
-update_rtf
Specifies that process rules and their associated folder templates might be updated during a receive operation. This is the default.
-update_releases (none|active|inactive)
Specifies how release definitions are updated on a DCM receive. The values that you can specify, none, active, and inactive, are case sensitive:
  • none

    Specifies that release definitions are neither created nor updated.

  • active

    If the DCM transfer package includes release definitions, any release definitions that exist in the receiving database are updated, but only new active release definitions are created. If the DCM transfer package includes release table information only (from Telelogic Synergy 6.2 or earlier), release definitions for releases are created as active releases.

  • inactive

    If the DCM transfer package includes release definitions, these are created or updated in the receiving database. If the DCM transfer package includes release table information only (from Telelogic Synergy 6.2 or earlier), release definitions for releases are created as inactive releases.

Example


Feedback