What naming conventions were used when generating the stored procedure?
Even though the environment uses *SYSTEM naming conventions, it the stored
procedure was created with *SQL Naming conventions, it will run with SQL
Naming conventions (independent of the naming conventions used in the
environment)
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
Modernization ? Education ? Consulting on IBM i
Database and Software Architect
IBM Champion since 2020
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
"Train people well enough so they can leave, treat them well enough so they
don't want to. " (Richard Branson)
"Learning is experience ? everything else is only information!" (Albert
Einstein)
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Justin
Taylor
Sent: Wednesday, 18 March 2026 21:10
To: MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Resolving *SRVPGM for ext stored proc
I have an external stored procedure around a RPGLE service program. The
stored proc does not specify a library for the service program. For some
reason, source control promotes the stored proc to 2 libraries. The service
program only exists in 1 of those libraries.
The .NET caller uses System naming. The library list contains both of the
libraries where the stored proc resides. It finds and executes the stored
proc in the highest library in the *LIBL. Then it assumes the service
program is in the same library, rather than using *LIBL. Since the service
program doesn't exist in that library, it fails (the service program is in
the other library).
How can I get it to use *LIBL to resolve the service program?
Thanks
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
midrange.com
