COLLECTION

Used only when the foreign DBMS type is DB2/400. Allows you to specify the SQL "Collection" or native "Library" for qualifying the data object target location. It also becomes the selection qualifier during the migration phase where objects are pulled from the foreign data source. If a value is not specified, a default value will be derived from the Data Source Name (DSN) configuration defined for the driver in the ODBC Administrator. For more information on migration considerations for DB2, see Migration considerations for DB2 .

CRTDEFAULT

Used only when the foreign DBMS type is DB2/400. Default values are pushed to the foreign database during migration, and during a schema pull, default values from the foreign database are stored in the schema holder. Specify YES to enable this behavior.

PRODBNAME

Specifies the source OpenEdge database name.

PROCONPARMS

Specifies parameters for the connection to the source OpenEdge database.

SHDBNAME

Specifies the new schema-holder name.

ODBCDBNAME

Specifies the logical name of the target data source. The logical name of the data source can be the same as its physical name, but it must be different from the name that you enter for the schema holder.

ODBCUSERNAME

Specifies the user name for the target data source.

ODBCPASSWORD

Specifies the password of the user for the target data source.

ODBCCONPARMS

Specifies additional connection parameters for the schema holder.

ODCBCODEPAGE

Specifies the OpenEdge name for the code page that the ODBC data source uses. By default, the code page for a schema holder is ibm850. You can leave this field blank and use the Change Code page utility to add the code page information for the schema holder later.

ODBCCOLLNAME

The Progress name for the collation that your ODBC data source will use.

ODBCTYPE

Selects the foreign data-source type to which the ODBC driver is connecting. OpenEdge provides the following choices: Sybase, DB2, and Other. Select Other if you are accessing a target data source other than those listed here. Note that you will get only the generic ODBC SQL functionality if you access databases other than those listed here.

LOADSQL

Allows you to specify whether you want the utility to create the schema in your empty ODBC data source. Specify YES to enable this behavior.

MOVEDATA

Allows you to specify whether to populate the database. Specify YES to dump and load data or NO to not populate the database. For example, you might specify NO if your database is large, and you want to dump and load data at a more convenient time. The default is NO.

SHADOWCOL

Allows you to specify if whether you will have Progress-compatible case sensitive behavior or not. If your ODBC data source is case sensitive, and you wish to maintain Progress-compatible, case insensitive behavior, specify YES.

COMPATIBLE

Allows you to specify whether to enable the ABL capability. Specify YES to enable this capability or NO if you do not want this capability. In most cases, the default is NO; however, for Sybase data sources, the default is YES.

SQLWIDTH

Default: NO

Specifies if the migration must use the _WIDTH field to calculate column size instead of using thef format field.

Dependencies: Specify YES to use the _WIDTH field in the column's schema image to calculate column size in place of the default format field, else ABL Format is used to size migrated column.

EXPANDX8

Default: YES

Set to YES to double the length of fields on conversion, and NO otherwise.

If set to YES, the single-byte characters receive adequate size as double-byte characters in MSS UCS-2 format. Specify NO if you want the column size of the server calcualated directly from the x(8) format value.

Dependencies: This option is ignored if SQLWIDTH is set to YES.