RE: testing an SQL procedure

Chuck,
Thanks for your insight.
I failed to think of including that link but will be more thorough in future posts.
Also, as posted to Rob, I now know the partition I am testing on is not yet to
the ptf level spec'd in Michael's article, and our production part not be for a
month or more . . . and, as you see, I don't know how to verify ptf levels . . .

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Tuesday, September 02, 2014 11:20 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: testing an SQL procedure

On 02-Sep-2014 12:10 -0500, rob@xxxxxxxxx wrote:

On 02-Sep-2014 11:56 -0500, Gary Thompson wrote:

Still trying to test my SQL procedure I created last week.
From Four Hundred Guru article
Dynamic Compound Statements in DB2 for i
by Michael Sansoterra:

I'm trying to run the following from Run Sql Scripts:

BEGIN
DECLARE doc_num CHARACTER(11);
call swiretest/fsp975dn ('82 ',1140627,'4200',doc_num); END ;
; This results in:
SQL State: 42601
Vendor Code: -104
Message: [SQL0104] Token DOC_NUM was not valid.

This was run against our test partition which is V7R1M0, with
"recent" PTF's I'm doing everything I can to avoid embedded SQL,
wanting to learn the easier/faster way to create and test SQL
procedures.

Any chance you left out some stuff in the beginning? Like

Create Procedure
MyProcedureName (list of parameters)
Language SQL

and then your Begin and stuff...

Probably best to read the article [why a link was not included in the OP.?.?] referenced in the OP, for why the CREATE PROCEDURE might be unnecessary, for the scripted SQL:
<http://www.itjungle.com/fhg/fhg011514-story02.html>

The OP might want to try the same test script in a RUNSQLSTM to test if there is any difference; perhaps also, to define and verify "recent", esp. with regard to the stated minimum [from the article] of DB2 group PTF level 26.

--
Regards, Chuck
--
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.