Re: I/O count differences

On 23 Jan 2013 08:22, RPGLIST wrote:

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,

Seems well enough explained.

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?

Not in I/O counts for the open file for the job, but there are CPU and paging\faulting which account that work, plus the "Access Path Activity Statistics" which track the "Access path logical reads" "Access path physical reads". See the DSPFD TYPE(*MBR) details for the keyed database file member.

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.

Again, no record-level physical I/O.