|
Oh boy... <copy> The Set.., Read requires two fetches. The Chain one. </copy> Not true.... Time to get out your RPG manuals... SetLL accesses the file's access path, to position RPG's cursor. No data is fetched by this opcode. Read and its variants fetch data, and bump the cursor. Chain is a combination of a SetLL and ReadE, though there are optimizations to allow CHAIN to perform better than the separate opcodes. Chain does not bump the program's cursor. Now, here's an interesting article that probably offers more performance gain than the old chain/setll question. http://www-912.ibm.com/s_dir/slkbase.NSF/0/d6738e1cd37e1f33862565c2007cef79?OpenDocument The implication is that poor management of record blocking can adversely effect performance. Eric
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.