×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




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
 

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 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.