Re: Stored procedure call not working

Figured it out. It was finding the program fine. The issue was that there
was a service program on the bind list that was not in library list so it
was bombing but instead of reporting that the program crash the iSeries was
saying that it couldn't find the program. Add the service program in and
everything works fine.

On Wed, Jul 29, 2015 at 12:56 PM, Alan Campin <alan0307d@xxxxxxxxx> wrote:

Yep, only difference is the parameter name is in upper and lower case and
bigint in lower case. Everything else is the same.
.Tried changing back to original and it still works. Not sure what the
difference was.


On Wed, Jul 29, 2015 at 12:47 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

I don't see the difference...

What am I missing?

Charles

On Wed, Jul 29, 2015 at 3:41 PM, Alan Campin <alan0307d@xxxxxxxxx> wrote:

Well changed to this and it worked. Doesn't make much sense given that

the

compiler upper cases the name.

CREATE PROCEDURE DEVIILIB/TESTITRANSFER(IN InIdNumber BigInt)
LANGUAGE RPGLE
NOT DETERMINISTIC
NO SQL
EXTERNAL NAME 'DEVIILIB/ITTEST(TESTPROCEDURE)'
PARAMETER STYLE GENERAL

dcl-proc TestProcedure Export;
dcl-pi *N;
InIdNumber Int(20);
end-pi;



On Wed, Jul 29, 2015 at 12:08 PM, Alan Campin <alan0307d@xxxxxxxxx>

wrote:

"SELECT * from SYSPROCS and see if there is another SP with the same

name."

Nope, only one TESTITRANSFER in SYSPROCS.

On Wed, Jul 29, 2015 at 12:02 PM, Buck Calabro <kc2hiz@xxxxxxxxx>

wrote:

On 7/29/2015 11:19 AM, Alan Campin wrote:

I have a defined a stored procedure using a service program

CREATE PROCEDURE DEVIILIB/TESTITRANSFER(IN ID_NUMBER BIGINT )
LANGUAGE RPGLE
NOT DETERMINISTIC
NO SQL
EXTERNAL NAME 'DEVIILIB/ITTEST(TESTPROCEDURE)'
PARAMETER STYLE GENERAL

-snip-

I can call this stored procedure through an RPG program without a

hitch

but

when I try to call from Ops Nav or from a C# program it fails with

a

message saying

Program ITTEST in library DEVIILIB not found. Obviously the service

program

is there because I works through RPG

Best guess is that you have ANOTHER stored procedure that matches a
different signature. That SP is trying to call the non-existent *PGM
object and falling over.

SELECT * from SYSPROCS and see if there is another SP with the same

name.

--
--buck

--
This is the RPG programming on the IBM i (AS/400 and iSeries)

(RPG400-L)

mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.