We have a mixture of .Net apps that connect through ODBC and DB2 Connect to an iSeries LPAR that's at V5R4. We also have some batch jobs running natively on the machine (COBOL, RPG, and straight CL mostly). During certain periods of the day, we experience high page faulting and are trying to determine which apps might be causing the problem.
Without purchasing any of the dozens of expensive tools on the market (i.e. iDoctor), is there any way to see the amount of memory being consumed by each job. Most of our jobs are running out of pool 2 and we do see improved performance when we add memory to that pool and simply looking at wrksyssts doesn't help much. We'd like to isolate the problem jobs and see if some modifications can be made to improve performance and reduce unnecessary memory utilization.