Propagating applications to other databases

You can use EXPORT or IMPORT to propagate systems by moving code from a development group to a production group.

You can also use the EXPORT and IMPORT utilities to back up and restore data from an SCLM hierarchy. The steps necessary to back up and restore the project database are listed as follows:

Export the group to be backed up using the EXPORT service.
Save the member text in a PDS for later recovery if necessary.
To restore the data, create an alternate definition that specifies a new temporary development group into which you will import the previously exported data.
Specify the export data sets to be restored on the FLMCNTRL macro.
Copy the saved member text for the backed up group to the new temporary group.
Invoke the IMPORT service and specify the new temporary group. Note that after the IMPORT service has completed, the new group contains the same data that was originally exported.
If you use the new group, use the DELGROUP service to purge the data in the original group, delete the original data sets, and rename the temporary group to the original group name. Another way of accomplishing the same goal is to delete the accounting data out of the original group and then import directly into it.

Note: The IMPORT service erases the exported data after it successfully imports members. Therefore, you may want to make a copy of the export data sets before invoking the IMPORT service if you want to preserve the backup version of the data sets.