Thanks Rob,
I do see the SQL procedure exists, the script below is only to
call the SQL proc, so maybe it's our PTF level - ops mgr just
stopped by to say we're not yet to ptf level - 26 which Michael
spec'd in his article from Jan 15, 2014.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, September 02, 2014 11:10 AM
To: Midrange Systems Technical Discussion
Subject: Re: testing an SQL procedure
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...
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Gary Thompson <gthompson@xxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 09/02/2014 12:56 PM
Subject: testing an SQL procedure
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
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.
midrange.com
