In Preferences under LPEX Editor, Parsers, Parser Associations, I think you can associate your ‘custom’ source types with the appropriate parser so that LPEX will correctly handle it. I remember doing it once some years ago in WDSCi, although I no longer remember why (yeah, memory is the first to go). Anyway, give it a go and see if it does what you’re looking for.
Sent from Mail for Windows 10
Sent: Wednesday, April 5, 2017 2:08 PM
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] Force LPEX editor to treat member as RPGLE even when it'snot?
We currently use a "fly by the seat of your pants" method of checking out
source code in this shop. (And to avoid that whole debate, please know
that we are currently investigating CMS options.) Here's what we do:
1) Find source code in production library using WRKMBRPDM
2) Copy it to our personal development library
3) Append our initials to the source member type in the production library;
this notifies others that someone has checked out the source.
4) Modify the source in our personal dev library, test, QA, etc.
5) "Promote" modified source back to production library. (Original source
name is renamed, appending '.nn' to it, where nn is a sequence number.)
The problem is when I want to browse the unmodified original source while
modifying the source in my library, the LPEX editor will not recognize
RPGLE_SPJ as an RPGLE source type. Is there a way to force it to do that
so I can get the outline and the editor highlighting?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.