|
Hi,
I have an unexpected behaviour when i call my (RPG) stored procedure on the
AS400. I am using the AS400 toolbox.
I have a pool of connections.
For each connection i set 3 library lists in java. (i do an execute command
"AddLibl")
I know that the last lib that is added will be used first.
When i call the stored procedure i don't prefix the call with name of the lib.
(e.g CALL EVALUATE_ACCOUNT instead of CALL MYLIB.EVALUATE_ACCOUNT)
I am surprised to see that if the stored procedure is not in the first
library, it is not
found (searched?) in the other libraries.
This is a bit annoying since i have some stored proc in my developpement
environment,
but some others are already in my integration environment.
I did'nt expected such a behaviour.
I use the naming = system convention.
Any one can help. I pretty sure it can search the stored proc in the other
libraries.
We do that with the datasource of websphere. I don't expect something
different
with classic JDBC.
All the examples i can find in the IBM document use something like MYLIBNAME.MYPROCEDURE
I have tried that, also specifying libraries in the connection URL (say ANOTHERLIB)
If MYPROCEDURE is not found in MYLIBNAME it is not found/searched in ANOTHERLIB.
Should i set something special on my profile on the AS400?
Many thanks
Gilles
Gilles Ducret
Wealth Management Division
IT Architect
Lloyds TSB Bank
Tel: + 41 22 307 31 50
Mob: +41 79 217 21 41
**********************************************************************
This E-mail and any files transmitted with it are confidential
and intended for the exclusive use of the addressee(s) only.
You should not disclose its contents to any other person.
If you are not the intended recipient please notify the sender
immediately.
**********************************************************************
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.