×

Good News Everybody!

The new search engine is LIVE!

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




Bob's questions spurred me to start looking at writing my own profile. Of course I can't find the darned page with the tutorial but I think I'm close. Anyway, I'm writing queries at the moment so I don't blow anything up. I was a bit surprised to find that query updateProfile.baseProfile tells me that I'm using the seu profile with an RPGLE source member open.

When I go to Window, Preferences, Lpex editor, I can see that I'm set to use the lpex profile. I don't think I really care one way or the other aside from the fact that I don't understand how the thing is put together. I sort of think that I'd want to have some sort of understanding before I go tinkering...

Am I right that WDSC 6.0 uses Eclipse 3.0? I was trying to have a look at the Eclipse documentation to try to follow how Eclipse fires the various classes. In particular, I was trying to see how Eclipse knows to load the RSE, and from there when I open an RPGLE source member, how the proper parser and profile get loaded.

Needless to say I am not going to be making a living reading Java code anytime soon. :-) I can see where (Windows, Preferences, Lpex Editor, Parsers) the parser for ILE RPG is registered. I can't readily see what jar file com.ibm.etools.iseries.editor.ISeriesEditorRPGILEParser lives in, nor where the source might be.

I'll stop rambling. Is there a good reference for the way WDSC loads the editor profile it uses for ILE RPG? Paper works too...
  --buck

As an Amazon Associate we earn from qualifying purchases.

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.