How to use Quick Migration for a remote target subsystem
Article ID: 72229
Updated On:
Products
RC Compare for DB2 for z/OS
Issue/Introduction
How can you run a Quick Migration using RC/Migrator when the target subsystem is remote?
Environment
Release:
Component: RCM
Component: RCM
Resolution
RC/Migrator provides multiple CPU Support. This means that different phases of a strategy can be run on different machines. With regards to performing a batch run of a Quick Migration to a remote subsystem, I would recommend the following:
In the following example, the local subsystem is DB2L and the remote subsystem is DB2R.
1. Specify the remote subsystem ID as the TARGET SSID on the 'RC/M Quick Migration Analysis' panel:
DB2 SSID SPECIFICATIONS TARGET SSID ===> DB2R - this should be a valid DB2 subsystem ID
Alternatively specify the remote target subsystem ID in the PARMFILE of the Quick Migration Analysis JCL cards:
TRGSSID DB2R
Analyze the Quick Migration strategy to generate the Analysis Report.
2. When you then execute the generated DDLFILE (RC/Migrator Analysis Report) you need to make use of the .RESTART SYSTEM() command to ensure which phase of the strategy is executed in which environment.
You can either do this through the 'Batch Processor Interface' panel by specifying the following Processing Option:
RESTART ===> UNLOADS
Or you can add the .RESTART SYSTEM card to the Batch execution JCL cards:
.OPTION NOERRORS NOSQLERRORS RETRY(20) NOBINDERRORS
.RESTART SYSTEM(UNLOADS)
.CONNECT DB2L
This will process the Unload phase on the local subsystem and then halts the execution at the next .SYSTEM card, SQLDDL. This ensures that only the Unload is executed locally.
3. Next you execute the remainder of the strategy on the remote subsystem. Again You can either do this through the 'Batch Processor Interface' panel by specifying the following Processing Option:
RESTART ===> SQLDDL
Or you can add the .RESTART SYSTEM card to the Batch execution JCL cards:
.OPTION NOERRORS NOSQLERRORS RETRY(20) NOBINDERRORS
.RESTART SYSTEM(SQLDDL)
.CONNECT DB2R
This will process the Create DDL and Load phase on the remote subsystem.
In the following example, the local subsystem is DB2L and the remote subsystem is DB2R.
1. Specify the remote subsystem ID as the TARGET SSID on the 'RC/M Quick Migration Analysis' panel:
DB2 SSID SPECIFICATIONS TARGET SSID ===> DB2R - this should be a valid DB2 subsystem ID
Alternatively specify the remote target subsystem ID in the PARMFILE of the Quick Migration Analysis JCL cards:
TRGSSID DB2R
Analyze the Quick Migration strategy to generate the Analysis Report.
2. When you then execute the generated DDLFILE (RC/Migrator Analysis Report) you need to make use of the .RESTART SYSTEM() command to ensure which phase of the strategy is executed in which environment.
You can either do this through the 'Batch Processor Interface' panel by specifying the following Processing Option:
RESTART ===> UNLOADS
Or you can add the .RESTART SYSTEM card to the Batch execution JCL cards:
.OPTION NOERRORS NOSQLERRORS RETRY(20) NOBINDERRORS
.RESTART SYSTEM(UNLOADS)
.CONNECT DB2L
This will process the Unload phase on the local subsystem and then halts the execution at the next .SYSTEM card, SQLDDL. This ensures that only the Unload is executed locally.
3. Next you execute the remainder of the strategy on the remote subsystem. Again You can either do this through the 'Batch Processor Interface' panel by specifying the following Processing Option:
RESTART ===> SQLDDL
Or you can add the .RESTART SYSTEM card to the Batch execution JCL cards:
.OPTION NOERRORS NOSQLERRORS RETRY(20) NOBINDERRORS
.RESTART SYSTEM(SQLDDL)
.CONNECT DB2R
This will process the Create DDL and Load phase on the remote subsystem.
Feedback
Yes
No
Powered by
