Generating a transfer package

You can generate a transfer package for a specified transfer set and destination database. If the indirect members of the transfer set are out-of-date, they are recomputed from the current direct members in the transfer set. The direct and indirect members added to the transfer set, or modified, since the last generate time for that database are included in the transfer package.

Optionally, you can transfer the transfer package to the destination database by using the transfer mode defined for that database. If you transfer the package, you can automatically receive the package into the destination database.

Before you begin

The current database must be initialized to use DCM.

You must have the dcm_mgr or ccm_admin role available to generate a transfer package.

About this task

A DCM manager or an administrator can generate a transfer package.

ccm dcm -gen|-generate -dbid|-database_id database_spec 
        -ts|-transfer_set transfer_set_spec 
        [-lg|-last_generated last_generated_value] 
        ([-email email_address] | [-noemail]) 
        ([-trn|-transfer [-rec|-receive ( [-wait] | [-nowait] )]] | 
        [-notrn|-notransfer])
-dbid|-database_id database_spec
Specifies the destination database for which the transfer package is generated. The database_spec must specify a single database definition. See Database specification for details.
-email email_address
Specifies the email address of the persons receiving email notification following a transfer set generate operation.

To define multiple email recipients for the transfer set, separate the addresses with a space or comma. To define email lists, set up email aliases or distribution lists by using the facilities of your mail server. To learn, consult your mail server and operating system.

If you do not set up an email address, Synergy uses the email address defined on the transfer set specified in the dcm generate command.

-lg|-last_generated last_generated_value
Specifies the last time a generate operation occurred.
Note: This option is for advanced users only.

If not specified, the package is generated to use the time at which a transfer package for the specified transfer set and database was last generated. Use this option to generate a transfer package that includes earlier changes, such as when recovering from missing transfer packages.

The last_generated_value must have one of the following settings:

never
— an integer index where 1 refers to the most recent generated transfer package.

If you select a timestamp that is not the most recent timestamp, the generated transfer package includes all objects that have changed or become members since that date. Also, the more recent timestamps are removed from the list.

Note: The never choice causes all previous time stamps to be removed from the list.

When last_generated_value is set to never, the transfer package is generated as if for the first time. The transfer package does not exclude an object regardless of when it was last modified or became a member of the transfer set.

-noemail
Specifies not to send email following a generate operation for the transfer set. By default, Synergy uses the email setting from the transfer set.
-notrn|-notransfer
Specifies not to transfer the generated package to the destination database. You can use this option if the destination database has a transfer mode other than direct. This option is the default.
-nowait
Specifies for an automatic receive not to wait until the receiving database completes receiving other transfer packages.
Note: It is not safe to receive multiple transfer packages in a database concurrently. By default, DCM receives one package at a time into a database. Use this option only if you are certain that the transfer packages do not contain overlapping objects. For example, if the same task object is present in two packages each generated from a different transfer set, these packages have an overlapping object. In this situation, use -wait, the default
-rec|-receive
Specifies to receive the generate package into the destination database. Use this option when the package is transferred to the destination database and if the host and database path are defined for the database definition.

To use this option, you must save the ccm_root user password on the machine where the receive will occur. Use the ccm set_password command to save the password.

-trn|-transfer
Specifies to transfer the generated package to the destination database. You can use this option if the destination database has a transfer mode other than none or direct. The default is -notransfer.
-ts|-transfer_set transfer_set_spec
Specifies the transfer set to be used for the DCM generate. The transfer_set_spec must specify a single transfer set.
-wait
Specifies for an automatic receive to wait until the receiving database has completed receiving other transfer packages. This option is the default.

Example

Generate the transfer package for the Secure transformer layer transfer set and the BST database, and save it to transfer later.
ccm dcm -gen -ts "Secure transformer layer" -dbid BST

Feedback