Re: Can I filter the library list in a RSE Member Filter?

Why don't you just change the filter string instead of going into your
workspace? Just right click on the filter and select properties. Then go
to filter string. You can also add the exception here by creating a new
filter string for it in this filter. No need to mess with the
node.properties file.

Jim Diephuis
IBM i consultant, IBM certified IT Specialist
Lab Services Power Systems Delivery Practice
phone: 507.253.1248
e-mail: diephuis@xxxxxxxxxx





From: Paul Bailey <PabloMotte+Midrange@xxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date: 12/14/2016 05:06 AM
Subject: Re: [WDSCI-L] Can I filter the library list in a RSE
Member Filter?
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



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.