|
midrange.com
Sorry guys...
Had a couple of slips on the keyboard when typing my last e-mail!!!
It should be:
"If you UN-checked the "Only create filter in this connection" box you will
see
it (and can use it) in all your connections."
And:
Also here there is a check box for "Only create filter in this connection",
which I can UN-check if I want this to be available in other connections!
/Frank
frank.broome@ibs.
net
Sent by: To
wdsci-l-bounces@m Websphere Development Studio Client
idrange.com for iSeries <wdsci-l@xxxxxxxxxxxx>
cc
2005-01-18 09:21 Subject
Re: [WDSCI-L] Filter pool &
Signature settings
Please respond to
Websphere
Development
Studio Client for
iSeries
<wdsci-l@midrange
.com>
Hi all,
I just wanted to say that I do NOT have "Show filter pools" checked, the
reason is that I don't like the appearance of it but I can still get what I
want!
E.g.
1. Select a connection in RSE where you want to apply this filter
2. Create a library filter by clicking on "Work with libraries" (You can of
course choose to create any type of filter library, object or member)
3. Enter a library name
4. Give the filter a name
5. If you want this filter to ONLY be shown in the particular connection
check the "Only create filter in this connection" box
6. Click "Finish"
The filter will now be shown only in the connection where you created it.
If you checked the "Only create filter in this connection" box you will see
it (and can use it) in all your connections.
Subsequently if you delete the filter in one connection, it'll be deleted
in all others.
This also applies to iSeries commands.
E.g. I have created a number of commands that sets up my library lists
differently dependant of what I want to do.
Also here there is a check box for "Only create filter in this connection",
which I can check if I want this to be available in other connections!
NOTE! This is valid from 5.1.2 and onwards in previous versions, if I
remember correctly, you could not create filters for a single connection.
Or maybe you could if you had the "Show filter pools" box checked!
Hope this helps!
/Frank
Don Yantzi
<yantzi@xxxxxxxxx
m> To
Sent by: Websphere Development Studio Client
wdsci-l-bounces@m for iSeries <wdsci-l@xxxxxxxxxxxx>
idrange.com cc
Subject
2005-01-18 04:57 Re: [WDSCI-L] Filter pool &
Signature settings
Please respond to
Websphere
Development
Studio Client for
iSeries
<wdsci-l@midrange
.com>
Let me see if I can shed some light here...
The RSE actually stores filters inside of filter pools. Filter pools are
not owned by any specific connection, instead connections can reference a
filter pool (so multiple connections can reference the same filter pool,
or a single connection can reference a filter pool.) Since filter pools
are more of an advanced topic we decided not to show them when you
initially start WDSc and the default behaviour is to have a single filter
pool that is referenced by all connections. Any filters you define get
created into this default filter pool. That is why you see your filters
under each connection.
So, to do more customization you need to turn showing filter pools on
(click the drop down menu in the Remote Systems view (the upside down
triangle) and select "Show Filter Pools". You can now right click on the
subsystems and create new filter pools and filter pool references. You
can then right click on a filter pool and create a new filter inside of
it.
You should now be able to customize your filters the way you want. Give
this a try and let us know if you think there are ways you would like to
setup your filters but still can't.
Don Yantzi
Technical Release Lead
WebSphere Development Studio &
WebSphere Development Studio Client for iSeries
IBM Toronto Lab
Phone: (905) 413-4476
IBM internal: IBMCA(yantzi) - Internet: yantzi@xxxxxxxxxx
jag@xxxxxxxxxxxxxxxx
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
01/17/2005 01:10 PM
Please respond to
Websphere Development Studio Client for iSeries
To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc
Subject
[WDSCI-L] Filter pool & Signature settings
My challenge, is to have the same spec, and as well as use the same filter
name in different connection, RSE does not allow that.
vhamberg@comcast.
net To: Websphere
Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
Sent by: cc:
wdsci-l-bounces@m Subject: Re: [WDSCI-L]
Filter pool & Signature settings
idrange.com
01/17/2005 11:36
AM
Please respond to
Websphere
Development
Studio Client for
iSeries
In 5.1.2 you can say to create a filter only in the connection you are in.
Does this let you use the same name but a different specification? The
default when creating filters is to have the filter in all connections,
but
then it has the same specs.
HTH
Vern
-------------- Original message --------------
>
>
>
>
> I just noticed today, that I will not be able to create a filter of same
> name in other connections (we have 3 LPAR box Live/Dev/Test). Is there
any
> settings which will override them.
>
> Moreover in regards to adding signatures to changed lines (Mod marker),
we
> have an ERP, which is heavily modified , could I suggest, it will be
great,
> if we could suggest the column# beginning instead. I feel this would
give
> higher flexibility and as well as preserve the original mod marker.
>
>
> Thanks
> Jag
>
>
>
>
>
> -=- A. Schulman Inc. Email Disclaimer -=-
>
> The content(s) of this e-mail and attachment(s) are confidential, may be
> legally privileged and is for the use of the intended recipient only.
> Access, disclosure, copying, distribution or reliance on any of it by
> anyone else is prohibited. If received in error, please delete and
e-mail
> confirmation to the sender.
>
> A. Schulman Inc. does not guarantee that the information sent and/or
> received by or with this e-mail is correct and does not accept any
> liability for damages related thereto.
>
> --
> This is the Websphere Development Studio Client for 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.
--
This is the Websphere Development Studio Client for 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.
--
This is the Websphere Development Studio Client for 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.
--
This is the Websphere Development Studio Client for 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.
--
This is the Websphere Development Studio Client for 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.
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.
