SETOBJACC & seeing it work in a job

I'm just starting to use SETOBJACC b/c we have some heavy file reads that I'd like to move into memory.

I know there's the job log entry saying that the files were moved into memory, but is there any way to see that the job is utilizing the memory the file was loaded into? Specifically I was wondering if the Display Open Files screen when looking at a job would show no I/O if it was actually using memory - or does that page not care if the I/O is against disk or memory? Is there any indicator that the job is using it, other than a performance comparison?

I'm new to SETOBJACC, and have been using the two following links as guidelines (although one is an article from 1994).
http://www-01.ibm.com/support/docview.wss?uid=nas1dc0a2297bdaefddb86256d6c0069907f
http://www.mcpressonline.com/index2.php?option=com_content&do_pdf=1&id=5076

From the 1994 article:

"Next, you need to locate additional memory for this pool, which is currently set to 100KB. You'll need to take the memory for your new storage pool from one of the existing pools. Using the Work with System Status (WRKSYSSTS) command, you can view all pools in the system and change their memory allocations. Any pool in which the fault rate (DB and non-DB) is constantly less than 10 faults per second indicates the pool has too much memory allocated. Even if the faults for a particular pool appear high, you may be able to reallocate some memory. You can safely reduce the memory allocated to a pool if adding or subtracting memory doesn't affect the fault rate. Memory removed from any pool is automatically added to the *BASE pool. You can now increase the DATAPOOL memory size by the amount of excess memory removed from the other pools plus any excess memory in *BASE."



I'm at v5r4, and the smallest pool size is now 256k. I'm curious if the bit about 10 faults per second has changed as well as a guideline.



Our System pool 3 had 194mb, none reserved, with a fault per second of .1. If I want to grab 70mb, I would simply lower the System Pool 3 size, which puts it in base, and once I set up my own pool with 70mb of memory, it removes it from base? Our *Base has around 664mb available. The job is using *Base and when I loaded the files in, 664mb was the first unused number. Do I really need to reduce System pool 3 if *Base has that much?



I appreciate any input.



Thanks,

Kurt Anderson

Sr. Programmer/Analyst

CustomCall Data Systems