Hi Ed,

the major problem (when you detect it, you'll be deep into your project) are 
some
incompatibilities between SQL/DS and DB2/UDB.

There are SQL-Codes which are different (but meaning the same), there are new 
codes and
old ones that aren't used any more. 
Sometimes you'll have to use the SQLSTATE, not the SQL-Code - and so on.

That means you HAVE to rewrite your own code - there is NO way around that! 

Then there are the discrepancies regarding functions - minimal, but causing 
errors
nevertheless.

Another problem is the translation between EBCDIC and ASCII. Fortunately, as 
long as
you use English, there aren't such mean things as "Umlauts" :-) But there are 
other
problems.

I can search through our docus if you want.

You are right saying "...is not something I could accomplish in a short period 
of time." This could easily be
the understatement of the week ;-)

With kind regards,
Willy

-----Ursprüngliche Nachricht-----
Von: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Im Auftrag von Ed 
Zell
Gesendet: Dienstag, 11. November 2008 18:07
An: [email protected]
Betreff: Re: DB/2 z/VM moving to DB/2 UDB on z/Linux

>>  Has anyone converted their DB/2 for z/VM environment to
>>  DB/2 UDB on z/Linux?   If so, would you be willing to
>>  take my call for 10 minutes?  Thanks.



>  Well, I was a bit too fast with the "send" button.
>
>  We needed 3.5 years because we had around 1500 big bad self-written  
> PL/1-programs which had to be adapted in part. Then there were some  
> equally bad errors in the code - oh well.
>
>  If you'd like to contact me, use my e-mail-address: 
>  mailto:[EMAIL PROTECTED]



Thanks Willy.  I appreciate the offer.  I am coming to the conclusion that a 
move from DB/2 on z/VM to DB/2 on z/Linux is not something I could accomplish 
in a short period of time.
And considering that I won't have the luxury of doing any code re-writes, it 
further complicates the situation.

Ed Zell
Illinois Mutual Life
(309) 636-0107
.


CONFIDENTIALITY: This e-mail (including any attachments) may contain 
confidential, proprietary and privileged information, and unauthorized 
disclosure or use is prohibited.  If you receive this e-mail in error, notify 
the sender and delete this e-mail from your system.

Reply via email to