× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Thanks Rob.

It is a single module service pgm, but not an SQLRPG. It contains no
embedded SQL. So I just issue a CRTRPGMOD. So I just have a *Module and
a *SRVPGM object in my library.

Greg

|-----Original Message-----
|From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
|bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
|Sent: Tuesday, September 11, 2007 9:05 AM
|To: Midrange Systems Technical Discussion
|Subject: RE: Syntax for calling stored procedure
|
|Perhaps you are on the right track. Maybe it is an "SQL Package"
issue?
|
|If your service program is a single module service program and you
issued
|the CRTSQLRPI to create the service program then the *SQLPKG object
should
|have been created. If your service program is a multiple module
service
|program you might have to issue the CRTSQLPKG separately.
|
|>From the help on OBJTYPE:
|When OBJTYPE(*PGM) or OBJTYPE(*SRVPGM) is specified and the RDB
|parameter is also specified, the CRTSQLPKG command is issued by the
|SQL precompiler after the program has been created. When
|OBJTYPE(*MODULE) is specified, an SQL package is not created and you
|must issue the CRTSQLPKG command after the CRTPGM or CRTSRVPGM
|command has created the program.
|
|Try WRKOBJ GNODGF/SORDERAPI. You should have two objects, a *SRVPGM
and a
|*SQLPKG.
|
|Rob Berendt
|--
|Group Dekko Services, LLC
|Dept 01.073
|PO Box 2000
|Dock 108
|6928N 400E
|Kendallville, IN 46755
|http://www.dekko.com
|
|
|
|
|
|"Fleming, Greg \(ED\)" <GFLEMING@xxxxxxxxxxxxxxxxxxxx>
|Sent by: midrange-l-bounces@xxxxxxxxxxxx
|09/11/2007 08:15 AM
|Please respond to
|Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
|
|
|To
|"Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
|cc
|
|Fax to
|
|Subject
|RE: Syntax for calling stored procedure
|
|
|
|
|
|
|Thanks Alan.
|
|When I do that, I get the following:
|
|SQL State: 42724
|Vendor Code: -444
|Message: [SQL0444] External program SORDERAPI in GNODGDF not found.
|Cause . . . . . : An attempt was made to CALL procedure or invoke
|function GETSHORTSKU in GNODGDF. External program or service program
|SORDERAPI in schema GNODGDF was not found.
|
|Someone else in my organization said they use question mark instead of
|the out parameter, but I get the same result.
|
|I know the service program is there, and it works when used from a
|regular RPG calling program. Is there something special I need to do
|with the CRTSRVPGM parameters when it is going to be used with an SQL
|stored procedure ?
|
|Greg
|
||-----Original Message-----
||From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
||bounces@xxxxxxxxxxxx] On Behalf Of Alan Campin
||Sent: Monday, September 10, 2007 6:08 PM
||To: midrange-l@xxxxxxxxxxxx
||Subject: Re: Syntax for calling stored procedure
||
||<snip>
||I got the message indicating that it was successfully created.
||
||Now the question. How do I call it ? Can I test this interactively
||from STRSQL or Iseries Navigator RUNSQL Scripts ?
||
||What's the correct syntax ?
||</snip>
||
||Use Run Sql Scripts in Ops Nav
||
||Call gnodgdf/getShortSKU ('SKU1', '001', '100', '3410')
||
||
||--
||This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
|list
||To post a message email: MIDRANGE-L@xxxxxxxxxxxx
||To subscribe, unsubscribe, or change list options,
||visit: http://lists.midrange.com/mailman/listinfo/midrange-l
||or email: MIDRANGE-L-request@xxxxxxxxxxxx
||Before posting, please take a moment to review the archives
||at http://archive.midrange.com/midrange-l.
|
|
|--
|This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
|list
|To post a message email: MIDRANGE-L@xxxxxxxxxxxx
|To subscribe, unsubscribe, or change list options,
|visit: http://lists.midrange.com/mailman/listinfo/midrange-l
|or email: MIDRANGE-L-request@xxxxxxxxxxxx
|Before posting, please take a moment to review the archives
|at http://archive.midrange.com/midrange-l.
|
|
|--
|This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
|To post a message email: MIDRANGE-L@xxxxxxxxxxxx
|To subscribe, unsubscribe, or change list options,
|visit: http://lists.midrange.com/mailman/listinfo/midrange-l
|or email: MIDRANGE-L-request@xxxxxxxxxxxx
|Before posting, please take a moment to review the archives
|at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.