× 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.



Jerry,
I have not used WDSC auto formatting and auto closing of structures. I
hated having to delete an endif everytime I wanted to wrap a block of text
in a new logic check. That's just the tip of the iceberg. I use the
auto-indent after a structure like IF, DO, etc. This works well enough
for me. None of my other statements indent though.

As to the second email... it sounds like you are somehow still inside the
scope of an sql statement. Make sure you aren't missing a semicolon
somewhere. A forgotten semicolon can be a nightmare. It can make it seem
like your source is a total mess and you'll never get the 1000 errors to
go away. Then you find the line, place the semicolon and everything
clears up. I find there is much left to be desired when it comes to the
compiler helping out with certain error messages.

I always had a lot of trouble with the syntax checking because I don't
write every line perfect. I write my opening structure 'if' before my
closing structure 'endif' which always throws an error in the code and
then you have to CTL+F5 to make it go away. Big pain in the butt. I'll
wait until compile time to check for errors. I don't make that many
syntactical mistakes that I need WDSC looking over my shoulder every
second complaining to me and slowing me down.

Just some thoughts, take them for what they are worth.


Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777



Jerry Adams <Jerry@xxxxxxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
12/14/2009 12:01 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
"Midrange-WDSc (wdsci-l@xxxxxxxxxxxx)" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
[WDSCI-L] SQLRPGLE Entry in WDSCi v7






I am having a frustrating issue when entering an SPQRPGLE program with
RSE.

Whenever I type a non-SQL statement and press the Enter key, a new line is
inserted (which, of course, should happen), and the RSE cursor moves to
the line following the last SQL statement - not to the blank line that it
just inserted.

I searched the archives but could not find anything on this so it must be
some setting that I have wrong. Under Preferences->Remote
Systems->iSeries Parsers->ILE RPG->Free form SQL formatting I have
Automatic indent checked, Automatic formatting checked with On Commas =
After, On AND.OR keywords = After, On Case keyword unchecked, and Comments
= Move to top. Under LPEX Editor->Parsers->Parser Associations SQLRPGLE =
ILErpgSql.

The source member type is SQLRPGLE. Code section:

/free

EXEC SQL
Declare CustMast cursor for
SELECT arcust,
arsm#,
From A.ARMAST
Where arcust in (SELECT customer
From LAYTRACK)
For Read Only;

EXEC SQL
Open CustMast;

DOW 1 = 1;

EXEC SQL
Fetch Next from CustMast Into :custpi, :routepi;

IF sqlstate = '02000'
OR sqlcode < *Zeros;
LEAVE;
ENDIF;





ENDDO;

All of the blank lines between the ENDIF and the ENDDO were inserted by
the editor after keying each IF clause statement. The RSE cursor jumped
back to the line right after the Fetch SQL statement so I had to position
to the line where I wanted the next non-SQL statement.

Since no one else has reported this problem, what am I doing wrong or what
other settings do I need to check?

Thanks.

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


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.