|
midrange.com
After you push your changes to the iSeries you can invoke a compile
directly from the iSeries Projects Navigator instead of using RSE's
compile. This will submit a batch job or run immediately depending on your
preference setting for compiles. If a job is submitted you can track it in
the jobs list and when it completes you can retrieve the errors. Errors are
reported for the compile in the error list. When you double-click on these
they should bring up the editor for the local iseries project member rather
than its remote counterpart.
_______________________
David Dykstal
david_dykstal@xxxxxxxxxx
"Kevin Turner"
<kevin.turner@cor
altree.co.uk> To
Sent by: <wdsci-l@xxxxxxxxxxxx>
wdsci-l-bounces@m cc
idrange.com
Subject
[WDSCI-L] Editing source
02/01/2006 05:06
AM
Please respond to
Websphere
Development
Studio Client for
iSeries
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."
--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.
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.
