× 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 believe this has to do with the way how the originating object that
you run QSQGNDDL against is created.

In my environment for example I have a stored procedure that was
originally generated with:
SET SCHEMA MGGPL ;
CREATE PROCEDURE Get_All_Blah

After using QSQGNDDL the outputted source shows
SET PATH "QSYS","QSYS2","SYSPROC","SYSIBMADM","SIMONSEA" ;
CREATE PROCEDURE MGGPL.Get_All_Blah

Procedures that are originally created with SET PATH *LIBL do also
output SET PATH *LIBL after QSQGNDDL.

Regards,
-Arco
_

2018-06-26 21:27 GMT+02:00 David Gibbs <david@xxxxxxxxxxxx>:
Folks:

Does anyone know what controls the value of the 'SET PATH' statement that
appears when you use the QSQGNDDL api or GENERATE_SQL procedure?

99% of the time it's set to *LIBL ... but on very rare occasions I've seen
libraries (although I can't remember a specific instance).

Thanks!

david


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.