|
Larry Bolhuis wrote: > > VENU, > > This then is an extension to my earlier reply to your earlier > question. > > You have correctly realized that paging is a potential problem (Which > you would probably get if you blocked 32K!) Realistically the file size > should not affect the blocking size. Record length does have an affect > as you realize since bigger records consume more memory. > If we are running a machine with approx 380 mb in the pool where the job is running alone would we still get paging problems ? What is the guideline for this? I remember reading an article some time back about "encouraging" the 400 to cache particular files. Is this still available or is the system doing this automatically now? We have 512 mb and overnight there are only spool writers and server jobs active on the system. John Hall Home Sales Co. +--- | 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.