× 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 am trying to create a SQL Function that uses a user defined function in a service program.

I created the CREATE FUNCTION statement in a member in QSQLSRC and used RUNSQLSTM to compile it and create the function. The function was created in the correct library, and iSeries Navigator lists it when I click on the FUNCTIONS dropdown for that specific schema. The function is in one schema and references a service program in another schema. Both schemas are in my iSeries Navigator's schema list.

When I tried using Navigator to test the function it would not work and always said it could not find the service program in *LIBL. I noticed that the QZDASOINIT job that my iSeries Navigator was connected to did NOT have either of those libraries in the library list, even though both were in the schema list.

I went to green screen, set up my correct library list, and used STRSQL to test my SQL statement. It worked fine the first time, and I did not receive any errors.

Has anyone else seen this where changing the Schema List (which I THOUGHT was the library list), does not update the library list on the QZDASOINIT job my iSeries Navigator session is connected to? Is there a PTF to fix this, or is there a bug in iSeries Navigator? Does the schema list not apply to Functions?

Thank you,

Doug


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.