× 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.



Mike,

I know I had some problems with Cobol SPs and the way they handled OUT
parms. What happens if you change the definition of the 4th and 5th parm
from OUT to INOUT?

-Walden

------------
Walden H Leverich III
President
Tech Software
(516) 627-3800 x11
(208) 692-3308 eFax
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com 

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
 

-----Original Message-----
From: Mike.Crump@xxxxxxxxxxxxxxxx [mailto:Mike.Crump@xxxxxxxxxxxxxxxx] 
Sent: Wednesday, April 23, 2003 11:11 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Stored Procedure question


I'm working on our first attempt with a stored procedure.  Effectively, I
have an external website that is requesting us to run a program and
generate a PDF file on the fly and place it back on the calling website
(also an AS/400).  So, this is not your typical type of SQL stored
procedure and I am not returning a data set to the calling program.

Effectively, the calling program sends the header data (customer, item,
etc.) and we return the success of the request and the name of the file we
have created via parameters.

Here is the code I used to generate the SP:

CREATE PROCEDURE SP(IN PROD CHAR(5), IN PRODSUFF CHAR(4), IN CUSTNO
      CHAR(9), OUT PDFfile CHAR(128), OUT ReturnValue CHAR(1) )
       LANGUAGE CL
       NOT DETERMINISTIC
       NO SQL
       EXTERNAL NAME LIBRARY/PROGRAM

The calling program is a Notes agent and it is effectively doing this:

CALL QGPL.SP ( '05425','0601','407580601','
',' ')

We've also tried just doing the call with the 3 input parameters and it
also errors out.  With the current statement we are getting this error
(back to the Notes agent):

Error code: 720
Error message:    IN, OUT, or INOUT not valid for parameter 4 in procedure
SP in QGPL.

I'm not sure if I understand the error message.  Evidently I have a
parameter issues but I'm not sure what.  I've considered adding the
statement PARAMETER STYLE GENERAL to my create statement.  Also, I've
hunted and not found any corresponding job on the target AS/400 that also
might contain some job log information.  I see the job start and end on the
system but I haven't been able to determine what job description to modify
to help generate more job log information for the individual job requests.

So, can anyone shed light on the correctness of the create statement,
parameter requirements, info on the intent of the error statement, can I
find more information about the error on the target AS/400, and any other
problem determination techniques?  I've been through the DB manual and the
two redbooks that cover the SP subject area and haven't had much luck.


Michael Crump
Saint-Gobain Containers
1509 S. Macedonia Ave.
Muncie, IN  47302
(765)741-7696
(765)741-7012 f
(800)428-8642

"We will meet that threat now with our Army, Air Force, Navy,
Coast Guard, and Marines so that we do not have to meet it later
with armies of firefighters and police and doctors on the streets of
our cities."  George W. Bush  March 19, 2003







_______________________________________________
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.cgi/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 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.