|
Thanks to Vern, I found a solution to this problem. I am giving the solution so that it helps someone in the future. If your procedure looks like the following (with or without parameters), Create Procedure PLib/TestProc (In iUserId char(10), Out oRetcod char(3)) result sets 1 Language RPGLE Modifies SQL Data External Name TestPgm - PLib does not need to be a valid library in the system. - External name is the RPGLE program name (in the above case). If we do not give any library name, it defaults to *LIBL. (If you enter *LIBL for library, the procedure will error out.) The program object TESTPGM should be available in the library list while calling the procedure. - You could take a look at the details using either sysprocs or sysroutines and make sure the specific schema- procedure library, routine - procedure, and external names - library/programname are correct. - The SQL path did not matter to me in my case since the sql was not deterministic. This way, we can avoid creating more than one procedure (and figuring out their specif names) if they are all pointing to the same process. Thanks, Sudha -----Original Message----- From: Ramanujan, Sudha Sent: Tuesday, January 14, 2003 11:05 AM To: midrange-l@midrange.com Subject: Stored Procedure question I have a java application running well with stored procedure(s). These stored procedures are created in an X library which the Java modules refer to. But now I need to set up an environment for other departments who do not have any authority on my program library and neither do I have on their program library. So typically when I create another set of procedures in the X library pointing to their program library programs, mine stops working. Is there a way I could get this to work without changing my application reference(s)? Thanks, Sudha _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.