This topic discusses getting started using Optim™.
When you invoke Move, the Main Menu is displayed. The following figure shows the Main Menu that is displayed when Access, Archive, and Compare are also installed.
Figure: Optim Main Menu
---------------------------- IBM's InfoSphere Optim ---------------------------
OPTION ===>
0 OPTIONS - Site and User Options SQLID ===> FOPDEMO
1 BROWSE TABLE - Browse a DB2 Table SUBSYS ===> TDB2
2 EDIT TABLE - Edit a DB2 Table LOCATION ===>
3 BROWSE USING AD - Browse DB2 Tables Using Access Definition
4 EDIT USING AD - Edit DB2 Tables Using Access Definition
5 ADS - Create or Modify Access Definitions
6 DEFINITIONS - Maintain InfoSphere Optim Definitions (Keys, Maps, ...)
7 MIGRATION - Data Migration - Extract, Insert, Update, ...
8 COMPARE - Compare Two Sets of Data
9 ARCHIVE - Archive and Restore Data
T TUTORIAL - Information About IBM's InfoSphere Optim
C CHANGES - Changes from Prior Release(s)
X EXIT - Terminate Product Use
P LICENSING - Product Licensing Modification
The panel prompts for two site-specific values, an SQLID and SUBSYS. The DB2® subsystem name, SUBSYS, must be supplied the first time you log on to Move. These values are profiled. If remote access is available, a LOCATION prompt is also displayed for the remote location. For example, you can change the displayed values for SQLID, SUBSYS, and LOCATION to extract data from one database and insert it into another.
The Main Menu options are:
This information focuses on Option 7 MIGRATION, which can be performed online or in batch. (If you intend to execute the migration processes in batch, select Option 0 OPTIONS and specify the necessary job card information on the Job Card and Print Options panel, displayed using Option 3 JOBCARD on the Choose Option Type menu.)
Many of the Main Menu options are available for all or most components. See the Common Elements Manual for information about these common options. For information about the Access, Archive, or Compare menu options, refer to the appropriate user manual.
Select Option 7 MIGRATION from the Main Menu to display the following panel.
Figure: Data Migration Menu
------------------------------- Data Migration --------------------------------
OPTION ===>
SQLID ===> FOPDEMO
SUBSYS ===> TDB2
1 EXTRACT - Extract Data from Source Tables LOCATION ===>
2 INSERT - Insert Data into Destination Tables
3 LOAD - Create Load Files and Perform Load
4 CREATE - Create Tables and Related Object Definitions
5 CONVERT - Convert Extract File using Table and Column Maps
6 LIST - List Extract Files in Directory
7 IMPORT - Import Extract File and Populate Directory
R RETRY/RESTART - Retry/Restart an Insert Process
B BROWSE - Browse Content of Extract or Control File
The Data Migration menu lists options used to migrate or copy data and object definitions from a source location to a destination.
The first step in migrating data is to identify the source data to be extracted in the Extract Process. Normally, this source data is in several related tables. You must specify:
If you choose to extract object definitions, Move extracts them first. Move then extracts the selected Start Table rows and related rows from other tables. The extracted data and any object definitions are copied to an “Extract File.”
An Extract File is a sequential file that contains the extracted data and associated information that defines the characteristics of the data. By using an Extract File, you can process the same source data repeatedly, without having to recreate it and without being concerned about changes to the original data. You can use the Extract File as input to the Insert, Load, Create, and Convert Processes, as well as the Browse facility.
The Insert Process inserts data from the Extract File into destination tables. You must define a Table Map to match source tables in the Extract File to destination tables, and you can define one or more Column Maps to match source columns to destination columns. You can also select insert processing to insert new rows, update processing to update existing rows, or both. This selection can apply to all tables, or you can select the type of processing on a table-by-table basis.
The Load Process creates load files from the Extract File. The load files can be used for input to the DB2 Load Utility or another third-party load facility (for example, BMC LOADPLUS) to load large sets of data.
The Create Process creates DB2 and Legacy Tables and related objects for which definitions are contained in the Extract File.
The Convert Process transforms the source data in the Extract File by applying Table Map and Column Map specifications to obtain a new or revised Extract File. Conversion is useful for masking sensitive data or for converting data to a comma separated values (CSV) format to be used with any application that supports CSV files.
Displays a list of Extract files that match selection criteria you specify. The List process allows you to manage extract files registered in the Optim Directory. Refer to the Move User Manual for full details.
Select Import to create entries to register extract files in the current Optim directory. An extract file stored on tape must be registered in the Optim Directory before it can be used in a Convert, Create, Insert, or Report process. For details refer to the Move User Manual.
You can use the Retry or Restart Process if an Insert Process does not complete successfully. The Retry Process allows you to process rows that have been discarded (e.g., due to RI constraints or conflicting data types). Any discarded rows are flagged and can be retried without reprocessing any successfully processed rows. The Restart Process allows you to “restart” a process from the last commit point. The process can be restarted if it terminates unexpectedly due to an internal error, resource restriction, or user request.
You can use the Browse facility to view the contents of an Extract File or a Control File. Browsing an Extract File is useful prior to inserting data into the database. Browsing a Control File is useful in examining discarded rows when a process does not complete successfully.
The scenarios in this manual focus on defining and extracting a set of source data and inserting that data at the destination. Scenario 1 – A Set of Customers highlights the basic procedures used to create a relationally intact test database. Scenario 2 – A Set of Items uses a more complex scenario to introduce other significant features. Scenario 3 – Legacy Tables includes two scenarios that demonstrate the processes for migrating VSAM, sequential, and IMS legacy data.