How to Unload and move data to another LPAR and then Load?
search cancel

How to Unload and move data to another LPAR and then Load?


Article ID: 54102


Updated On:


RC Compare for DB2 for z/OS Database Analyzer for DB2 for z/OS Fast Unload for DB2 for z/OS Fast Check for DB2 for z/OS Fast Index for DB2 for z/OS Rapid Reorg for DB2 for z/OS


 How to use Batch Processor to Unload data from one SSID and load it on another SSID that exists on another LPAR?




Component: RBP


The Unload mode is used to control data migration between different LPARS. Typically this would be a pre-generated (data only) Migration strategy from CA-RC/Migrator.

When using Batch Processor and unloading from the SOURCE SSID, set the UNLOAD MODE on the Batch Processor Interface screen to U.

 PROCESSING OPTIONS:                                                          
   UNLOAD MODE    ===> U 

Only the section of input containing Unload statements will be executed on the SOURCE (section .SYSTEM UNLOADS). Execute the job and only the unloads will be processed.

If the source and target LPAR do not share DASD you will have to move the unloaded data with e.g. CA-XCOM Data Transport or CA-NetMaster File Transfer Management .
Or you may consider using tapes especially for large volumes of data.

Note: If you are using RC/Migrator to create the unload/load job (as part of a Migration strategy) you can force the use of tape/cart by setting symbol %LARGE to zero in the Unload and Load model you use.
Please refer to the RC/Migrator Guide 'Utilities reference by Default Model ID' .

On the TARGET SSID you now run the rest of the job with the Unload Mode set to N.

 PROCESSING OPTIONS:                                                          
   UNLOAD MODE    ===> N 

Executing the same migration strategy with the unload mode set to N, the unloads are skipped. The .SYSTEM UNLOADS section will be bypassed and the job continues with the next step(s) and the data is loaded using the unload data sets created by the U option.