MVSFORUMS.com

[HB0]

Hello,

Our application is moving from V7 to V8. Currently the UNIT region has been moved from V7 to V8 CM and we are asked to perform the required testing. Here are few things that the DB2V8 doc said -

> ORDER BY and Range Predicates get effected
> In CM, results are converted from Unicode to EBCDIC
and the effect of collating sequence is same in V7 and CM
> Only when we are in NFM we can see the Unicode results and going back from NFM to V7 is very difficult or rather no going back

We are testing programs that use ORDER BY and don't see anychange in results as both V7 and CM show them in EBCDIC. Now the question is how to see the results in CM in Unicode , so that we don't get a suprise while we get to NFM.

Please share your thoughts.

[CZerfas]

Well, what is converted from EBCDIC to Unicode is the content of the DB2 catalog tables. If you have crucial information for your applications in there, you have to test the effects of the changed collating sequence.

Your application data is untouched by the conversion process from V7 to V8 (if you don't convert the encoding schema of your tablespaces additionally, of course).

regards
Christian

[satyenderd]

HBO,

You follow that same process when moving to Version 8.
1. First you upgrade the DB2 catalog using CATMAINT and perform all initial testing of the new code,just like in the past. That step is called compatibility mode (CM), and new SQL function (plus a few other features) is not yet available. CM is also the only timeyou can fall back to Version 7. Compatibility mode is a conversion mode intended to make the transition as simple as possible. Incompatible changes are introduced at this point, so that you can fall back to Version 7 easily.
However, new function that is compatible with the previous release is not yet introduced; this prevents you from using a feature or function during migration that mightprevent you from falling back to Version 7.

2. After you are comfortable that the catalog migration works and the new version behaves as advertised, the next step is to convert the catalog to Unicode and enable the use of long names. This step is new and a little different compared to previous releases of DB2. It
_________________
Satya