Re: Embedded SQL

Thank you!
Carmen 

-----Original Message-----
From: Violaine Batthish [mailto:batthish@xxxxxxxxxx] 
Sent: Wednesday, July 19, 2006 7:52 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Embedded SQL

Hi Carmen,

I am told that this is a bug with the SQL precompiler/syntax checker, and
the same syntax error is issued when in SEU.
The SQL team is investigating.  You may wish to open a PMR.

thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab



wdsci-l-bounces@xxxxxxxxxxxx wrote on 07/10/2006 03:54:14 PM:

My apologies if this belongs elsewhere, but I truly think this is a 
WDSC problem.  This past weekend we upgraded to V5R4.  I'm very 
excited

because

we've started to use embedded SQL a lot and it's annoying to have the

/free,

/end-free surrounding SQL statements.  However, I can't get embedded 
SQL statements to work when I'm coding in the RSE LPEX editor.  We 
have the changed lines signature turned on so we can see who last 
changed a

statement

(Remote Systems -> iSeries -> LPEX Editor Parsers, check Add signature 
to changed lines).  I added a statement like this:

CN      /Free
CN      Exec SQL
CN         Fetch C1 into :ItmFields;

but when it inserts the signature (initials) on the left, I get an

SQL0104

error message - Token CN was not valid. Valid tokens: ( END GET SET 
CALL DROP FREE HOLD LOCK OPEN WITH ALTER BEGIN.  This is an editor 
error

message,

not a compile message.

If I edit on the green screen so it doesn't add the signature 
initials, everything's fine.  I've noticed I can have the signature on 
the Exec

line

and the editor is ok as long as it  isn't on the continuation (Fetch)

line.

Is this bug?  Is there a work-around other than having to edit in the

green

screen or turning off the signature?
I'm on RSE 6.0.1.1, WDSC 6.0.1.

Thanks!
Carmen Nuland