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



When you create a User Action to set up a library list, what do you put in the 
command line? I would like a user action to add several and possibly remove a 
couple of entries from the library list. What would the command look like?

Thanks,
Kelly

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of
jstevens@xxxxxxxxxxxxxx
Sent: Friday, October 22, 2004 8:59 AM
To: Websphere Development Studio Client for iSeries
Subject: RE: [WDSCI-L] Filter Pools


I just use one profile and one connection. But I have user actions setup 
for each type of environment (in my case each client) that I want to work 
in.  I expand the library list folder, then right click, user actions, and 
"Set LIBL for XXXX client".


Jeff Stevens
Mize, Houser & Co. P.A.
913 451 1882
JStevens@xxxxxxxxxxxxxx





"Kelly Cookson" <KCookson@xxxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
10/22/2004 08:10 AM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
RE: [WDSCI-L] Filter Pools






I think I may switch from using multiple profiles to using a single 
profile with multiple connections, as you have done, Michael. The profiles 
idea works. And I like the fact that when a profile is not active, its 
connections are no longer visible. But I could define all my connections 
in one profile and use the 'Go Into' menu option to hide everything except 
the particular connection with which I am working.  It seems simpler to 
make multiple connections without making the extra profiles.

Thanks,
Kelly

 


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of
MichaelQuigley@xxxxxxxxxx
Sent: Friday, October 22, 2004 7:56 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Filter Pools


Profiles aren't really the place that controls the library list.  Library 
lists are set at the connection.  (i.e., You set the library list you want 

on the under the 'Subsystems' branch of the connection properties -- then 
under the 'iSeries Commands' tab.)  You can define a different set of 
library lists (and the current library) for each connection within a 
profile and you can define as many connections as you need under one 
profile.  I currently have 8 connections defined under my one profile and 
each has it's own library lists and filter pool(s) so that I can work with 

the appropriate source and objects related to that connection.  For my 
use, I also have a general filter pool (available to every connection) 
which contains filters to source and objects common to all my areas of 
responsibility.

Michael Quigley
AS/400 Programming Coordinator
The Way International
www. TheWay.org

------Original Message-----


date: Thu, 21 Oct 2004 09:58:55 -0500
from: "Kelly Cookson" <KCookson@xxxxxx>
subject: RE: [WDSCI-L] Filter Pools

Well, I was able to achieve something close to what I wanted. I tend to 
create filters by programming project (i.e., one filter contains all the 
COBOL, CL and DDS source files required for a particular application).  I 
have grouped filters for Human Resources applications into a single HR 
filter pool. The filters in my HR filter pool tend to require the same 
library list. 

So now I have an HR profile, which I made by copying my current profile. I 

modified the connection names in my HR profile so I know clearly which 
profile connection I am using. I also modified the connections in my HR 
profile to open with the desired library list for HR projects. It's pretty 

easy to toggle the profile on and off. 

Let me see how much I like/use this arrangement.

Thanks,
Kelly



-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Cary Phillips
Sent: Thursday, October 21, 2004 9:38 AM
To: 'Websphere Development Studio Client for iSeries'
Subject: RE: [WDSCI-L] Filter Pools


I might be wrong, but I believe filters and library lists are controlled 
at
the profile level.  So if you can create a profile for each library list 
you
need and then create the filters within the appropriate profile.  You can
have multiple profiles active at the same time.

Hope this helps,
Cary 

          .          .          .

          .          .          .

          .          .          .

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

Follow-Ups:

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.