|
The library list for an RSE connection initially comes from the job description for the user profile that signs on (just like 5250). There are two ways to customize this: 1. Run the various LIBL commands (addlible, etc..) or use corresponding library list actions available on the library list filter. These are dynamic changes that get picked up on the fly but are lost as soon as you disconnect the RSE connection (same as 5250). 2. Set the initial library list properties for the RSE connection (right click on iSeries objects and select "Properties" then click on the "Initial Library List" property page.) These are not dynamic, you must disconnect and reconnect to pick these changes up (just like changing your jobd). Now for the link to CODE Designer. The RSE and CODE tools use different communications layers and therefore each have separate backend jobs (and therefore library lists). However, any library list changes you make using #2 above will carry over to CODE when you launch either CODE Editor or CODE Designer from the RSE. This is a one time thing. If you make changes using #2 and want CODE tools to pick them up then you have to shutdown all the CODE tools, RSE and end any evf* processes - or just reboot :) I know this last bit is a pain, but once you get it setup then you can forget about it. This is also why you can create multiple connections to the same host, so you can setup each with their own library list. Hope this helps. Don Yantzi Technical Release Lead WebSphere Development Studio & WebSphere Development Studio Client for iSeries IBM Toronto Lab Phone: (905) 413-4476 IBM internal: IBMCA(yantzi) - Internet: yantzi@xxxxxxxxxx jstevens@xxxxxxxxxxxxxx Sent by: wdsci-l-bounces@xxxxxxxxxxxx 02/08/2006 09:45 AM Please respond to Websphere Development Studio Client for iSeries To Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx> cc Subject Re: [WDSCI-L] DDS in WDSC I have the same problem with the LIBL also. Jeff Stevens Mize, Houser & Co. P.A. 913 451 1882 JStevens@xxxxxxxxxxxxxx Mark Phippard <markp@xxxxxxxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 02/08/2006 08:31 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] DDS in WDSC wdsci-l-bounces@xxxxxxxxxxxx wrote on 02/08/2006 09:19:15 AM: > It wasn't there in V5 or V4 either, for that matter. > > Is there any chance that it ever will be, or that CODE Designer will take > over the library list of the current RSE connection? > > It's really a pain that I have to start a CODE server in 5250 and launch > Designer from PDM in order to get my library list right. > > If I start it from RSE, it apparently always uses a new CODE server, with > an empty LIBL. > > Unless I'm overlooking some option in RSE and/or CODE of course (any hits > from IBM'ers?) I am not sure why you are having that problem, but when you switch to using TurnOver, if you launch the editor from your TurnOver worklist in WDSC it always sets the library list for you, both in RSE or Code Designer. My understanding of RSE, was that the reason it created its own server connection was so that it could transfer the library list, but maybe it will only transfer the list of libraries you can define in the connection as opposed to whatever it might be currently? Mark _____________________________________________________________________________ Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs. _____________________________________________________________________________
As an Amazon Associate we earn from qualifying purchases.
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.