Re: Custom compile from IFS -- WDSCI-L

× 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.

On 4/21/2016 11:16 AM, John Yeung wrote:

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.

Alas, terminology.

An interactive compile uses the server job that RDi has previously
established to execute commands. That job starts when RDi does and
lasts until RDi closes (ish). So, technically speaking, an interactive
compile runs in batch too.

One might consider it 'interactive' in that each developer has a
separate server job. If all hundred of them compile programs
simultaneously, IBM i will process all hundred of them at the same time.
(Leaving work management details aside for the moment).

If the same hundred developers requested the same hundred compiles
simultaneously, and those requests went to a single, common job queue
('batch compile'), they would process one after the other, rather than
all in one go.

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.