Re: Deprecation of NAMING parameter on RUNSQLSTM command. -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Yes, we changed to allow a period as an object qualifier for system naming
in a DB2 PTF group in 2012 for 7.1. It was in the base 7.2 release. Note
that the NAMING parameter remains meaningful for determining how to
qualify unqualified object names (such as tables). Here is a link to the
IBM i wiki page that describes the change.

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/System%20naming%20convention%20expanded%20to%20permit%20%28slash%29%20and%20%28dot%29%20qualifiers

Sue Romano
IBM i SQL Development

It looks to me like IBM is deprecating the NAMING parameter on the
RUNSQLSTM command.

With current PTFs you no longer have to specify NAMING(*SQL) when you

code

something like
mylib.mytable
If it sees a period there it will make it work with NAMING(*SYS). Which
used to require mylib/mytable.

Confirmation:
http://www-912.ibm.com/a_dir/as4ptf.nsf/a18db68aae4a7d81862566ba005d145c/abe9230551696e6286257a5d0068c474?OpenDocument

I just noticed this while working on a reply on another thread. I thought

I'd better break this out as a new thread to make it stick out more.

Rob Berendt

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.