ZOS DB2 v8 Reserve Words

Michael Kaminski

ZOS DB2 v8 Reserve Words
We are currently at DB2 v8 (CM) and have been doing some testing with
the new v8 reserve words and it appears to be tolerated. We tested and
know that you cannot alter a table to add a reserve work but you can
create a table using one. We also did not come across any errors in any
SQL statements using reserve words as well. IBM's response was:

Other customers observed same situation(can create table with column
using reserved words, but can not create index, alter). The question
had been escalated development and developers response was:
--------
*************
There seems to be no way to predict the contexts in
which the parser will complain about the use of a reserved
word as an SQL ordinary identifier. It depends on the complex
state tables generated from the bnf. In some contexts, t
he parser will tolerate a reserved word used as an
undelimited ordinary identifier; in other contexts, it will not.
That's why, in the appendix in the SQL Reference listing
reserved words, we say this (note the words "some" and "might"):
"Table 78 lists the words that cannot be used as ordinary
identifiers in some contexts because they might be interpreted as SQL
keywords."
*********

We already have the programming staff working on eliminating the know v8
reserve words (June 2010) and are waiting for them to finish before
going on the ENFM & NFM.

Can anyone share any similar experiences with this topic? Will v9
tolerate them as well?

Thanks,

Michael A. Kaminski
Systems/DBA
Trustmark Insurance
[login to unmask email]

P Please consider the environment before printing this e-mail





NOTICE: This message and all attachments transmitted with it may contain confidential,
sensitive, or protected information intended solely for the use of the addressee. If the reader
of this message is not the intended recipient, you are hereby notified that any reading,
dissemination, distribution, copying, or other use of this message or its attachments is strictly
prohibited. If you have received this message in error, please notify the sender immediately
by telephone or by electronic mail and delete this message and all copies and backups thereof.
Thank you.



_____________________________________________________________________

* IDUG North America * Tampa, Florida, * May 10-14 2010 * http://IDUG.ORG/NA *
_____________________________________________________________________

http://www.idug.org/db2-videos.html has hundreds of video presentations!
Did you miss out on attending an IDUG conference?
Many of the presentations were recorded and are available on our website!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's DB2-L

Phil Grainger

Re: ZOS DB2 v8 Reserve Words
(in response to Michael Kaminski)
Another way to reduce the burden of eliminating reserved words (especially
when none of us know what reserved words there will be in the future) is to
wrap quote marks around everything that the SQL parser may misinterpret

Ie CREATE TABLE "SELECT" .. Instead of CREATE TABLE SELECT

Phil Grainger
Grainger Database Solutions Ltd

_____

From: IDUG DB2-L [mailto:[login to unmask email] On Behalf Of Kaminski, Michael
Sent: 12 January 2010 18:43
To: [login to unmask email]
Subject: [DB2-L] ZOS DB2 v8 Reserve Words



We are currently at DB2 v8 (CM) and have been doing some testing with the
new v8 reserve words and it appears to be tolerated. We tested and know that
you cannot alter a table to add a reserve work but you can create a table
using one. We also did not come across any errors in any SQL statements
using reserve words as well. IBM's response was:

Other customers observed same situation(can create table with column
using reserved words, but can not create index, alter). The question
had been escalated development and developers response was:
--------
*************
There seems to be no way to predict the contexts in
which the parser will complain about the use of a reserved
word as an SQL ordinary identifier. It depends on the complex
state tables generated from the bnf. In some contexts, t
he parser will tolerate a reserved word used as an
undelimited ordinary identifier; in other contexts, it will not.
That's why, in the appendix in the SQL Reference listing
reserved words, we say this (note the words "some" and "might"):
"Table 78 lists the words that cannot be used as ordinary
identifiers in some contexts because they might be interpreted as SQL
keywords."
*********

We already have the programming staff working on eliminating the know v8
reserve words (June 2010) and are waiting for them to finish before going on
the ENFM & NFM.

Can anyone share any similar experiences with this topic? Will v9 tolerate
them as well?

Thanks,

Michael A. Kaminski

Systems/DBA

Trustmark Insurance

[login to unmask email]



P Please consider the environment before printing this e-mail





NOTICE: This message and all attachments transmitted with it may contain
confidential,

sensitive, or protected information intended solely for the use of the
addressee. If the reader

of this message is not the intended recipient, you are hereby notified that
any reading,

dissemination, distribution, copying, or other use of this message or its
attachments is strictly

prohibited. If you have received this message in error, please notify the
sender immediately

by telephone or by electronic mail and delete this message and all copies
and backups thereof.

Thank you.









_____




< http://www.idug.org > IDUG - The Worldwide DB2 User Community!



The IDUG DB2-L Listserv is only part of your membership in IDUG. If you are
not already an IDUG member, please register here.
< http://www.idug.org/register >


_____________________________________________________________________

* IDUG North America * Tampa, Florida, * May 10-14 2010 * http://IDUG.ORG/NA *
_____________________________________________________________________

http://www.idug.org/events/index.html is your DB2 Events calendar! RUG meetings,
Webcasts, Conferences- what is going on next?
RUG leaders- get your events on the calendar today!
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's DB2-L