Example 2: Migration of changes with set ranges
This example uses the scenario described in Example-1-Ongoing-migration-with-adjusted-ranges. However, in this example, instead of setting the range of the time frame from a point of consistency to the current time, you set the time frame from a log mark to another log mark. The log marks use a
Log Master
feature to create points of consistency (quiesce points).
Be sure to create quiesce points if you use this technique. If you create the log marks without quiesce points, you can fail to capture transactions that are in process at the beginning or end of each run.
Following table provides a high-level task list for this example.
Task | References |
|---|---|
Create the decision-support database. | |
Specify the log mark and log scan jobs for the daily migration. | |
Define a log mark for the point of consistency (quiesce point) used in the first mass migration of data. | |
Define a filter that selects specific table space transactions. | |
Define a log mark step to create a quiesce point at the beginning of the repeated job. | |
Define a time frame that starts and ends at two relative versions of a log mark. | |
Modify the output options for the default Summary report and SQL file (as needed). | |
Save your selections in a work ID. | |
Generate JCL and save it for batch submittal. | |
Run the ongoing migration job. |
This section contains the following topics:
Related topic