RE: RPG Blocked Writes

Before I drop this, and in defense of my own statements: UNIQUE will
*always* cause this effect. Other circumstances *may* cause the effect.
Note that I didn't promise that taking UNIQUE away will bring the desired
result. What I did say was that you will never get the desired results if
UNIQUE is involved. It's not fair to try to turn one's statements around in
any context.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"There are so many things that we wish we had done yesterday, so few things
that we feel like doing today."
-- Mignon McLaughlin

Actually, in some circumstances, it is whether there are any keys, if
I'm reading the SEQONLY info right in Database Programming manual.

On 6/7/2010 6:05 PM, Dennis Lovelady wrote:

It is the UNIQUE constraint that causes this effect.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"The efficiency of our criminal jury system is only marred by the

difficulty

of finding twelve men every day who don't know anything and can't

read."

-- Mark Twain

Also - is it unique keys, or any keys? I'm guessing any, but I

thought

I'd verify.

Thanks,
Kurt

Are there unique keys on the table? That will change it to single
record
I/O.

On Mon, Jun 7, 2010 at 4:22 PM, Kurt Anderson
<kurt.anderson@xxxxxxxxxxxxxx>wrote:

I have a file defined in a program as:

FFileA O A E K Disk

From my understanding, writes to this file should be blocked.

However

when I look at the I/O for the job, the I/O count and the RRN is

always

equal. For comparison, reading a file that's blocked has a lower

I/O

count

than the current RRN.

Is this a matter of me not understanding the I/O screen (when

looking

at

the job as it is running), or is this file actually writing a

single

record

at a time?

According to this document, I feel that these writes should be

blocked.

https://www-

912.ibm.com/s_dir/slkbase.NSF/1ac66549a21402188625680b0002037e/d6738e1c

d37e1f33862565c2007cef79?OpenDocument

"All high-level language programs (HLLs) use blocking at certain

times and

use single record I/O at other times, based on program

specifications.

Because blocking takes less system resources to perform a single

I/O,

a

program that blocks performs better and uses less system resources.

The

default for the HLL uses record blocking if opening a file for

output

only

(write) or input only (read)."

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.