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



I have always put my copybooks in a separate source member so I don't have
that problem. You could assign your copybooks a type of "TXT" or "RPGLEH"
or something similar so they won't be included in the COMPILE.CLLE. You can
even configure RDP to do RPGLE syntax highlighting on whatever type you
decide on and it still won't include it in the COMPILE.CLLE.

It might a bit of a hack, but it works.


On Wed, Jun 1, 2011 at 10:42 AM, Mike Wills <mike@xxxxxxxxxxxx> wrote:

Thanks David and Edmund for the references. However, I didn't learn
what I was hoping a tutorial would cover.

Since I use service programs with my applications, many times the
automatically generated COMPILE.CLLE program has to be heavily edited
to remove the "programs" that aren't programs (like copybooks). How
can I exclude those "programs" from the COMPILE.CLLE. I really would
like more control over how the COMPILE.CLLE is generated.

--
Mike Wills
http://mikewills.me
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.