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



Very cool, Paul - I get so much from this list, I'm glad to give a little back.

Vern

On 12/14/2016 5:05 AM, Paul Bailey wrote:
Thanks everyone.

Using Vern's tip to specify Q*SRC as the source file name in all member
filters, I can filter out the precompiler temporary sources and the
EVFTEMP* source file. The TOSRCFILE(...) option on CRTSQLRPGI only works
for the QTEMP/QSQLTEMP1 source file, not QTEMP/QSQLPRE or *libl/EVFTEMP*
source files, so wasn't the best option.

This only leaves the situation for that one source file that doesn't match
Q*SRC and I think I can manage that one manually. Hopefully I'll remember
the next time I need to use it.

I now have to go through and amend all my member filters from SRCFILE(*) to
SRCFILE(Q*SRC). Should be fairly easy if I can find the correct
node.properties file in my workspace. :)


-Paul.



On 13 December 2016 at 12:56, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

Hi Paul

I tried a couple things - you might try setting the file value to Q*SRC or
some other generic name.

I might also recommend adding entries in the filter for each library in
use - I know, but *USRLIBL feels like too inclusive - I say that without
knowing enough about your environment.

The Q*SRC idea assumes you are using IBM's recommended names.

You CAN specify a library and source file for the SQL compiles to use
instead of the default in QTEMP.

I don't think you have much help with the EVF* files - they are needed to
get the stuff that displays after compilation.

Just some ideas -maybe they'll stir up others.

Vern

On 12/13/2016 5:29 AM, Paul Bailey wrote:

Hi,

I create member filters in RDi (v9.5.1) to list the source members I am
working on for a project. I often use the *USRLIBL option in the library
part of each filter string.

When I compile SQLRPGLE source, additional members are created in QTEMP
with the same name as the source member I'm working with (SRCFs QSQLTEMP1
and QSQLPRE), so if I right-click one of those in my member filter
unexpected results can come up (compile/compare wrong source, etc.)

Additionally, when compiling any RPGLE program, the compiler puts a source
member in the EVFTEMPF01 file in the "object" library, which also shows up
in a member filter using *USRLIBL (or *LIBL). This EVFTEMP01 member then
causes similar problems to the above if I misclick or don't pay enough
attention.

Can I filter out all source files in QTEMP and the EVFTEMPF01 source file
from anywhere in the library list if my filter string contains *LIBL,
*USRLIBL, *ALL or *ALLUSR? I want to do that at a member filter string
level (with the default controlled by a RDi preference.)

Can I relocate those QTEMP source files, and/or that EVFTEMPF01 source
file
when compiling?

I'll raise an RFE if I have to, but can anyone suggest anything to help?
Removing the object library from the library list won't work for me, and
specifying things other than *USRLIBL will mean I need to take a lot more
time to create a set of filter strings each with a specific library name.


-Paul.

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