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



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.

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