CLI operation

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 that have been added to the transfer set, or modified, since the last generate time for that database are then 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 be working as the DCM manager or administrator to use the -generate option. You must be working in the ccm_admin role to use the -rec option.

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 will be generated. You can set the database_spec to a single database definition. See Database specification for details.
-email email_address
Specifies the email address of the person(s) who will receive email notification following a generate 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.

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 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 these:

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 will not exclude an object regardless of when it was last modified or became a member of the transfer set.

-noemail
Specifies that email should not be sent following a generate 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 is the default.
-nowait
Specifies that an automatic receive should not wait until the receiving database has completed receiving other transfer packages.
Note: It is not safe to receive multiple transfer packages in a database concurrently. By default, DCM will receive 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.
-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. You can set the transfer_set_spec to a single transfer set. For details, see Transfer set specification.
-wait
Specifies that an automatic receive should wait until the receiving database has completed receiving other transfer packages. This is the default.

Example


Feedback