I undestand that, I guess what I'm trying to determine how to evaluate the
fact that its still taking resources and time (as minute as it may be) to
spin through the disk.
The system uses the index only on a no-hit. Never touches the data at all.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of RPGLIST
Sent: Wednesday, January 23, 2013 10:23 AM
To: midrange-l@xxxxxxxxxxxx
Subject: I/O count differences
I need an explanation on this if someone would be so kind.
When I chain to a file with a key and get a hit, I fully expect the I/O
count to increase by 1, even though it is sort of doing a SETLL and then a
READE within the chain process. However, whenever it doesn't find a
record it shows no I/O count.
I understand that since it didn't find a record it brough nothing back
from the disk and therefore didn't increase the I/O count, but it
certainly used resources to spin all the way through that drive disk....Is
there anywhere that the system accoutns for this in the statistics?
I see the same results when performing a SETLL, If %Equal, actually even
if there is a hit I don't see an I/O count until the READE statement.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
