Re: Interactive SQL faster than Batch SQL?

fkany@xxxxxxxxxxxxxxxxxx wrote:
> When I submit an SBMJOB an SQL RPG program, it takes almost an hour to
> process.  When I manually run the SQL statements using STRSQL, the
> processing takes about 10 minutes.

Interactive jobs run at a much higher priority than batch jobs.

The theory is: Interactive jobs need to run very fast while they are
running, but a majority of their time (CPU wise) is spent waiting for a
user to respond.  Thus they run fast for very short periods of time.

A batch job, on the other hand, needs to have systems resources for a
longer period of time, but it doesn't need to run as fast because a user
isn't sitting behind a screen waiting for a response.

There's more too it, but I think that's a pretty reasonable summary.

david


-- 
David Gibbs
david@xxxxxxxxxxxx

Receipt of this message does not grant you permission to send me
Unsolicited Commercial Email