Re: Filter Pools

I have a system, that pleases me, but I feel there is always room for
improvement.

On the i5, I call a program that creates my development library. We have
quite a few standards. One is a CLP that quite simply puts the library list
in place and makes the development library as the CURLIB. This program will
always be called when we compile.

I create a RSE connection. I set the properties so that when I connect, this
CLP is called.
In the connection I have 1 filter pool activated. In this pool I have all my
filters based on the CURLIB. One will be called My Developments, for
example, and will automatically show all the sources I am modifying in the
development library.

Now, this is the part I like : when I create a new development library on
the i5, I simply copy my RSE connection and change the library name in the
properties. No need to create any new filters.

To work with the production libraries, I have a separate RSE connection and
there it's not so simple. I have a lot of filter pools. I've tried
organising them by application name like Jeff, I've tried giving each one a
libray name and inside having a filter for names A-D, E-G, etc, but I admit
that its a bit of a mess.

I have one more RSE connection called TEST that I use to test for all my
developments. When I connect to this one, I have to first click on  a
commande filter that will call the library set up program with a prompt so
that I can tell it which test library I am going to use for the connection.
Then, when the connection is established, I will automatically see all my
test programs that are standard from one test library to another.

To recap, I have 3 basic RSE connection types : One for PROD, one for TEST
and as many for development as I have projects to work on.


----- Original Message -----
From: "Mark Keller" <mkeller@xxxxxxxxxx>
To: "Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
Sent: Wednesday, March 28, 2007 5:58 PM
Subject: Re: [WDSCI-L] Filter Pools

I like this thread.  I've only used filter pools to group source members.

I name my pools after libraries and then create a filter for each source
file.  I also had an objects filter so I could set my SEPs on them.  I just
created a programs filter so I don't have to see the files when I go to set
my SEP.  I'm curious to hear how more people use this.

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Dave Boettcher
Sent: Wednesday, March 28, 2007 8:55 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Filter Pools


Too impatient to wait for the first question and tried setting up a
object filter, then clicked on properties and limited it to files and
*SRC* for type to catch all  the old 38 source files also.

Looks great * fewer filters already.

I guess because I always used option 3 on PDM I didn't think of getting
to source members like this but I can probably get used to it.  :>)

Thanks,

Dave B

<jstevens@xxxxxxxxxxxxxx> 03/28/07 9:59 AM >>>

I use filter pools all the time.  For example, I might have an
application
that might take up a dozen or so libraries.  So, I'll create a filter
for
each library and call it "LIBRARY-Source Files", and then set that one

filter to limit to *FILE and PF-SRC for the file type.   Then I'll
create
a filter pool that might be titled "APPLICATION NAME" and put all of my

"LIBRARY-Source Files" filters in that filter pool.  When I expand
"APPLICATION NAME" I would see my dozen or so, "LIBRARY-Source Files",
the
I could expand the specific library that I need.  This seems to work
for
me, until I get to a source file that has - say a 1,000 or more
members,
then it takes WAY too long to expand even the QRPGSRC or what ever.
Then
I have to have more filters, just for specific groups of member names.

HTH


Jeff Stevens
Mize, Houser & Co. P.A.
913 451 1882
JStevens@xxxxxxxxxxxxxx
--