Success! :-)
I found this article very helpful:
http://www.itjungle.com/fhg/fhg050306-story02.html
and these two also were interesting reading:
http://www-912.ibm.com/s_dir/slkbase.NSF/0/2554db904e5a601b862565c2007cc4b8?OpenDocument
http://www.systeminetwork.com/article/rpg-programming/use-libl-for-stored-procedures-and-udfs-65996
For what I'm doing, the keys turned out to be a) connect using a user profile whose library list is set by their job description (Dan, you nailed that one), and b) specify System naming convention in the connection string (Robert, you pointed the right
way, but I'm not using Exec SQL, so I had to do it differently: as the first article above explains, I had to put "Naming Convention=1;" in my connection string argument list).
The upshot is that based on what I want to do, I can choose the user profile that I want to connect with, and the stored procedure will use that user's library list to find what it needs. Not only that, I found that I no longer have to specify the
library when I call the stored procedure from the PC side -- the user's library list will determine which version of the stored procedure gets called.
This is really slick. I just wish I had known all this two years ago .... ;-}
Thanks again to everyone for your help,
Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA 01376
413-676-3144
Internal: x 444
mnaughton@xxxxxxxxxxxx
****************************************
NOTICE: This e-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that any use is
strictly prohibited. If you have received this e-mail in error, please notify us immediately by replying to it and then delete it from your computer.
midrange.com
