× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



RSE under WDSc 5.0

We have 5 various iSeries boxes. I can use the Profile given to me during
set-up and then create Connections to each of the boxes.  This is fine, but
when I create filters, the filter is created the same for each Connection.
Well, this does not really work in all cases because stuff could be in
different libraries/members on each of the different boxes.  So a filter I
set up could apply to one of the boxes, but does not apply to the others.

I can set up multiple Filter Pools, but they get 'added' to every
connection. I did find the "remove reference" option, but that applies to
only that level under the connection. If I remove the reference for the
filter pool under the objects for a connection, it still shows up under the
commands for that connection. I would then have to remove it from there
too.  Should I set up a different Profile each box? Are there any bad
points to doing this?

What are the best practices for setting up multiple iSeries in RSE???

--  THANKS
------------------------------------------------------
Scott P. Johnson
Senior Programmer/Analyst
IBM Certified Specialist - AS/400 RPG Programmer
Highsmith Inc.
W5527 Hwy 106, PO BOX 800
Fort Atkinson, WI 53538-0800
TEL:  920-563-9571                FAX:  920-563-7395
sjohnson@xxxxxxxxxxxxx
www.highsmith.com
------------------------------------------------------


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.