The Transfer menu pops down when you select the Transfer option under the QABUTIL menu bar:
You can transfer a number of QA Build elements including programs, procedure trees,procedures, procedure bodies, macros and C function definitions. Alternatively, you can transfer all the programs of one QA Build system.
The elements of a QA Build system exist as records in the base dictionary tables of the application database. Consequently, the transfer operation involves an export and an import. The QA Build data is extracted from the source database to a file and the file is then posted to the target database. Finally, the QA Build programs updated on the target database must be compiled.
In practice there are two situations where you must transfer QA Build programs. One, the most difficult, situation is where development has been pursued on both databases. If it has, you must take care to avoid updates to the target database that would overwrite the changes made during development on the target database. See Version Control for how QABUTIL can help you deal with this situartion. The other situation is where the target database has remained untouched since the last transfer from the source database. This is more straightforward, since nothing is lost by transferring too many programs or procedures.
The explanations and instructions in this section assume that the two databases have the same table structure. For information on updating database structure see the Transferring Database Structure in the DP4 Developer's Manual.
In extracting QA Build programs or other components, you create an ASCII file which you can copy to the system to be updated.
Copy onto your system the ASCII file containing the QA Build updates