Use the Insert Process to insert data stored in an Archive File or Extract File into a destination database. If tables in the Archive or Extract File do not exist at the destination, the Insert Process uses the object definitions stored in the Archive or Extract File to create them.
Specifications for the Insert Process can be stored as an Insert Request to be reused. Based on your specifications and the primary key values in each table, you can:
Map data from the source to the destination using Table Maps and Column Maps. You must use a Table Map to specify the destination for the tables in the Archive or Extract File. You may also use Column Maps for one or more destination tables. Column Maps enable you to specify the source data for each column and, optionally, to transform the data before it is inserted.
When inserting data from an Archive File migrated from the mainframe version of Optim™ (i.e., the Optim z/OS® Solution), any object names that exceed the maximum length for an Optim client/server object of the same type are truncated. When this happens, the truncated name is suffixed with the code “__TRUNC__”. A 128-character Creator ID, for example, might be truncated in Optim as follows:
You can process an Insert Request immediately by clicking , or you can schedule the request for processing at a later time by clicking . You must save the request before it is scheduled, but it is not necessary to save the request before it is run.
The fully qualified name of an Insert Request consists of: identifier.name.
When you create Insert Requests, it is helpful to use a logical set of naming conventions to identify the use for each and to organize them for easy access.
This chapter explains how to create, maintain, and process an Insert Request, including how to: