|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Hi Kaare, This is not an answer, but what difference to your processing will knowing the answer make? This may give a clue or an outside-the-box thought to someone. Regards, Kevin Wright. > -----Original Message----- > From: Kaare Plesner, SOSY A/S [mailto:kaaple@attglobal.net] > Sent: Thursday, 25 July 2002 16:33 > To: MI400@midrange.com > Subject: [MI400] What is main memory resident? > > > I have a case where I need to know if a bunch of records from > a data base > resides in main memory when I want to access them. I can > indirectly make > intelligent guesses by checking if there are any physical reads when I > access these records, but I would like to actually verify > this. I am looking > for something like the good old mainframe dump of a given > part of storage. > > (I know (and agree) that the "Single level storage" > philosophy should mean > that you normally wouldn't and shouldn't care, since OS/400 > brings into > memory what you need and when you need it.) > > Can anyone assist? - could be some MI code, but an existing > OS/400 tool that > I have overlooked might be easier. > > Kaare Plesner I SOSY A/S > mailto:kp@sosy.dk I DK-2730 Herlev > I Denmark > > SOSY A/S - an IBM Business Partner > Meet us at http://www.sosy.dk/ > > _______________________________________________ > This is the MI Programming on the AS400 / iSeries (MI400) mailing list > To post a message email: MI400@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/mi400 > or email: MI400-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/mi400. >
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.