RE: .NET Unqualified Stored Procedures in the iSeries World.

["Neill Harper" <neill.harper@xxxxxxxx>]

When you define stored proc in SQL (i.e. your create procedure) use SET PATH
= *LIBL; before it.

When connecting from the outside world you  need to set your library list on
the SQL connection object.

In java this is done by the libraries property. I am sure there will be a
similar property on the .net adapter. 

You are also right, you need naming *system on the connection too.

Neill



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Lowary, Jim
Sent: 14 July 2009 18:38
To: midrange-l@xxxxxxxxxxxx
Subject: .NET Unqualified Stored Procedures in the iSeries World.

We are starting into the .net world and using stored procedures in the
iSeries, and are starting to have some problems with testing, promoting,
etc.  Within the stored procedure we are using SYSTEM NAMING convention
and trying to utilize the iSeries User Library List .  The user library
list includes the Developers Testing Library at the top followed by
Production Libraries.  This then causes us to have "ambiguous
references" error if we call UNQUALIFIED stored procedures.   

We would like to use the UNQUALIFIED stored procedures - and take
advantage of the current user's library list - and not hard code the
library name on any stored procedures.   But do not see a way around the
"ambiguous procedure call" problem.

How have others gotten around this and successfully used the power of a
Library List on the iSeries?  We can have a web config file that could
have the environment in it and library qualifiers, and change this file
as in each environment, but this seems to be a dangerous approach (at
least from what the iSeries CMS world is use to).  

Just trying to figure out the best way to handle this?  Problems seem to
come were the PC sql world meets the iSeries sql world and things blur
(or we just don't have a good grasp on how to set thing up because we
are to iSeries focused).

Any ideas, suggestion etc. would be welcomed.

Thanks,
--Jim Lowary
Mo Farm Bureau