×
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.
Have you checked the compile listing for messages regarding how it may have chosen to access the file.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Kurt Anderson
Sent: Tuesday, 8 June 2010 10:23 a.m.
To: 'RPG programming on the IBM i / System i'
Subject: RPG Blocked Writes
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)."
Thanks,
Kurt Anderson
Sr. Programmer/Analyst
CustomCall Data Systems
As an Amazon Associate we earn from qualifying purchases.
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.