You can create a transfer set. A transfer set represents a collection of objects to be replicated to other databases. The objects to be replicated can be added to the transfer set. The Entire Database transfer set is a special predefined database that automatically includes all projects, directories, files, tasks, folders and baselines.
Before you begin
The current database must be initialized to use DCM.
You must be working as the DCM manager or an administrator to use the -create option. You must be working in the ccm_admin role to use the -rec, -init, -change, -modify, and -settings options.
About this task
ccm dcm -c|-create -ts|-transfer_set new_transfer_set_name
([-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]
- -crq|-change_request_query|-pq|-problem_query cr_query
- Specifies the change request query to be used with the change request scope for the transfer set. 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. This is the default value.
- -crsc|-change_request_scope|-ps|-problem_scope scope
- Specifies 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 that the change request scope for the new transfer set is 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 new transfer set is cumulative. The release scope and query for transfer sets are evaluated with each generate or generate preview operation. However, if -cumulative_release_scope is specified, 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
- For the new transfer sets, specifies to use the specified 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 the email address of the person(s) 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.
The default is -noemail.
- -ep|-email_policy policy
- Specifies the email policy that is used during generate and transfer operations. 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. This is the default.
- 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 new transfer set. The default is -noexclude_db_info.
- -exclude_imported_objects
- Specifies to exclude objects created in other databases from transfer packages generated from the new transfer set. The default is -noexclude_imported_objects.
- -exclude_nct|-exclude_non_completed_tasks
- Specifies to exclude tasks that have not been completed from transfer packages generated from the new transfer set.
The default is -noexclude_non_completed_tasks.
- -exclude_products
- Specifies to exclude products from transfer packages generated from the new transfer set. The default is -noexclude_products.
- -exclude_types type1,type2,...
- Specifies to exclude objects of the specified types from transfer packages generated from the new transfer set. The value must be a list of zero or more type names separated by commas and optional spaces. The default is an empty list.
- -exclude_typedefs
- Specifies to exclude type definitions from transfer packages generated from the new transfer set. The default is -noexclude_typedefs.
- -ferp
- Specifies to fully expand the update properties of projects that are members of the transfer set. This option causes these scenarios to occur:
- 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.LINK: For details, see "Fully expand reconfigure properties".
The default is -noferp.
- -ib|-include_baselines
- Specifies to include any baselines that are associated with objects that are members of the transfer. The default is determined by the DCM setting of Default Include Baselines. The default is -noinclude_baselines.
- -local_parallel
- Specifies to send parallel notifications through email to local owners of parallel object versions received from transfer packages generated from the new transfer set. This is the default.
- -nocumcrsc|-nocumulative|-nocumulative_change_request_scope
- Specifies that the change request scope for the new transfer set is 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.
This is the default.
- -nocumrsc|-nocumulative_release_scope
- Specifies that the release scope for the new 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. This is the default.
- -noemail
- Specifies that email should not be sent following a generate, receive, or transfer for the transfer set. This is the default.
- -noexclude_db_info
- Specifies to include information about database definitions in transfer packages generated from the new transfer set. This is the default.
- -noexclude_imported_objects
- Specifies to include objects created in other databases in transfer packages generated from the new transfer set. This is the default.
- -noexclude_nct|-exclude_non_completed_tasks
- Specifies to include tasks that have not been completed to transfer packages generated from the new transfer set. This is the default.
- -noexclude_products
- Specifies to include products in transfer packages generated from the new transfer set. This is the default.
- -noexclude_typedefs
- Specifies to include type definitions in transfer packages generated from the new transfer set. This is the default.
- -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 transfer set. The default is determined by the DCM setting of Default Include Baselines. This is the default.
- -nolocal_parallel
- Specifies not to send parallel notifications through email to local owners of parallels for received objects from transfer packages generated from the new transfer set. The default is -local_parallel.
- -nomail
- Specifies that email should not be sent for a generate, receive, or transfer for the transfer set. This is the default.
- -rq|-release_query release_query
- Specifies a release query to use with the release scope for the new transfer set. 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. This is the default.
- -rsc|-release_scope (none | releases | (releases_templates | releases_and_templates | releases and templates))
- Specifies the release scope for the new 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_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. This is the default.
- -ts|-transfer_set transfer_set_name
- Specifies the name of the transfer set you are creating. The name can contain any characters, but it must be unique in this database.
Example
- Exclude object types from a transfer set (while you are creating the transfer set).
ccm dcm -create -ts transfer_set_spec -exclude_types "list_of_types"
- Include products in a transfer set (while you are creating the transfer set).
ccm dcm -create -ts transfer_set_spec -noexclude_products
- Exclude imported objects from a transfer set (while you are creating the transfer set).
ccm dcm -create -ts transfer_set_spec -exclude_imported_objects
- Exclude database information from a transfer set (while you are creating the transfer set).
ccm dcm -create -ts transfer_set_spec -exclude_db_info