Re: 'SET PATH' statement when using QSQGNDDL api or GENERATE_SQL procedure?

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