RE: [WDSCI-L] Profiles, Filter Pools, and Library Lists

["Kelly Cookson" <KCookson@xxxxxxxxxxxx>]

I already need two connections per profile (test machine, production machine). 
I had set up three profiles, one for each of the areas in which I program 
(human resources, accounting, credit) since these areas usually require 
different library lists. That resulted in a total of 6 connections.

Although I spend the majority of my time on a typical day in one area of 
programming, I have realized that I need to carry out small tasks in all three 
areas of programming throughout the day.  Hence, I either need to constantly 
activate and inactivate some profiles, or I need to leave all three profiles 
active. It was a choice of constantly logging back into profile connections or 
constantly scrolling through 6 RSE connections. 

The arrangement I have now lets me stay in one or two connections, reduces 
logins and RSE scrolling, and lets me set up a library list by simply choosing 
a User Action. 

This is all a matter of preference, really. If profiles work for you, great! It 
should probably be viewed as a strength of WDSCi that we can each find a 
different way we prefer to accomplish a task.

Thanks,
Kelly


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx
[mailto:wdsci-l-bounces@xxxxxxxxxxxx]On Behalf Of Vernon Hamberg
Sent: Friday, October 29, 2004 10:51 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Profiles, Filter Pools, and Library Lists


Kelly

I found multiple connections to be a reasonable way to manage library 
lists. You can have multiple connections to the same server under the same 
profile. You probably know how, but here goes - right-click on the 
connection, click on Properties, click on Susbsystems, then on the iSeries 
Commands tab. There you can set the library list for this connection. This 
setting propagates to all subsystems under that connection. You can 
right-click a subsystem, such as iSeries Commands or IFS Files, click on 
Properties, and then on Initial Library List. Making a change here affects 
all other subsystems, although it would appear that you could set it for 
each one, since it is editable in each subsystem. Sigh!

So, if you can have only one profile active at a time (is that why you had 
to jump around?), then using multiple connections might give you what you want.

HTH
Vern

At 09:27 AM 10/29/2004, you wrote:
>Just wanted to share my experience using profiles to manage library lists.
>
>I created three WDSCi profiles. Each profile set up a different library 
>list when its connections were opened. However, I had to jump around 
>between profiles too much during the day, which meant either (1) 
>constantly activating and logging in to the profile connections when 
>needed, or (2) leaving all profiles active, which cluttered my RSE view 
>with multiple connections.
>
>I definitely see how profiles might be useful in other kinds of 
>situations. I like the profiles feature. I just didn't find profiles 
>convenient for this particular use.
>
>So I'm back to one profile. I am now managing library lists in the 
>following way: (1) create User Actions for frequently used library list 
>set-ups, and (2) add a library list filter to each filter pool when the 
>filter pool is created.  The latter puts the library list filter in a 
>handy location.
>
>Thanks,
>Kelly

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