Migration: Handling Reserved Words
 
  Problem
I am preparing to migrate to DB2® for z/OS® Version 8. When will I run into problems with reserved words? In compatibility mode, enabling-new-function mode, or new-function mode? What do I need to do?  
   
Solution
Reserved words are found when you precompile or BIND. You'll get the errors in compatibility mode if you precompile or BIND in that mode.

When you move from one release to another, you need to manage some changes. It is possible, but rare to find SQL that processed in the prior release but does not run in the new release. This situation is more common for users who test the boundaries. Reserved words are handled in context when possible, but new reserved words can cause problems in SQL that worked in the prior release. You might also find problems with words that have been reserved for several releases in a new context. Check for APARs. http://www-1.ibm.com/support/search.wss?rs=64&lang=en&loc=en_US&r=10&cs=utf-8&apar=include&q1=&Go.x=14&Go.y=12&sort=desc&tc=SSEPEK&dc=DB550+D100&dtm

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 you find matches, make changes or use delimited identifiers.


P.S. Please pass my address to anyone interested in DB2 HOTLINE - thank you.

With kind regards
Michael Dewert, Software GroupTechnical Sales DB2