|
Michael, The CODE comm layer does not support the concept of an initial command for a server definition so this doesn't carry over from the RSE. Once you are in the CODE tools you can switch to a command shell and run a command. 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 MichaelQuigley@xxxxxxxxxx Sent by: wdsci-l-bounces@xxxxxxxxxxxx 02/10/2006 08:18 AM Please respond to Websphere Development Studio Client for iSeries To wdsci-l@xxxxxxxxxxxx cc Subject Re: [WDSCI-L] DDS in WDSC Don, Is this true only when you specify the inidividual libraries on the "Initial Library List" properties page? We have a utility which sets our library lists using a single command. Everything works great in RSE, but I *NEVER* get can get referenced fields to resolve correctly unless the file they resolve to is my current library. This is one of my challenges getting my developers to migrate to the workbench from PDM, SEU, & SDA. (That and finding SQL errors in the source.) Thanks, Michael Quigley AS/400 Programming Coordinator The Way International www.TheWay.org Original message: ------------------------------ Don Yantzi <yantzi@xxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 08/02/2006 19:06 Subject Re: [WDSCI-L] DDS in WDSC 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
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.