|
Hi Buck, The outline view doesn't yet support embedded SQL, but its on out list of requirements. I thought that the outline view did show line numbers - which is not the same thing as sequence numbers. Look at the top left over the ruler in the LPEX window, and you will see your current cursor position by Line and Column. thanks, Violaine Batthish WebSphere Development Studio Client, IBM Toronto Lab wdsci-l-bounces@xxxxxxxxxxxx wrote on 03/20/2007 11:05:00 AM:
Thanks to posts here, but especially to the blog (http://wdsc.wordpress.com/), I'm trying the Outline view for the first time. Yeah, yeah, go ahead and snicker. I've been using the spooled file compiler listing all this time. Anyway, I'm ashamed to say that I have been ignoring discussions of the Outline view because I haven't been using it. I looked in the archives, help and Windows->Preferences and didn't see how to adjust any settings, so I'll ask here with an apology if I skipped an earlier answer. I'm looking at an SQLRPGLE source member. I'm FETCHing into a qualified
DS.
1) The Outline view doesn't show any references to some members of that DS, probably because they're referred to only by the precompiler. Is there a setting for that? 2) What do the line numbers mean in the Outline view? They neither match the Lpex line numbers in the edit window, nor do they match the compiler listing line numbers. Not crucial since clicking on a line takes you there. (That's interesting behaviour that I might want to tap into with a plug-in!) 3) Is there a way to get the Outline view to recognise the columns used in the DECLARE ... CURSOR? For instance, DECLARE CURSOR FOR SELECT NAME FROM MYTABLE. 'NAME' doesn't show in the Outline view. Of course, it doesn't show in the compiler cross reference either, but a guy can always hope can't he? :-) This is a nifty thing. Need to use it more. Nice job! --buck
As an Amazon Associate we earn from qualifying purchases.
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.