CLI operation, modify

You can modify the specified transfer sets.

Before you begin

The current database must be initialized to use DCM.

You must be working as the DCM manager or administrator to use the -modify option.

About this task

ccm dcm -m|-modify -ts|-transfer_set ([-email email_address] |
       [-noemail]) [-ep|-email_policy (generate | transfer | always)]
       [-crsc|-change_request_scope|-ps|-problem_scope (none |
       (crs|crs only|change_requests|problems) |
       (crs_and_tasks|crs and tasks|change_requests_and_tasks|
       problems_and_tasks) | (crs_tasks_and_objects|crs, 
       tasks and objects|change_requests_tasks_and_objects|
       problems_tasks_and_objects))]
       [-crq|-change_request_query|-pq|-problem_query cr_query]
       ([-cumcrsc|-cumulative|-cumulative_change_request_scope] |
       [-nocumcrsc|-nocumulative|-nocumulative_change_request_scope])
       [-rsc|-release_scope (none | releases | 
       (releases_templates|releases_and_templates|releases and templates))]
       [-rq|-release_query release_query]
       ([-cumrsc|-cumulative_release_scope] |
       [-nocumrsc|-nocumulative_release_scope]) ([-exclude_products] |
       [-noexclude_products]) ([-exclude_imported_objects] |
       [-noexclude_imported_objects])
       ([-exclude_nct|-exclude_non_completed_tasks] |
       [-noexclude_nct|-noexclude_non_completed_tasks])
       ([-exclude_typedefs] | [-noexclude_typedefs]) ([-exclude_db_info] |
       [-noexclude_db_info]) ([-ib|-include_baselines] |
       [-noib|-noinclude_baselines]) [-exclude_types type1,type2,...]
       ([-ferp] | [-noferp]) ([-local_parallel] | [-nolocal_parallel])
       [-dir|-directory generate_dir] 
       [-new_ts|-new_transfer_set new_transfer_set_name]
       transfer_set_spec...
-crq|-change_request_query|-pq|-problem_query cr_query
Specifies to modify the change request query for the specified transfer sets. You can use the change request query only if you set the change request scope to a value other than none.

The value must either be blank or a valid query expression. A blank value means to query for all change requests.

-crsc|-change_request_scope|-ps|-problem_scope scope
Specifies to modify the change request scope of the specified transfer set. The scope defines how to include change requests and their associated objects in transfer packages generated using the transfer set. Choose from these scopes:
  • none

    Change requests are not included automatically. This is the default.

  • crs|crs only|change_requests|problems

    Change requests found by the change request query are included along with their attachments.

  • crs_and_tasks|crs and tasks|
    change_requests_and_tasks|problems_and_tasks

    Change requests found by the change request query are included along with their attachments and associated tasks.

  • crs_tasks_and_objects|crs, tasks and objects|
    change_requests_tasks_and_objects|problems_tasks_and_objects

    Change requests found by the change request query are included along with their attachments and associated tasks, and the associated objects of each of those tasks.

Note that change requests, tasks, or other objects added explicitly as direct members of the transfer set are not affected by this option.

-cumcrsc|-cumulative|-cumulative_change_request_scope
Specifies to modify the change request scope for the specified transfer sets to cumulative. The change request scope and query for transfer sets is evaluated with each generate or generate preview operation. However, if you specify -cumulative, older members found by previous queries that are not found by current queries will never be removed. That is, the indirect (query-based) membership for change requests will be added to and thus, will be cumulative.
-cumrsc|-cumulative_release_scope
Specifies that the release scope for the specified transfer set is cumulative. The release scope and query for transfer sets are evaluated with each generate or generate preview operation. However, if you specify -cumulative_release_scope, older members found by previous queries that are not found by the current queries will never be removed. That is, the indirect (query-based) membership for releases will only be added to and thus, will be cumulative.
-dir|-directory generate_dir
Specifies to modify the generate directory for the specified transfer sets. Use the generate directory to prepare generated transfer packages for transfer modes other than direct. The generate_dir value represents a server path. Use an absolute path for UNIX servers; use a UNC path for Windows servers. If you use a blank string, Synergy uses the default generate directory, located under the dcm/generate directory under the database path. This is the default.
-email email_address
Specifies to modify the email address for the specified transfer sets. This option delineates the email address of the person who will receive email notification following a generate, receive, or transfer for the transfer set.

You can define multiple email recipients for the transfer set by separating the addresses with a space or comma. If you want to define email lists, you can set up email aliases or distribution lists by using the facilities of your mail server. To learn how to do this, consult your mail server and operating system.

-ep|-email_policy value
Specifies to modify the email policy for the specified transfer sets. This option supports these email policies:
  • Transfer - Specifies that an email message is sent only when you transfer a non-empty package to the destination database. Moreover, no message is sent if there are no objects included after the DCM generate operation.
  • Generate - Specifies that an email message is sent when you generate or transfer a populated transfer package. However, no message is sent if there are no objects included after the DCM generate operation.
  • Always - Specifies that an email message is sent whenever you generate or transfer a populated transfer package. This includes occasions when there are no objects included after you perform the DCM generate operation or when you generate a package that is not automatically delivered to the destination database.
-exclude_db_info
Specifies to exclude information about database definitions from transfer packages generated from the specified transfer set.
-exclude_imported_objects
Specifies to exclude objects created in other databases from transfer packages generated from the specified transfer set.
-exclude_nct|-exclude_non_completed_tasks
Specifies to exclude tasks that have not been completed from transfer packages generated from the specified transfer set.
-exclude_products
Specifies to exclude products from transfer packages generated from the specified transfer set.
-exclude_types type1,type2,...
Specifies to exclude objects of the specified types from transfer packages generated from the specified transfer set. The value must be a list of zero or more type names separated by commas and optional spaces.
-exclude_typedefs
Specifies to exclude type definitions from transfer packages generated from the specified transfer set.
-ferp
Specifies to fully expand the update properties of projects that are members of the specified transfer set. This option causes:
  • All associated objects of tasks that are members are also included, even if they are not members of the project hierarchy.
  • All folders, tasks, and baseline projects in the project's update properties are included, even for projects in a static state.
  • All the subprojects of each baseline project are included, even if they are not directly used by the project hierarchy's update properties.

Note that this can significantly increase the number of indirect members of a transfer set and increase the time it takes to compute indirect members.

-ib|-include_baselines
Specifies to include baselines that are associated with objects that are members of the specified transfer sets. Use this option cautiously. If used incorrectly, you could replicate partial baselines.
-local_parallel
Specifies to send parallel notifications through email to local owners of parallel object versions received from transfer packages generated from the specified transfer set.
-new_ts|-new_transfer_set new_transfer_set_name
Specifies the new name of the transfer set.
-nocumcrsc|-nocumulative|-nocumulative_change_request_scope
Specifies to modify the change request scope for the specified transfer set to be not cumulative. The change request scope and query for transfer sets is evaluated with each generate or generate preview operation. If you use this option, older members found by previous queries that are not found by the current queries will be removed because they're indirect (query-based) members of the transfer set.
-nocumrsc|-nocumulative_release_scope
Specifies that the release scope for the specified transfer set is not cumulative. The release scope and query for transfer sets is evaluated with each generate or generate preview operation. If you use this option, older members found by previous queries that are not found by the current queries will be removed because they're indirect (query-based) members of the transfer set.
-noemail
Specifies that email should not be sent following a generate, receive, or transfer for the specified transfer set.
-noexclude_db_info
Specifies to include information about database definitions in transfer packages generated from the specified transfer set.
-noexclude_imported_objects
Specifies to include objects created in other databases in transfer packages generated from the specified transfer set.
-noexclude_nct|-exclude_non_completed_tasks
Specifies to include tasks that have not been completed to transfer packages generated from the specified transfer set.
-noexclude_products
Specifies to include products in transfer packages generated from the specified transfer set.
-noexclude_typedefs
Specifies to include type definitions in transfer packages generated from the specified transfer set.
-noferp
Specifies not to fully expand the update properties of projects that are members of the transfer set. This option causes:
  • Associated objects of tasks that are in a project's update properties will only be included if they are members of the project hierarchy.
  • Folders, tasks, and baseline projects for projects in static states are not included.
  • Subprojects of the baseline project are included, even if they are directly used by a project's update properties.

This is the default.

-noib|-noinclude_baselines
Specifies not to automatically include baselines that are associated with objects that are members of the specified transfer set.
-nolocal_parallel
Specifies not to send parallel notifications through email to local owners of parallel object versions received from transfer packages generated from the new transfer set.
-rq|-release_query release_query
Specifies to modify the release query to use with the release scope for the specified transfer sets. The release_query must either be a blank string or a valid query expression. A blank string means to query for all releases. You can use the release query only if you set the release scope to a value other than none.
-rsc|-release_scope value
Specifies the release scope for the specified transfer set. Use these scopes:
  • none

    Release definitions are not automatically included.

  • releases

    Release definitions found by the release query are automatically included as indirect query members. However, their corresponding process rules and folder templates are not automatically included.

  • releases_templates|releases_and_templates |releases and templates

    Release definitions found by the release query are automatically included as indirect query members. For each release, its process rules and any user-defined folder templates used by the process rules are also automatically included as indirect query members.

transfer_set_spec...
Specifies the transfer set(s) to be modified. See Transfer set specification for details.

Example


Feedback