×
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.
I'm not sure what this message means - I just ran the statement given
here with both syntaxes in turn while the naming was *SYS - at 7.3 of
the OS, at least, both were successful, with no SQL5016. The same result
using 3-part naming.
I did this in both STRSQL and the ACS Runner - I also looked up things
in the reference, there is, at 7.4, this footnote -
18 For system naming, the qualified form that uses a period is also
accepted.
So I ran the statement in STRSQL, setting *SQL naming after in the
environment, and got the 5016 message when using *SYS syntax.
I believe this started at 7.1 - the 6.1 manual doesn't have the footnote.
So it seems that *SYS gives flexibility - you get the *LIBL for
unqualified names and you can use either convention for qualified names
- I've not tested every kind of object, however.
Regards
Vern
On 3/15/2020 1:38 AM, D*B wrote:
How can I check a running job to determine if it's using SQL or System
naming?
From inside: select * from sysibm/sysdummy1 brings up Y for system
naming or
SQL5016 for SQL naming.
From outside it might depend on the running Job and how it is using SQL.
D*B
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.
midrange.com
