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

[Vernon Hamberg <vhamberg@xxxxxxxxxxx>]

Jeff

I don't think they are related, so the answer is no, AFAIK. Same word but 
totally different contexts. Besides, a subsystem on the 400 does not have a 
library list, only jobs.

HTH
Vern

At 12:06 PM 10/29/2004, you wrote:
> Vern,
>
> Does changing the initial library list on the sub-system in WDSC effect
> the sub-system running on the iSeries at all?
>
> TIA
>
> Jeff Stevens
> Mize, Houser & Co. P.A.
> 913 451 1882
> JStevens@xxxxxxxxxxxxxx
>
> Vernon Hamberg <vhamberg@xxxxxxxxxxx>
> Sent by: wdsci-l-bounces@xxxxxxxxxxxx
> 10/29/2004 10:50 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] 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