Re: Editing source

Hi Kevin,

When verifying from an iSeries project, the Error List view should open
your project version of your member.
If you look in the error list, you can see the difference when a project
events file is loaded because the title is:
project -- <connection>lib/file(mbr)

When compiling from iSeries projects (by right clicking on the member,
selecting Remote Actions->Compile->compile_cmd) You should then see the
member pushed to the host (if needed) then the Job Status view appear after
the compile is submitted.  When the job has completed, you can right click
on the job and select Task Actions->Retrieve Errors.  This will download
the events file into the Error List view.  Again the title is different
than when compiling members from RSE:
connection -- job_name
Double clicking in the error list should open the project version.

The only times during compile/verify when you double click and the project
version of the member might not be opened is:
1) you project references are not correctly set and your /COPY members or
Copy books have errors in the error list and are in a different
project/library
2) The /COPY members or Copy books have errors in the error list and have
not yet been downloaded to a project

If you continue to have problems with the remote copy being opened, I
suggest that you contact your IBM support folks for assistance.

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 02/01/2006 06:06:50 AM:

> While in the ISeries Projects perspective you can load source into the
> editor from either your local workspace or directly from the ISeries (if
> you have the Remote System tab open).  Ideally we ONLY want to edit
> source in the workspace to ensure that version control remains intact.
> Changes are then "pushed" in order to compile.
>
> It appears that the best feedback for a compile is achieved by taking
> the compile option from the Remote System tab after having "pushed" the
> changes. If, however, the compile fails and errors are generated the
> natural thing to do is to double click the error(s) to load the editor
> at the line causing the problem.   This seems to load the source from
> the iSeries rather than the workspace causing the following issues:
>
> 1) There seems to be no apparent obvious indicator to tell you that you
> are editing the iSeries source as opposed to the workspace source.
> 2) The temptation (if you are not careful) is to make the change there
> and then (thereby only changing the iSeries source and not the workspace
> source)
> 3) You lose your changes when you (or someone else) pushes the workspace
> version down again.
>
> Clearly I am missing a trick here - there must be a more resilient way
> of working. Any light that can be shed on the subject would be
> gratefully received.
>
>
>
> "NOTICE: The information in this electronic mail transmission is
> intended by CoralTree Systems Ltd for the use of the named
> individuals or entity to which it is directed and may contain
> information that is privileged or otherwise confidential. If you
> have received this electronic mail transmission in error, please
> delete it from your system without copying or forwarding it, and
> notify the sender of the error by reply email or by telephone, so
> that the sender's address records can be corrected."