Yes: On line compiles are prohibited in many higher security environments,
so each job can be monitored and reviewed as needed. Secondly if you are on
a production system and too many compiles are running, you can impact
performance and potentially depending on what you are compiling and where
impact a running application.
In a pure test/development environment I can't think of a reason other than
your coworkers not wanting you to monopolize the CPU..... (not that
compiles are all that hard on the system anymore)
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of John Yeung
Sent: Thursday, April 21, 2016 10:16 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries
Subject: Re: [WDSCI-L] Custom compile from IFS
On Thu, Apr 21, 2016 at 8:45 AM, Paul Bailey <PaulBailey@xxxxxxxxxx> wrote:
I always compile interactively [...]
[...] Can anyone think of good reasons to always compile in batch instead
of interactively?
I always compile in batch, but I only compile from the green screen, so
maybe my views don't translate to an RDi-based workflow.
I guess the primary reason I see for choosing batch over interactive is
responsiveness of the session. If compilation happens to take a while, then
interactive compilation locks up my session. Even if compilation is quick, I
haven't lost anything by compiling in batch. I imagine RDi is threaded so
that it doesn't lock up regardless.
For my personal (PDM-based) workflow, batch also has the advantage that I
can easily find the compile listing by looking at one job's spooled files
instead of wading through the output for various commands. Again, I could
conceive of this not being an issue with RDi.
So, the way I imagine RDi working, it doesn't make a difference whether
compilation is batch or interactive. (From RDi's perspective, I would think
it's all effectively "batch" anyway, in that everything has to be
"submitted" to the i.) In which case, yeah, if interactive has better "event
file characteristics", then go with that.
(I guess it's *conceivable* that you could have lots of developers all
logged into an underpowered i, which is also serving a lot of interactive
users, and maybe in this case if all the developers are busy compiling
stuff, it would be better that they do it in batch?
Maybe?)
John Y.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & 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.
midrange.com
