PMFJI here, but can you tell us where the rest of this conversation may be located? I found only one message on IBM-MAIN with this subject, from April 22, author Joe Reichmann.
I would be interested to read the whole thread if I could find it. Peter -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of Mike Hochee Sent: Thursday, May 16, 2019 9:56 AM To: [email protected] Subject: Re: Sysadata symbol and literal cross reference record type x’44’ re-post from IBMMAIN Hi Martin, No, I cannot elaborate as I have no additional information, just a presumption. Thank you for the E163 reference. Mike ________________________________ From: IBM Mainframe Assembler List <[email protected]> on behalf of Martin Truebner <[email protected]> Sent: Thursday, May 16, 2019 2:22 AM To: [email protected] Subject: Re: Sysadata symbol and literal cross reference record type x’44’ re-post from IBMMAIN Mike, >> Also, if IBM makes available some diagnostics about instruction cache >> flushes, like cause and location, this might be another option. Can you elaborate on that "if"? Are you saying that there are ways to get more from the hardware than just the counter E163 (*). I do agree that that counter (even in relation to counter B2) does not say much- but typical numbers for your load (i.e. heavy night load when certain programs run) vs. daily online load or numbers from other installations before and after attempts to eliminate the cause of E163. Martin (*) definition of that counter from the book: Counter 163 – A directory write to the Level-1 Instruction cache directory where the returned cache line was sourced from an On-Chip Level-3 cache with intervention. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
