Incorrect schema migration scripts created or aborts if chose to run now. (4225678)

Incorrect schema migration scripts created or aborts if chose to run now.

When trying to migrate databases with Toad for DB2 3.0.0. I can create scripts for the migration but cannot use the Execute Scripts Now option. If the option is used, it aborts out before script creation completes. If I choose to just create scripts and this will complete but with some errors. When reviewing the scripts he notices some incorrect settings/mappings.

In the migration wizard I have sets some Transformation rules, specifying 2 mapping changes during the migration, by adjusting the tablespace names it maps to in the target database and changing the schema names it maps to.

There are instances where SET SCHEMA = USERS@ and SET SCHEMA = DB2ADMIN@ commands sprinkled throughout the code, 2 just before each object, but why? And why is it set to USERS@ and DB2ADMIN@ when the migration should be setting to NEWUSER in the target database?

There are also instances where there are CREATE ALIAS statements that note for DB2ADMIN, instead of NEWUSER. But other create object statments do correctly notE the new target schema. Why does it seem to be inconsistant?

Sample from script:
CREATE ALIAS PUBLIC.TCONTACT_CLIENT_HOLD
FOR DB2ADMIN.TCONTACT_CLIENT_HOLD@

WORKAROUND:
none

STATUS:
Waiting for fix in a future version of Toad for DB2.