RE: Embedded SQL problem

Once again you have all come through!  Thank you all for your help.  The
program was indeed compiled with commit(*CHG) and now that I have
recompiled it works great!!

Roger Boucher
Standard Pacific Corp.
rboucher@stanpac.com
714-668-4326


-----Original Message-----
From: David Morris [mailto:dmorris@plumcreek.com]
Sent: Monday, March 29, 1999 4:23 PM
To: RBoucher@stanpac.com
Subject: Re: Embedded SQL problem


Roger,

I thought you might want some information quickly so I sent this to you 
directly.  I also believe you will get lots of responses.

You can display the message by appending the reason code to SQL and 
looking in QSQLMSG.  dspmsgd sql7008 qsqlmsg.  You should have a low 
level message in your joblog that contains the formatted and complete 
message text. A quick and wild guess is that the program was compiled 
with COMIT(*CHANGE) and should have been COMIT(*NONE).

David Morris

>>> Roger Boucher <RBoucher@stanpac.com> 03/29/99 04:38PM >>>
I am trying to debug a vendor's program with embedded SQL and I regret
to say I have never had the opportunity to learn how this works.   I am
using ISDB/400 (IS Debug) and can not follow the lines of code where it
is executing SQL.  I know that no records are being loaded to the
subfile and the reason is an "SQL code" of -7008.  Does anyone know what
this means, or how I might be able to debug the SQL executable
statements?

P.S.  The Select string that is being built by the application before
heading into the SQL executable statements is valid and selects the
proper records when run through STRSQL.

Thanks for any help!


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---