Copying Product Line Data
There are four ways to copy data from one product line to another. These are listed in the table below. General information about the utilities referred to here can be found in the System Utilities Reference Guide and at the command line.
If you are copying data from one product line to an existing product line that contains application data, you must delete all data for the existing product line before proceeding.
| Basic Methods and Utilities for Copying Product Line Data | |
|---|---|
| Copy data for the entire current product line, data area or data ID |
This option may not be possible if the amount of data in the product line is too large to fit on the disk. Caution: You MUST copy ALL system codes for the entire product
line to retain relational integrity.
Use the following utilities:
|
| Copy data from one data area to another |
Use the following utility:
|
| Copy data for a single system code |
This option is most manageable because it results in smaller dump files. Caution: You MUST copy
ALL system codes for the entire product line to retain relational
integrity.
Use the following utilities:
|
| Copy data for a single file |
Because it is difficult to access relational requirements, this option has a high degree of risk. It is useful for testing out a new form that only uses one table. Caution: You MUST investigate and account for all relational requirements
of the existing product line before proceeding.
Use the following utilities:
|
| Copy jobs |
Allows copying of job-related information from the GEN database of one Lawson Environment to another Lawson Environment. Use the following utilities:
|