Re: ADO Connection to iSeries

Mike, I think your problem may be that unless you tell the stored
procedure to use the library list explicitly it won't. The way to tell
the stored procedure to use the library list is to change the stored
procedure to use NAMING=*SYS.
We do this in RPG using a Set Option statement such as
// Set the SQL environment
Exec SQL
SET OPTION COMMIT=*none, DYNUSRPRF=*owner, NAMING=*sys,
DLYPRP=*yes, CLOSQLCSR=*endmod;
Make sure that this Set Statement, which will set up the SQL environment,
is physically the first SQL statement in your program.

HTH,

Robert Rogerson

On 2011-11-23 3:13 PM, Michael Naughton wrote:

I'm trying to do something that I had assumed would be pretty basic, but obviously there's something I don't understand.

I'm running a stored procedure on the iSeries (from a Domino agent, if that makes any difference) using an ADO connection. It works fine when I connect using the user profile that we normally use for ADO connections. But when I try to use another user
profile that has a different library list, so the stored procedure will use different files, it doesn't work -- that is, it runs, but it finds the same files that it finds with the default user. Also, I had thought that when I started using the new user
profile to connect I would find QZDASOINIT jobs in QUSRWRK for that profile, but I don't see any.

Can anyone point me in the right direction here? Thank you very much in advance!

Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA 01376
413-676-3144
Internal: x 444
[1]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.

References

Visible links
1. mailto:mnaughton@xxxxxxxxxxxx