× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Could this have anything do with caching and/or the order of the remote 
connections it that view?

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On 
Behalf Of John Wallroff
Sent: Thursday, March 16, 2006 3:14 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] iSeries Project source. Verify and Outline.

That's a good question... It's also the first thing I checked before asking 
here.

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On 
Behalf Of MWHopkins@xxxxxxxxxxxxxxx
Sent: Thursday, March 16, 2006 2:46 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] iSeries Project source. Verify and Outline.

Are you sure that there isn't an old version of the file in a library that 
is higher in the library list on the dev box connection?

Matt Hopkins 
Sr. Programmer/Analyst 
Web: www.pdpgroupinc.com 
Email: MWHopkins@xxxxxxxxxxxxxxx 
Office: 410-584-0330 
Fax: 410-584-0336 





"John Wallroff" <jwallroff@xxxxxxxxxxxxxxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
03/16/2006 03:40 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc

Fax to

Subject
Re: [WDSCI-L] iSeries Project source.  Verify and Outline.






As far as I can tell all that does is tell WDSCi what connection and 
library to push the source changes to.  The project that I'm working on 
has a PF DDS included that I needed to add a field to.  I did this, pushed 
the PF source to our DEV box and did a CHGPF to change the PF and all 
logical files tied to it.  I have also brought an RPGLE source file into 
the same iSeries project.  The project is still pointed to the DEV box but 
when I update the Outline or try to do a Verify in WDSCi it looks at a LF 
of that PF on our Production box.  The same thing happens if try to do a 
Verify of the program source, I get errors because the new field isn't 
present in the LF because WDSCi is looking at the LF on the Production box 
instead of the Dev box.

Is WDSCi looking at the Production box because it's the first connection 
that's listed in the Remote Systems view?

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] 
On Behalf Of Violaine Batthish
Sent: Thursday, March 16, 2006 2:03 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] iSeries Project source. Verify and Outline.

John,

iSeries projects should use the connection defined in the project:
1) Right click on project and select properties
2) Select iSeries project
3) Select (or create) connection

thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab

You know you've achieved perfection in design, not when you have nothing
more to add, but when you have nothing more to take away. - Antoine de
Saint-Exupéry



wdsci-l-bounces@xxxxxxxxxxxx wrote on 03/16/2006 11:31:15 AM:

> Anyone have any ideas at all here?
>
>
> Where do I define in WDSCi what iSeries connection I want to check
> against when doing things like "Verify" source and "Outline" source on
> source I have in an iSeries project.  We have a Development LPar and a
> Production LPar.  Even though the iSeries project I'm working on is
> pointing to the Dev box when I do a Verify or try to update the Outline
> it is pointing to the Production box.  How/Where do I change this?
>
>
>
>



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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.