Re: Controlling library list in RDi 7.5

This is what I just thought of and started testing. Two connections to the same system, one named Development and one Production, each connection has the necessary library list set.

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of David Wright
Sent: Thursday, July 09, 2009 9:49 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Controlling library list in RDi 7.5

We always setup two connections: one for test and one for production.
The two connections logon with different user ids and different library
lists, and can have different sets of object filters.

Our test ids do not have authority to compile into production, so there
is little risk of accidently compiling into production with the test
connection.


-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Mike Cunningham
Sent: Thursday, July 09, 2009 6:02 AM
To: 'Websphere Development Studio Client for iSeries'
Subject: [WDSCI-L] Controlling library list in RDi 7.5

What's the easiest way to deal with library lists in RDi 7.5? In SEU
programmers default to the development libraries and call a CL to set
the production libraries when ready to compile into production. Then
another CL to go back to development. Or they use EDTLIBL if they need
to setup something out of the ordinary.