|
At 01:51 PM 2/27/01 +0100, you wrote: >Al wrote: > > > > If I did a RGZPFM, I'd remove the members from the file's logicals >before >.. > > Clearly this will have positive performance implications if you have any > > multi-record format logicals, or LF joins. > >Why? >In all practical context I have found that > o Multi-record format logicals are the same as old RPF Matching record > o LF join is the same as RPG CHAIN >except of cause that it's more fool-proof and needs less coding >In other words: Theese two constructions have the overhead connected to >the access time (millisecond), rather than to the build/maintain time Because there will be seize/lock contention on two files simultaneously. By removing them first, particularly if you were reorging multiple files in one pass (multiple executions of the RGZPFM) command, you could minimize additional locking. We did some benchmarking of this late in the life of the System/38 CPF R08M01, PC F, and proved this conclusively. The files were clearly much smaller then, but then again was both the CPU speed and the DASD speed. Al +--------------------------------------------------+ | Please do not send private mail to this address. | | Private mail should go to barsa@ibm.net. | +--------------------------------------------------+ Al Barsa, Jr. - Account for Midrange-L Barsa Consulting Group, LLC. 400 > 390 Phone: 914-251-1234 Fax: 914-251-9406 http://www.barsaconsulting.com http://www.taatool.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.