|
Within RSE, how do you change it to compile Interactively versus Batch? Mike Tuckman Systems Engineer TNT Logistics North America Office: (904) 928-1516 Pager: (877) 291-0016 Text Page: 8772910016@xxxxxxxxxxxxxxxx |---------+----------------------------> | | "Mark Phippard" | | | <MarkP@softlandin| | | g.com> | | | Sent by: | | | wdsci-l-bounces@m| | | idrange.com | | | | | | | | | 09/04/2003 02:06 | | | PM | | | Please respond to| | | Websphere | | | Development | | | Studio Client for| | | iSeries | | | | |---------+----------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx> | | cc: | | Fax to: | | Subject: Re: [WDSCI-L] WDSCi problem - iSeries Error List rarely updates | >------------------------------------------------------------------------------------------------------------------------------| When using TurnOver, we never bring back the compile results automatically on submitted jobs, only interactive. This is because the compile framework in 5.0 only supports a single compile, in terms of feedback, and we wanted our compile process to handle multiples. So what we did instead is we added an option in our Tools menu to let you manually bring back the compile results when the job ends. Tools -> Show compile results in Error List. This goes out and pulls in the results in the same view. When you run the compile interactive we can do this automatically at the end of the process because we know when it completes. I am not sure why it wouldn't work from RSE except that it can be tricky to initiate a connection from the iSeries back to the PC. I know they store something in the IFS in your home folder to help this process work. Mark
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.