|
What do you mean by the behaviour (oops, that's Cdn spelling :-)) is unchanged? Do you mean after Susan created a new filter and explicitly selected the new pool, the new filter appeared in multiple connections? Or that existing filters still appear in multiple connections? I hope the latter, as the former should be impossible. But when in doubt, go into Show Filter Pools mode, and ensure you don't see the new filter pool in those other connections. If you do, select it there and choose the right click action to remove the reference. All of this has been the same for 4.0, 5.0 and 5.1. As for the appropriate default, we did a lot of debating on this, and it seemed for most it was more intuitive for filters to appear in multiple connections "in general" which we then applied to all filters, including libraries, for better or worse. By the way, with the new release not only will we create the connection-specific filter pool, we'll manage it too, such that deleting the connection will delete the pool. Phil Coulthard, iSeries AD, IBM Canada Ltd. coulthar@xxxxxxxxxxx ----- Forwarded by Phil Coulthard/Toronto/IBM on 12/22/2003 04:38 PM ----- |---------+----------------------------> | | "Jon Paris" | | | <Jon.Paris@Partne| | | r400.com> | | | Sent by: | | | wdsci-l-bounces@m| | | idrange.com | | | | | | | | | 12/22/2003 03:16 | | | PM | | | Please respond to| | | Websphere | | | Development | | | Studio Client for| | | iSeries | |---------+----------------------------> >---------------------------------------------------------------------------------------------------------------------| | | | To: "Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx> | | cc: | | Subject: RE: [WDSCI-L] Library filters | >---------------------------------------------------------------------------------------------------------------------| >> All filters, be they library, object, member, command, job, IFS or local, apply to all server connections by default. Thanks Phil - glad to hear it is changing. I does seem a rather strange choice for the default. I guess it has been there all along and I never noticed before. On Susan's V5.0 system the pool entry appears, but the filter behavior is unchanged. It still appears in both and is deleted in both. Could this be because there were filters already in place before she applied the new setting? Or is it just that way in V5.0? Jon Paris Partner400 www.Partner400.com _______________________________________________
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.