×
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.
- The problem of using sql for this task is that there is no way to
handle record lock.
If this is a one time, non critical fix program, I say go with SQL. If
this is on-going and critical process, you will have to put record lock
in consideration.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[
mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Campin
Sent: Thursday, June 21, 2007 1:35 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: SQL Mass Delete Vs. READ/DELETE
<snip>
I would disagree strongly with this statement. Using a loop with an
update file means that each record is read one record at a time, locked,
returned to the program, delete issued or locked must be released and
then repeated again.
Nothing takes more resources on an AS/400 than logical I/O and
especially when you have no buffering.
Huge amount of overhead.
</snip>
midrange.com
