Execution of QCopy

Step 1: Conigma CCM rework

If Conigma CCM is running on the system to be adapted, the report /GAL/CCM_ADMTOOLS_SYSTEM_SYNC must be executed before QCopy is executed. The corresponding button "Rework for system copy" in the report interface is already highlighted in color after a detected system copy.

Step 2: review ALOGs

The first step is to ensure that the ALOG files have not been altered, emptied or otherwise manipulated before or during the system copy.

This is a mandatory prerequisite for QCopy, as non-compliance can lead to a non-functional QA system.

Step 3: start QCopy

Execute transaction “/n/GAL/QCP_QCOPY“.

Step 4: Read system data

The next step is to read the system data. To do this, specify the SID of the production system as the copy source and the SID of the QA system as the copy destination. The date of the previous system copy (before adjustment) is specified as the reference date. This is not the date of the current system copy, but the date of the previous system copy from which adjustment is to be performed. Afterwards the button 'Read system data' is pressed.

If the error message appears that the QA system is already locked by user XYZ, the lock can be unlocked using transaction "/n/GAL/QCP_UNLOCK_SYS″ after consulting user XYZ. If the weekly cache filling report is running, the time required for reading in is usually in the range of minutes.

Step 5: Check

Now QCopy displays its proposal, which can be manually changed. The completeness of all the required files must be checked (press the button “Check“).

Step 6: Execution

Press the button "Execution". By the execution all selected transport requests of the delta queue are imported.

ATTENTION:

QCopy is not completed yet. After the delta import, some rework has to be done.

Step 7: Postprocessing 

If the import is completed (please check via button "Update") the post-processing must still be carried out. The postprocessing is initiated via the button "Jump to Postprocessing".

The postprocessing can also be carried out using transaction '/n/GAL/QCP_QCOPY_PP' (also on the development system). After successful completion of the postprocessing, the original queue (from before the QCopy run) should be available exactly the same way and QCopy is complete.

Step 8: Post import (optional)

This step is optional and by default deactivated. It can be activated over a configuration parameter. In this step, the very new transport requests imported since the system copy in the reference system, can be imported also in the target system. QCopy makes a proposal for the transport requests to be imported in this step. This proposal can be changed and the selected transport requests can be imported by pressing the “Import“ button.