The MDBT Configuration Utility enables you to configure options for the following tools:
- SQLTP2 tool
- Enables you to specify how to handle dynamic SQL statements during migration.
- HCOSS
- For SQL Server databases in which dynamic SQL statements are z/OS DB2 statements. This option is required when you are using
HCOSS to migrate the database and your code contains z/OS DB2 DDL statements.
- Agnostic
- For SQL Server, DB2 LUW, Oracle, and PostgreSQL databases in which dynamic SQL statements are specific to the DBMS vendor
specifications. Default.
- SQLUTB tool
- Enables you to specify the issuing of single or multiple commit statements during a LOAD operation. The default is a single
commit issued after all records have been loaded.
You can also use this tool to specify the format of DATE columns for input data and output data, respectively, and to check
the row size of the table against the LRECL of SYSREC using Fuji mainframe behavior.
We recommend that you use the single commit to provide optimal performance. However, if DBMS logging or other such issues
are a concern, you might prefer the multiple commit. For the multiple commit, you also specify a batch size (number of rows).
During the LOAD operation, a commit is issued each time the batch size has been reached.
- SQLTUL tool
[3]
- Enables you to specify that the return code (RC=04) for execution of non-SELECT * statements should match the mainframe DSNTIAUL
return code. The default is to not match the return code, but to return RC=0.
The SQLTUL tool also enables you to specify how to handle dynamic SQL statements during execution by setting either the HCOSS
or Agnostic options:[11]
- HCOSS
- For SQL Server databases in which dynamic SQL statements are z/OS DB2 statements. This option is required when you are using
HCOSS to migrate the database and your code contains z/OS DB2 SQL statements.
- Agnostic
- For SQL Server, DB2 for z/OS, DB2 LUW, Oracle, and PostgreSQL databases in which dynamic SQL statements are specific to the
DBMS vendor specifications. Default.
For complete information about running the MBDT Configuration Utility from the command line, see the
mbdtconfig command topic.