CTDUFEXP – Transfer data between Control-D Repositories

The CTDUFEXP utility enables the customer to transfer metadata and objects (such as viewing rulers and notes) associated with Control-D reports from one Control-D for z/OS repository to another Control-D for z/OS repository.

This process is useful for customers

• re-defining their Control-D repositories to reflect changes in their business or IT structure
• merging their Control-D repositories to reduce their production cost
• splitting their Control-D repositories to improve system performance

CTDUFEXP is submitted separately for each exported Control-D User file (Permanent, Active, Migrated, or History). For each User file, the CTDUFEXP utility does the following:

• exports metadata from a Control-D for z/OS repository to a sequential file.

  The data is unloaded to the sequential file pointed by DAEXP DD statement. The name of the sequential file is %DBPREFD%.PACKAGE.DBFILE, where %DBPREFD% is the Control-D files prefix defined in the source repository. The PACKAGE and DBFILE values are taken from the input parameters described below. Using the CTDUFRST and CTDUFLD utilities, the customer can import the metadata from the sequential file to another Control-D for z/OS repository.

• creates a list of the unloaded reports, rulers, CDAM and Index datasets, and tape volumes related to the extracted Control-D reports.

  The lists are helpful for transferring the datasets or volumes to another Control-D repository.

• deletes User and Notepad records from the exported Control-D User files.

  Other objects associated with the exported files can be deleted later by the CTDDELRP, CTDCLHST, and CTVCLMIG utilities.