× 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.



That is exactly what I have been trying to figure out for awhile.  Thanks
for the tutorial!

Aaron Bartell

-----Original Message-----
From: Phil Coulthard [mailto:coulthar@xxxxxxxxxx]
Sent: Tuesday, May 13, 2003 11:21 AM
To: WDSCI-L@xxxxxxxxxxxx
Subject: [WDSCI-L] New Project


Mark asks:

>Here is the scenario that I have. We have, on the same
>iSeries, a production and test environment. I'd like to
>set up a project/perspective (not quite sure of the
>terminology) for each environment complete with it's
>own library list and member filters. When I create a
>new connection, any changes I make to one, duplicates to
>the other.
>Is my quandary clear and is it possible?

Mark, its clear and possible. It is not as intuitive as it can be and
eventually
will be, but here are the steps:
  -> look in the dropdown in the title bar of the Remote Systems view,
        and select the "Show Filter Pools" action.
  -> In each connection, right-click on iSeries Objects to create a new
        filter pool.
  ->Create the filters you want in each filter pool (via right click New
action on
        the pool).
  ->That's it for filters... the trick is filters live in pools, and pools
can be referenced
        by one or more connections. By default they go in the default pool
which is
        always referenced by every connection.
       By creating a new filter pool, it is only referenced by the
connection you
         create it in by default (you can always add a reference to an
existing pool
         if you want to subsequently share the filters in more than one
connection)
    ->As for library list information and such, select the Properties
action on the
        connection, and set the information there via the SubSystems node.
This
        info is per connection.
     ->Once you have connections tailored to your particular scenario, you
can
        create iSeries Projects, one per connection, inheriting that info,
if you like.


Phil Coulthard, STSM, iSeries AD,  IBM Canada Ltd. coulthar@xxxxxxxxxxx
905-413-4076, t/l 969-4076

_______________________________________________
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 thread ...


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.