Mainframes DB2 on z/OS moved to DB2UDB on Windows-DS Impact

Sushma ChowReddy · Post by **Sushma ChowReddy** » Sun Jul 07, 2013 11:32 pm

Hi All,

The Mainframes DB2 on Z/Os is moved to DB2UDB on Windows, but the Datastage part remains the same.

Is Datastage (DS DB2 stages are) compatiable when the above migration is happend?
Could any one please post if any issues with (data issues/datatype/Dateformat/..........) the same.

Thanks Very Much,
Sushma.

jwiles · Post by **jwiles** » Sun Jul 07, 2013 11:45 pm

Which DB2 stages are your jobs using?

In general, the DB2 Connector stage is compatible, DB2Z stage is not. If the DBAs perform the migration successfully, you shouldn't have any data issues but you should ALWAYS thoroughly test to identify any issues that may be particular to your environments.

Regards,

Sushma ChowReddy · Post by **Sushma ChowReddy** » Mon Jul 08, 2013 12:49 am

Thanks jwiles.

Correction on the OS type: Its migrated to Linux not Windows.

We are using DB2/UDB Connector,DB2/UDB Enterprise,DB2/UDB API,
DB2/UDB Load. So the DS is compitable when the above stages are using Correct. Could you please confirm.

Thanks,
Sushma

jwiles · Post by **jwiles** » Mon Jul 08, 2013 8:47 am

All of those stages should work with DB2 on Linux/Unix and Windows. You should contact your official support provider for verification and for the specific versions of DB2 supported by those stages in the version of Information Server you are working in.

FYI...there is no need to send a private message asking the same question that you have put into the forum. That usually serves to just annoy the people to which you do that.

Regarding the migration question (issues encountered): I've not done that particular migration--moving the database from DB2/z to DB2/LUW--so can't give you any specifics regarding it. As with any database migration, ensure that you have connectivity to the new database servers, databases and schemas. Verify with the DBAs as to any changes they may have made to tables and views that your jobs access. TEST, TEST, TEST! Run tests to ensure that the data you retrieve from the new database is correct, especially with data types that you're concerned about. Followup on any new warnings in your jobs...they may point out differences for you.

Regards,