Simple cloning of data involves making exact duplicates of a specified object type within a Output Manager database instance, or to another Output Manager database instance.
UBU can be used to clone data of the following object types: ARCHIVE_ATTRIBUTE, BANNER_PAGE, PRINTER_ATTRIBUTE, RECIPIENT_ID, REPORT_SELECTION_RULE, SELECTOR_RULE, BUNDLE_DEFINITION, BUNDLE_RECIPIENT, BUNDLE_REPORT, BUNDLE_INSTRUCTION, REPORT_LAYOUT, DISTRIBUTION_LIST, PRSET, TPL_RULE, and CUSTOM_REPORT. There are two processes for basic cloning of data: a process for cloning data without row-group restrictions, and a process for cloning data with row-group restrictions. Objects with row-group restrictions include REPORT_LAYOUT, DISTRIBUTION_LIST, and CUSTOM_REPORT.
- The PREP4CLON parameter automatically changes the negative (-) values in the GroupID fields to positive values by replacing the minus characters (-) with blanks.
- When used for object types with row-group restriction, the PREP4CLON parameter can only be used for basic cloning purposes; if you plan to clone and then MODIFY data of these object types, you cannot use this parameter. Instead, you must make an additional change in the BJTDATA file. When editing the BJTDATA file (step 2), type ADD in the H_ACT_REQ for all rows that you want to clone, and change the minus (-) character to a blank character in the LID field (for REPORT_LAYOUT object types), the LIST_ID field (for DISTRIBUTION_LIST object types), or the RID field (for CUSTOM_REPORT object types).
- If you want to add some object to an existing group, leave the GroupId field negative (-). For example, if you want to add another CUSTOM_REPORT_CONDITION object into some existing CUSTOM_REPORT, the RID field must be negative and have the RID value (a row id) of the target CUSTOM_REPORT.