Default: <blank>

Specify the source OpenEdge database name to be migrated.

If this environment variable is not set and if the user has already set a current working database, the command line migration uses this as the value for the original OpenEdge database.

Dependencies: If PRODBNAME is not set, and no working database is connected prior to running the conversion utility then the migration terminates, and an error is thrown in the logs.

Default: Current working database parameters

Specifies startup parameters for the original OpenEdge source database.

If this environment variable is not set and if the user has already set a current working database, the command line migration uses the parameters that were associated with the startup of the original OpenEdge database specified by the PRODBNAME environment variable. You can specify your own startup parameters for the connection to the source OpenEdge database with this environment variable.

Dependencies: The connection parameters associated with the source OpenEdge database, named by PRODBNAME, is specified by and connected with the PROCONPARMS environment variable value, along with the single-user mode (-1) parameter. In single-user mode, only one user can access the database. It is required that the PRODBNAME source database be started in a single-user mode for successful batch migration so that a snapshot of the database is used during the conversion.

If you provide your own PROCONPARMS value, it must include settings to connect PRODBNAME in single-user mode or in read-only mode (-RO). Otherwise, the database connection fails with an error. For more information, see Startup Command and Parameter Reference.

Default: <blank>

Specify the new schema-holder name, in which the resultant logical database will reside.

Dependencies: If SHDBNAME is not set, the migration terminates with an error.

Default: <blank>

Specify the ODBC Data Source name associated with the resultant schema image from the migration.

Dependencies: If MSSDBNAME is not set, the migration terminates with an error. The ODBC DSN must be properly specified and located in the ODBC Data Source Administration of your system.

If the Load SQL environment variable is set to YES, it must be properly configured to connect to the foreign data source.

Default: <blank>

Specify the Logical Database name configured to connect the foreign data source.

Dependencies: If MSSPDBNAME is not set, the migration terminates with an error. The value for MSSPDBNAME can be the same as PRODBNAME but must be different from SHDBNAME.

Default: <blank>

Specify the user name for the target data source.

Dependencies: If MSSUSERNAME is not set, the migration terminates with an error.

Default: <blank>

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

Dependencies: If a password is required for authentication and MSSPASSWORD variable is not set, the migration terminates with an error. The error is logged in protomss.log.

Default: <blank>

Specifies the startup parameters for the DataServer and the target foreign data source.

For more information on connection parameters, see Connecting the DataServer for connection parameters.

Dependencies: Connect parameters are not mandatory. If supplied, they must be formatted as a comma-separated list of names or name-value pairs, without white-spaces, that comprise the -Dsrv parameter value passed to the DataServer connection. Some of the parameters are parsed into the DataServer run-time, while others in the list are forwarded onto the target foreign data source.

Default: The unconditioned default is 8000. It ranges from 4000 to 8000.

Specify the maximum number of characters for a VARCHAR type. When a single-byte character set is utilized, as determined by the selected MSSCODEPAGE value, this must be a positive value less than or equal to 8000. The default threshold value of 8000 is the maximum number of characters that can be stored in a VARCHAR data type in MS SQL Server. When Unicode character data is utilized by virtue of a Unicode CODEPAGE environment variable selection, the default threshold value is limited to 4000. This value can also be overridden. During OpenEdge to MS SQL Server migration, whenever the column length of character data exceeds the value specified for VARLENGTH, the column is instead migrated as a Large Object (LOB) data type that can store data that far exceeds the data that can be stored in a VARCHAR data type.

Dependencies: When MSSCODEPAGE is set to utf-8, the value set for VARLENGTH must be a positive value less than or equal to 4000 as it is the maximum number of characters that can be stored in a NVARCHAR data type in MS SQL Server due to UCS-2 character expansion. And, character lengths exceeding the threshold value set for VARLENGTH are converted to Unicode Large Object types.

When an OpenEdge database stores UTF-8 data, each OpenEdge character can be as large as 4 bytes, potentially reducing the Maximum Varchar Length to 2000 characters on the server. But generally, MS SQL Server only supports the UCS-2 character set that allows 4000 UTF-8 characters in the UCS-2 range to be migrated into a Varchar column on the server.

Default: iso8859-1 when UNICODETYPES is disabled (that is, set to NO). Else, the default is utf-8.

Specifies the corresponding OpenEdge name for the code page with which the MSS Database is compatible. Use UTF-8 if Unicode support is desired.

If you use a code page that OpenEdge does not support, you must supply a conversion table that translates between the OpenEdge client code page and the code page that your data source uses. For a complete discussion of code pages, see OpenEdge Development: Internationalizing Applications.

It is not mandatory to pass this value during batch migration. You can use Change DataServer Schema Code Page utility to add the code page information to the schema holder later but before you start using the DataServer to read and write data. For more information on changing code page, see Changing a code page in a schema holder.

Dependencies: The specified codepage must exist in the convmap.cp file of your Progress environment in order to be used during the migration.

Default: Basic

Specifies the collation name with which the OpenEdge client must collate and weigh code page values.

Dependencies: The specified collation must exist in the convmap.cp file of your Progress environment in order to be used during the migration unless you are using a Unicode code page. In case you are using a Unicode code page, then the code page name can correspond to one of the International Components for Unicode (ICU) collations that provide linguistic sorting of Unicode data based on the Unicode Collation Algorithm.

Default: NO

Specifies if the code page you are matching on the foreign data source is or isn't case insensitive. Provide YES if your code page is case insensitive, else retain the default value NO.

Dependencies: By default, the code pages in MS SQL Server are case-insensitive. This matches the default sensitivity in OpenEdge. So, if you are using a case-insensitive code page in MS SQL Server, Progress recommends setting this value to YES.

Default: NO

Allows you to specify whether you want the utility to execute the SQL script that is generated in order to create the schema in the target empty MS SQL Server database on the server that was configured through your ODBC Data Source Name. Specify YES to enable this behavior.

Default: NO

Allows you to specify whether to populate the foreign data source with your OpenEdge data. 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.

Dependencies: Load SQL must be selected in order to move data.

Default: NO

Set to YES to migrate constraint definitions from the OpenEdge database definitions to real constraint objects in the foreign data source and constraint definitions in the schema image.

Default: NO

Determines if the OpenEdge primary should attempt to map itself to the SQL Server primary constraint and/or clustered index and/or the DataServer ROWID.

Dependencies: If MIGRATECONSTR is set to YES, this option is superseded in the conversion process by existing constraints in determining the DataServer ROWID.

• OE Schema
• Foreign schema

Default: NO

Looks at existing indexes over the table and tries to identify the "Best" ROWID candidate based on index uniqueness, data types, number of components, and mandatory component characteristics.

Default: Yes

Specifies whether DATE and DATETIME data types in OpenEdge must map to legacy DATETIME timestamp data types in MSS Server.

If set to Yes, it provides backward-compatibility to earlier version of OpenEdge and MSS Server. However, if your database target is MSS 2008 or above and MAPSMSSDATETIME is set to No, more accurate mapping takes place between OpenEdge data and time data types and the new data and time data types in MSS Server.

Default: NO

Determines if shadow columns must be added to the record layout to represent data in upper case form for OpenEdge fields marked case-insensitive.

Dependencies: If MSSCASESEN is set to YES, the SHADOWCOL value is ignored.

Default: NO

Determines if migration must use generator or the old sequence generator when migrating sequences to foreign data source. When MSSREVSEQGEN is set to NO, the legacy sequence generator is migrated instead of the revised version

Default: NO

• "0"= server (the cache size is determined by the server based on server criteria)
• "?"= No Cache("NO CACHE" option is appended to the native sequence creation on the server)
• Positive integer(1 or >1) - The number of sequences stored in the cache(Can range between 1 to the maximum value of the data type of the native sequence)

Default: NO

Maps OpenEdge character fields to MSS Server unicode data types.

Dependencies: Selecting this option changes the default code page to UTF-8 and directs the schema migration to convert all character and CLOB data types in the OpenEdge database to Unicode data types on the server.

Default: NO

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.

• Width
• ABL Format

Default: NO

Specifies if the migration must use the _WIDTH field to calculate column size instead of using the 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.

Default: Yes

Determines whether character fields set to the default format size of x(8) should be expanded to a 30 character default. This expands the default length on the foreign data source.

Dependencies: The option only affects the batch conversion if SQLWIDTH is set to NO, which utilizes 4GL Format for character size translation to the foreign data source. If SQLWIDTH is set to YES, this option is ignored.

• Index Attributes
• Constraints

Default: NO

Specify YES to create named Unique constraints for index uniqueness, otherwise retain the default of automatically using Index attributes to define index uniqueness for unique indexes migrated from an OpenEdge database.

Default: NO

Specify YES to include OpenEdge initial values in the schema image definitions of the foreign data source in the schema holder database with fields migrated to columns in the foreign data source.

When CRTDEFAULT is off, the initial values are assigned out of the schema image to records created in the foreign data source by the OpenEdge DataServer.

When CRTDEFAULT is YES, the initial values are actually transferred and become part of the server definitions, not just the schema image definitions.

• Field Attributes
• Constraints

Default: NO

Specify YES to create named default constraints for initial values rather than setting the DEFAULT column attribute of the generated server column.

Dependencies: If the OpenEdge initial value is going to be migrated to the foreign data source, CRTDEFAULT must be set to YES.

PRODBNAME=db-name; export PRODBNAME
PROCONPARMS="-1 -i"
SHDBNAME=schema-holder-name; export SHDBNAME
.
.
.
pro -b -p prodict/mss/protomss.p