|
David, I use filter pools to group my filters by resulting object type. Within a connection I will generally have two standard filter pools. One for source code and another for program objects. Within each filter pool there will be object filters for each source or object library I need in the project. The source object filters list all the source file for a library and the program object filters show all program related objects within a library. Sometimes I will also add a data files filter pool with the same type object filters in it. Can't help with the filter pool reference question. Rick
-----Original Message----- From: wdsci-l-bounces+rick.chevalier=americredit.com@xxxxxxxxxxxx [mailto:wdsci-l-bounces+rick.chevalier=americredit.com@midrang
e.com] On Behalf Of David Foxwell
Sent: Tuesday, January 30, 2007 3:32 AM To: Websphere Development Studio Client for iSeries Subject: [WDSCI-L] Organisation of filters, pools, etc I would like to hear from others as to how they use filters efficiently. I have just stumbled on my own system, and realised that I must have been doing it all wrong up until now. This is roughly how I work, and I would welcome any advice on how to improve the organisation of my RSE : 1. For each job I'm working on, I create a new connection. When I start the connection, a standard CLP that is in every developpement library puts the library list in place. That way, as soon as I start work, my *CURLIB is the development library. 2. When the new connection is created, I can see a filter pool that is common to all connections. I'm not sure about how that works, so any ideas would be great. 3. In this "default" filter pool I have filters based on the *CURLIB. As I have standardised programmes for installing and testing my modifications, I have managed to greatly reduce the number of filters I need to create. Can anyone improve on this ? Can anyone elaborate on the use of filter pools ? With examples ? When I click right + new on iseries objects, under filter pool is "filter pool reference". If I choose this, the menu proposes a list of profiles. What exactly is this filter pool reference? --
Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.
As an Amazon Associate we earn from qualifying purchases.
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.