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



Simon,

FFileA O A E K Disk
You're telling me that's not output only?

And the sentence after the quote I provided is:
"The programmer is expected to override the file or use larger blocks if the default is not appropriate."
But the default _is_ appropriate. It's an output-only specification, and thus should block (barring other reasons for the file not blocking which isn't mentioned in the article).

If it's the K you're referring to in the F-Spec as being an issue, I tried removing it (per an earlier thread response) to no effect. Hwoever, even with the K it's still output-only. I see no way I could read or update that file.

Thanks,

-Kurt


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Simon Coulter
Sent: Monday, June 07, 2010 6:33 PM
To: RPG programming on the IBM i / System i
Subject: Re: RPG Blocked Writes


On 08/06/2010, at 8:22 AM, Kurt Anderson 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/d6738e1cd37e1f33862565c2007cef79?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)."

Read this part again:

"The default for the HLL uses record blocking if opening a file for
output only (write) or input only (read)."

and then compare that with your file specification:

FFileA O A E K Disk

paying particular attention to the use of the word "ONLY" in the
blocking explanation. If that's not clear enough then re-read the
original paragraph (of which you quoted only part)--specifically the
second sentence after the one you think should cause blocking.


Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.