|
David, I suggest you look at "Profiles" which allow you to group connections, filter pools, user commands, compile commands, and so forth. I have used them to define paired systems (prod system, and development system) that share filters, library lists, etc. Shared filter pools only share within a profile, so I can define common filters over libraries/objects/members that are useful on both prod and dev. just another thing to consider..... <g> Eric -----Original Message----- From: wdsci-l-bounces+edelong=sallybeauty.com@xxxxxxxxxxxx [mailto:wdsci-l-bounces+edelong=sallybeauty.com@xxxxxxxxxxxx]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?
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.