The Import dialog has four tabs. Each tab and menu command available on the dialog serves a unique purpose.
In addition to standard File and Edit options, you can choose the following options from the File and Tools menus on the Import dialog:
If no dialog defaults are established, the Import dialog displays application default settings for the check boxes.
The tab is populated with the defaults you have specified. If you have not established defaults, the Import dialog displays application default settings for the check boxes, and the Input File box is populated with the name of the last Input File designated in the Import dialog.
The Import Utility populates the list of objects by:
At least one available object must be selected to run the Import Utility.
Statistics detail the current and total number of objects of particular types imported, and the current and total numbers of errors encountered (the “total” numbers are the composite counts for all Import Processes performed in the session). This display is updated during processing. The status bar displays information about the object being processed.
Specify an Input File. The Input File for Import is generally an Output File generated by Export (see Export for details about creating this file).
Indicate the action taken when the name of an imported object definition matches that of an object already in the current Optim Directory:
Use the Options tab to provide defaults for amending the names of object definitions imported from MVS.
Enter a DB Alias and Creator ID as the Default Qualifier. The Default Qualifier is assigned automatically to objects imported from MVS. Objects on these platforms do not use qualifiers. If the DB Alias is explicitly mapped on the DB Aliases tab, it overrides any default DB Alias specified on the Options tab.
Select this check box to automatically generate a constraint name for any object definition that has “Requires Constraint Name” as the last part of the qualified name. The first eight characters of the first column name for the child table are used as the constraint name, unless the name does not result in a unique Optim relationship name. Otherwise, one of the following characters is appended to the column name or used to replace the eighth character:
123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ.
Each character is applied in turn until a unique name is generated.
If you want to be prompted for a constraint name, clear the check box. The Supply a Relationship Constraint Name dialog is displayed when a name is required.
Choose elements of a three-part Access Definition name (from an MVS definition) that should be used when the Access Definition is migrated to the two-part (identifier.name) Optim naming system.
If Access Definition names are explicitly mapped on the Objects tab, these names override the naming choice specified here.
Use the DB Aliases tab to map explicit DB Aliases for the imported objects.
This grid column is populated with the name of each DB Alias associated with objects in the Input File.
You can provide a new DB Alias for objects to be imported. During Import Processing, the New DB Alias is substituted for the corresponding Current DB Alias. For example, the importing Optim Directory may include a DB Alias that corresponds to a database referenced in the import file by a different DB Alias name. You can specify the appropriate DB Alias for the importing Optim Directory and import the objects and use them without further change. Right-click to select from the following shortcut commands:
Use the Objects tab to review the objects in the Input File and specify new names for imported objects.
Abbreviations for object types:
Abbreviation | Object |
---|---|
AD | Access Definition |
AFC | Archive File Collection |
ARCH | Archive Request |
CALENDAR | Calendar |
CM | Column Map |
CMPROC | Column Map Procedure |
COMP | Compare Request |
CONV | Convert Request |
CURRENCY | Currency Table |
DBALIAS | DB Alias |
DEL | Delete Request |
ED | Edit Definition |
EXTR | Extract Request |
LOAD | Load Request |
PK | Primary Key |
REL | Relationship |
REPT | Report Request |
REST | Restore Request |
STORPROF | Storage Profile |
TM | Table Map |
UPIN | Update or Update/Insert Request |
The names of the objects available for importing. The number of parts in the name depends on the object type and the platform of origin for the object.
If an object name requires changes before Import (e.g. the name already exists), the Utility selects the check box for that object. If you have specified values on the Options and/or DB Aliases tabs that resolve all discrepancies for the selected objects, you need not make changes on the Objects tab.
Specify a new name for the object. The name must comply with the naming conventions for that object type in Optim. For information on naming conventions, refer to the section that discusses the specific object type. Right-click to select from the following shortcut commands:
If Import encounters errors, processing continues according to the specification for the Continue import if error(s) option. Errors are displayed on the message bar and represented visually by a red “X” beside each object in error. Errors are written to the Import Process Log after Import Processing is finished. You can review and print the Import Process Log for diagnostic information about errors.
If some objects fail to be imported due to errors, check the specifications, and try Export and Import again. For details about the format of the Export/Import File, see Output/Input File Format.
When Import Processing finishes, select Show Process Log from the Tools menu to display the Import Process Log.
Print the log by choosing Print from the File menu. Each execution of Import clears the log before information for the current execution is written. Previous log information is not retained.