Exactly what I needed. I was just looking for it one level too high at the
connection instead of the objects.

Thanks for the help and quick response.

-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Brian
Parkins
Sent: Wednesday, February 9, 2022 4:48 PM
To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] Different library lists

Having separate Workspaces may be an overkill. Just set up different
Connection(s) for each project.

Within a given Workspace you can have as many Connections to the same - or
different - IBM i servers as you wish. Each Connection has its own library
list which may be customised:

For each Connection, right-click the OBJECTS subsystem > PROPERTIES >
INITIAL LIBRARY LIST

In addition, this List can be manipulated dynamically:

- Right-click the LIBRARY LIST filter > ADD or CHANGE as required
- With RDi V9.6 you also have a separate Library List view, which is quite
handy

To summarise, the Workspace itself is not associated with any library list;
the Connections defined within the Workspace determine the library list to
be used.

HTH,
Brian.

On 09/02/2022 21:31, smith5646midrange@xxxxxxxxx wrote:
I am working on a few different projects and they need different
library lists for compiles (copybooks, files, etc.). Is there a way
to have a workspace automatically load a specific library list? That
would allow me to create a workspace for each project and switch back
and forth. If not, is there some other way to do this? I'd rather
not manually have to load the library list every time I start a session or
switch projects.



I am currently running V9.5.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2022 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.