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 brought 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 accounts 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
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact