× 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,
I've lost a day and a half already on this and I just got through creating a standalone program from the original exported procedure. I put it in a savf and sent it to IBM. Would you like me to forward the email to you?



-----Message d'origine-----
De : midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de rob@xxxxxxxxx
Envoyé : mardi 4 mai 2010 14:14
À : Midrange Systems Technical Discussion
Objet : Re: SQL EXECUTE failing after upgrade to V6R1

Can you post more detailed code at code.midrange.com and put
a link to it in a reply to the list?


Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: David FOXWELL <David.FOXWELL@xxxxxxxxx>
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxx>
Date: 05/04/2010 03:49 AM
Subject: SQL EXECUTE failing after upgrade to V6R1
Sent by: midrange-l-bounces@xxxxxxxxxxxx



All,

We are having a problem with embedded SQL since we went to
V6R1. IBM are
on the case but I thought I would share this with you.

A program is running a series of PREPARE and EXECUTE USING
commands. The
example below shows part of the PREPARE statement. The first
and third
execute OK, the second returns sqlcod=-0901 after the
execute. Debugging,
I find an SQL0117 that says the number of values is different
from the
number of columns.

SET Cclient = ?, Cfld1 = ' ', Cuser = ?, Cdate = CURRENT_DATE
SET Fclient = ?, Fuser = ?, Fdate = CURRENT_DATE
SET Vclient = ?, Vfld1 = ' ', Vuser = ?, Vdate = CURRENT_DATE

If I execute the second statements first, then the other 2
will fail. It
seems that the PREPARE is only being resolved the first time round.
--
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.