The .tar.gz file or .dcm directory contains the objects that are being transferred.
During the generate operation, DCM does the following to create this file or directory:
- If type definitions are not excluded, DCM creates a temporary directory in generate_directory named <FROM_DB_ID><TSET_NUMBER><TO_DB_ID><TIME>\types. DCM exports each user-defined type definition. The format is equivalent to using the ccm typedef /export command.
- If release definitions are not excluded, DCM creates a temporary directory in generate_directory named <FROM_DB_ID><TSET_NUMBER><TO_DB_ID><TIME>\releases. DCM exports the release definitions that are to be included. DCM also constructs a pseudo release table for these release definitions for compatibility with prior releases of Rational® Synergy and creates a <FROM_DB_ID><TSET_NUMBER><TO_DB_ID><TIME>\rel_tbl.txt file.
- If templates are not excluded, DCM creates a temporary directory in generate_directory named <FROM_DB_ID><TSET_NUMBER><TO_DB_ID><TIME>\templates. DCM exports the templates that are to be included.
- Determines which objects to include in the data part of the transfer package.
- Creates a temporary subdirectory in generate_directory. The directory is: <FROM_DB_ID><TSET_NUMBER><TO_DB_ID><TIME>\data
- Exports each object in the transfer list to the temporary data subdirectory.
- If the package is to be compressed, it collects all the files and directories under the <FROM_DB_ID><TSET_NUMBER><TO_DB_ID><TIME> temporary directory into one file using ccm_tar piped through ccm_gzip. Compression removes the temporary subdirectory. If the package is not to be compressed, the package contents directory is renamed to <FROM_DB_ID><TSET_NUMBER><TO_DB_ID><TIME>.dcm