Reserved words are found when you precompile or BIND them. You'll
errors in CM if you precompile or BIND there, but the usual story
customers don't do everything at once, so we still see problems
Whenever you move from one release to another, there are some
manage. It is possible, but rare to find SQL which processed in the
release that will not run on the new one. If you have users who
boundaries, instead of reading the limits, then this is more
Reserved words are handled in context when possible, but new
can cause problems in SQL that worked on the prior release. It is
possible to find problems with words that have been reserved for
releases in a new context. Check for APARs.
The best technique for dealing with reserved words is to get a list
reserved words from the SQL Reference for Cross-Platform
Appendix O. Reserved schema names and reserved words. Compare that
with your catalog of table, view and column names. If there are
collisions, make changes or use delimited identifiers.
There are lots of V8 presentations and planning information on the
Here are the primary DB2 V8 migration resources, but get to them
Support web page http://www.ibm.com/software/data/db2/zos/support.html
Then click on white papers, redbooks, presentations, ...
DB2 information on the web: RTFW
On Mon, 20 Dec 2004 08:28:24 -0600, Gerald Hodge
<[login to unmask email]> wrote:
>We encountered several issues, but we were in the early support
for V8 and
>so I am not sure where all these issues stand. The only mode I
>where fall back is available is in Compatibility Mode. IBM is
>saying that a complete rebind of your plans and packages is
>statement would seem to obviate a change in reserve words
>One issue that we have not seen on the list of items is that
>and the other related tables need to be in an EBCDIC table
>Otherwise, you will find that EXPLAIN works, but that the
>Another issue is the default for the SQL from the precompiler
>EBCIDIC to Unicode. Your tools need to be able to handle
Unicode at the
>beginning of your conversion.
>Please feel free to contact us offline for more specifics.
>HLS Technologies, Inc.
>From: DB2 Data Base Discussion List
[mailto:[login to unmask email] On Behalf
>Of Nic Honan
>Sent: Monday, December 20, 2004 5:36 AM
>To: [login to unmask email]
>Subject: DB2 z/OS v8 migration: seeking clarification for
>I am planning and preparing to migrate to DB2 for z/OS v8 (from
>I am paying particular attention to Chapter 3 of the Release
> Planning for migration, conversion, and fallback
>Let's take the issue about new reserved words as an
>It is not entirely clear to me when we fall foul of new
reserved words. Is
> a) in CM (Compatability Mode)
> b) during ENFM (Enabling New Function Mode)
> c) in NFM (New Function Mode)
>I won't be getting my hands on V8 just yet, so I can't "test"
>I'd like to think it is in CM. As this means we can catch any
>applications that we failed to spot before we go NFM.
>I could probably extend seeking this type of clarification to
>in Chapter 3 ...
>Nic Honan [login to unmask email]
>John Lewis Partnership
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives
and home page at http://www.idugdb2-l.org/archives/db2-l.html.
From that page select "Join or Leave the list". The IDUG DB2-L FAQ
is at http://www.idugdb2-l.org.
List Admins can be reached at [login to unmask email] Find
out the latest on IDUG conferences at http://conferences.idug.org/index.cfm