Example 3: Defining and running ad hoc migration jobs
To meet this request, you define a new table similar to table DB2DBA.GOVERNMENT_SALES_INVOICES that resides on your production subsystem. You want to populate the table with only the information that the auditors need. Therefore, you decide to generate MIGRATE SQL for only specific columns in the new table.
The following table provides a high-level task list for this example:
Task | References |
---|---|
Define a filter that selects specific transactions for government sales, and that selects only insert actions (new invoices). | |
Define a time frame that starts from a specific date and time and ends at a specific date and time. | |
Modify the output options for the default Summary report and SQL file (as needed). | |
Define MIGRATE SQL to include only certain columns for a specified table. | |
Save your selections in a work ID. | |
Generate JCL and save it for batch submittal. | |
Run the ongoing migration job. |
To define the filter and time frame
To modify the output options
To save the selections in a work ID
To generate and save the JCL
Running the ad hoc migration job
To migrate the data that the auditors requested, apply the SQL that you generated on the production subsystem to the table that you created for the auditors.
Comments
Log in or register to comment.