DB2 z/OS v8 migration: seeking clarification for release incompatibilities

Nic Honan

DB2 z/OS v8 migration: seeking clarification for release incompatibilities
I am planning and preparing to migrate to DB2 for z/OS v8 (from v7).
I am paying particular attention to Chapter 3 of the Release Planning
Guide:
Planning for migration, conversion, and fallback

Let's take the issue about new reserved words as an example.
It is not entirely clear to me when we fall foul of new reserved words. Is
it:
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" this.

I'd like to think it is in CM. As this means we can catch any affected
applications that we failed to spot before we go NFM.

I could probably extend seeking this type of clarification to other issues
in Chapter 3 ...


-----------------------------------------------------
Nic Honan [login to unmask email]
DBA
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. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Phil Grainger

Re: DB2 z/OS v8 migration: seeking clarification for release incompatibilities
(in response to Nic Honan)
Hmmm

Not 100% sure of this myself, but I would also worry about whether I was
running the pre-compiler NEWFUN(NO) or (YES). I would expect the latter
to flag more reserved word errors than the former UNLESS IBM have been
clever and added "future" reserved word checking to NEWFUN(NO). Of
course, you definitely do NOT want to recompile with NEWFUN(YES) until
you are in NFM!

Phil Grainger
Computer Associates
Product Manager, DB2
Tel: +44 (0)161 928 9334
Fax: +44 (0)161 941 3775
Mobile: +44 (0)7970 125 752
[login to unmask email]


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Nic Honan
Sent: 20 December 2004 11:36
To: [login to unmask email]
Subject: DB2 z/OS v8 migration: seeking clarification for release
incompatibilities

I am planning and preparing to migrate to DB2 for z/OS v8 (from v7).
I am paying particular attention to Chapter 3 of the Release Planning
Guide:
Planning for migration, conversion, and fallback

Let's take the issue about new reserved words as an example.
It is not entirely clear to me when we fall foul of new reserved words.
Is
it:
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" this.

I'd like to think it is in CM. As this means we can catch any affected
applications that we failed to spot before we go NFM.

I could probably extend seeking this type of clarification to other
issues in Chapter 3 ...


-----------------------------------------------------
Nic Honan [login to unmask email]
DBA
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. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
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. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Gerald Hodge

Re: DB2 z/OS v8 migration: seeking clarification for release incompatibilities
(in response to Phil Grainger)
Nic:

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 am aware of
where fall back is available is in Compatibility Mode. IBM is no longer
saying that a complete rebind of your plans and packages is required. This
statement would seem to obviate a change in reserve words for compatibility
mode.

One issue that we have not seen on the list of items is that the PLAN_TABLE
and the other related tables need to be in an EBCDIC table space.
Otherwise, you will find that EXPLAIN works, but that the output is
unreadable.

Another issue is the default for the SQL from the precompiler changed from
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.

Gerald Hodge
HLS Technologies, Inc.
888-494-9019




-----Original Message-----
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 release
incompatibilities

I am planning and preparing to migrate to DB2 for z/OS v8 (from v7).
I am paying particular attention to Chapter 3 of the Release Planning
Guide:
Planning for migration, conversion, and fallback

Let's take the issue about new reserved words as an example.
It is not entirely clear to me when we fall foul of new reserved words. Is
it:
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" this.

I'd like to think it is in CM. As this means we can catch any affected
applications that we failed to spot before we go NFM.

I could probably extend seeking this type of clarification to other issues
in Chapter 3 ...


-----------------------------------------------------
Nic Honan [login to unmask email]
DBA
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.
The IDUG List Admins can be reached at [login to unmask email] Find
out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
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. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Roger Miller

Re: DB2 z/OS v8 migration: seeking clarification for release incompatibilities
(in response to Gerald Hodge)
Reserved words are found when you precompile or BIND them. You'll get the
errors in CM if you precompile or BIND there, but the usual story is that
customers don't do everything at once, so we still see problems from V5
reserved words.

Whenever you move from one release to another, there are some changes to
manage. It is possible, but rare to find SQL which processed in the prior
release that will not run on the new one. If you have users who test the
boundaries, instead of reading the limits, then this is more common.
Reserved words are handled in context when possible, but new reserved words
can cause problems in SQL that worked on the prior release. It is also
possible to find problems with words that have been reserved for several
releases in a new context. Check for APARs.

The best technique for dealing with reserved words is to get a list of the
reserved words from the SQL Reference for Cross-Platform Development,
Appendix O. Reserved schema names and reserved words. Compare that list
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 web.
Here are the primary DB2 V8 migration resources, but get to them from the
Support web page http://www.ibm.com/software/data/db2/zos/support.html
Then click on white papers, redbooks, presentations, ...

White papers:
ftp://ftp.software.ibm.com/software/data/db2zos/db2v8dbv.pdf
ftp://ftp.software.ibm.com/software/db2storedprocedure/db2zos390/techdocs/V
8planmigrate.pdf
ftp://ftp.software.ibm.com/software/db2storedprocedure/db2zos390/techdocs/V
8migrateprocess.pdf
http://www.ibm.com/support/docview.wss?
rs=64&context=SSEPEK&q1=presentation&q2=V8+and+migration&uid=swg27005493&lo
c=en_US&cs=utf-8&lang=en

Presentations:
ftp://ftp.software.ibm.com/software/data/db2zos/z04rm.pdf
ftp://ftp.software.ibm.com/software/db2storedprocedure/db2zos390/techdocs/S
1345.pdf
ftp://ftp.software.ibm.com/software/db2storedprocedure/db2zos390/techdocs/O
F2.pdf
ftp://ftp.software.ibm.com/software/db2storedprocedure/db2zos390/techdocs/O
A2.pdf
ftp://ftp.software.ibm.com/software/data/db2zos/Z21.pdf

http://www.ibm.com/support/search.wss?rs=64&lang=en&loc=en_US&r=10&cs=utf-
8&rankfile=0&cc=&spc=&stc=&apar=include&q1=presentation&q2=V8+and+migration
&sort=desc&tc=SSEPEK&Go.x=9&Go.y=10&dc=DA400+DB300+DA100+DA110+DA120+DB100+
DA700+DA450+DA300&dtm

DB2 information on the web: RTFW
ftp://ftp.software.ibm.com/software/data/db2zos/doc.pdf

Roger Miller

On Mon, 20 Dec 2004 08:28:24 -0600, Gerald Hodge
<[login to unmask email]> wrote:

>Nic:
>
>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 am aware
of
>where fall back is available is in Compatibility Mode. IBM is no longer
>saying that a complete rebind of your plans and packages is required.
This
>statement would seem to obviate a change in reserve words for
compatibility
>mode.
>
>One issue that we have not seen on the list of items is that the
PLAN_TABLE
>and the other related tables need to be in an EBCDIC table space.
>Otherwise, you will find that EXPLAIN works, but that the output is
>unreadable.
>
>Another issue is the default for the SQL from the precompiler changed from
>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.
>
>Gerald Hodge
>HLS Technologies, Inc.
>888-494-9019
>

>-----Original Message-----
>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 release
>incompatibilities
>
>I am planning and preparing to migrate to DB2 for z/OS v8 (from v7).
>I am paying particular attention to Chapter 3 of the Release Planning
>Guide:
> Planning for migration, conversion, and fallback
>
>Let's take the issue about new reserved words as an example.
>It is not entirely clear to me when we fall foul of new reserved words. Is
>it:
> 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" this.
>
>I'd like to think it is in CM. As this means we can catch any affected
>applications that we failed to spot before we go NFM.
>
>I could probably extend seeking this type of clarification to other issues
>in Chapter 3 ...
>
>
>-----------------------------------------------------
>Nic Honan [login to unmask email]
>DBA
>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. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm