Use this page to select options for DB2 IMPORT/LOAD operations.
The initial setting of this option depends on the current DB2 database selected. For databases that are local to the PC running Scriptoria, this option defaults to the LOAD operation (except OS/390). You can also choose to use the IMPORT operation. When connected to a remote DB2 database, only the IMPORT operation is allowable.
For DB2 for OS/390, the choices for this option are “ODBC” and “IMPORT”. You must have DB2 Connect installed to use the “IMPORT” option.
Note that Scriptoria facilitates the IMPORT operation by first dropping foreign-keys and any cascade update relationship related triggers that would prevent data from being transferred. All other triggers, like those that enforce case and validation rules, will execute. After all IMPORT operations have completed, Scriptoria reinstates the previously dropped relationships and triggers.
After a LOAD operation, Scriptoria performs a SET CONSTRAINTS operation for all tables that may have been placed in a check pending state.
Note that if you wish to ensure that case rules are enforced whjen exporting data, you must use the IMPORT option.
This option defaults to REPLACE. You may also choose the INSERT (and INSERT_UPDATE for IMPORT) options for flexible data transfers.
For DB2 for OS/390, the choices for this option are “INSERT” and “REPLACE”. If the “REPLACE” option is selected, Scriptoria first deletes all rows in the target table before it is populated with MS-Access data.
This option is only available when IMPORT is selected. It is used to specify how many rows are inserted before data is committed.
Choose Overwrite to instruct Scriptoria to delete the previous command messages and import/load log files before writing new messages, or Append to add new messages to existing files. The default is Append.
Select this option to log IMPORT/LOAD Log to a file whose location is specified by pressing the Browse button or by typing a file location. The default file location is the Scriptoria Temp sub-directory created at installation time.
To accomplish the IMPORT/LOAD operation, intermediate data files must be created from Access table data. Each Access table to be exported requires it's data to be extracted, reformatted and saved as ASCII text so it can be properly interpreted by the DB2 IMPORT/LOAD facilities. For the greatest flexibility and accuracy, Scriptoria outputs delimited ASCII data in the DB2 supported "DEL" format.
In addition, Access tables that contain OLE Object fields or are assigned CLOB DB2 data types, must have additional temporary files created - one for each OLE Object field in every row of the table. For example, if an Access table contains two OLE Object fields, and the table has 1,000 rows, then 2,000 temporary files must be created before performing the IMPORT/LOAD operation.
Note that these temporary files are automatically deleted when the “Deploy Immediately” option is set, however, when the “Create Script Only” option is selected, these files must be manually purged after the execution of the script completes or when you are finished using them.
Use this page to supply directories (other than the installation defaults) to contain the temporary ASCII and BLOB files created during the export process.
Press the Browse button the select a directory to contain the temporary ASCII file using a standard Directory List box, or type the location of an existing directory. The default file location is the Scriptoria Temp \ ASCII sub-directory created at installation time.
Press the Browse button the select a directory to contain any temporary BLOB files using a standard Directory List box, or type the location of an existing directory. The default file location is the Scriptoria Temp \ Blobs sub-directory created at installation time.