Peter, Yes, some confusion was caused by terminology: I regard VLF as the manager of the cache and the exploiters as doing 'caching', meaning giving an object to VLF to put it in its cache.
Finally, the first and basic question of this thread was: -can I use VLF trimming statistics as a good measure to determine if my CSVLLA cache is large enough? -If not, what measure does tell me this, besides the LLAFETCH/PGMFETCH measures I get from CSVLLIX1/2? Besides all the information you do not wish to publish, this in my opinion is useful information worth publishing. Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Peter Relson Sent: 30 November, 2014 16:58 To: [email protected] Subject: Re: VLF caching >Now, please put your wisdom in IBM books. I think that most of my post was discussing internal details that are not suitable for documentation (where by documenting them, customers and programmers are allowed to rely on them, which in turn may hamstring future desire to change). If there are particular pieces that would really help customers if we document them, I'll listen to requests for them (which should include at least a hint of how it will help). >>If LLA finds that a module that it had successfully gotten cached no >>longer is deemed worthwhile, it does not tell VLF. >No? Why? Not having been involved in the initial implementation, I'm not sure. Perhaps it was felt that doing so would be overkill, that trimming would do a good enough job such that the overhead of doing the "delminor" was not worth the cycles. It also makes it less flexible -- if there are subsequent fetches, LLA might be able simply to mark its data as "active" and not have to re-cache the module. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
