RE: Why do people set up their batch submission defaults to run multiple batch jobs at the same time?

Lukas is right though.

His primary point was that if the application expects to run single threaded
it should ensure it or program against those situations where a second
instance starts.

That's not 'idealized' it's what the application has been designed to
expect.

Regards
Evan Harris


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of sjl
Sent: Friday, 7 May 2010 10:42 a.m.
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Why do people set up their batch submission defaults to run
multiple batch jobs at the same time?

Lukas -

No offense intended, but life in your idealized world is not as easy as it
is in the real world. Most AS/400 - iSeries - System i - IBM i shops are
running code that was written over 20 years ago, and have no intention of
'fixing' it to match your conception of 'right'.

- sjl


Lukas wrote:
No. Proper program logic should ensure that something like this can't
be destructive - running the same job twice should result in a "job x
is already running" message. This can be achieved by proper locking.
Forcing a single-batch job to fix problems in the application logic..
Well, it works - but it's a workaround, not a proper solution.

What can be a reason for running only a single batch job can be
performance, but this is going to be less and less of an issue...