How much memory is currently paged?

There is a way to determine how much memory is paged.
WRKSYSSTS
Take
Current unprotect used . : 110277 M
Subtract the sum of:
Pool
Size M
5044.38
24317.51
2284.17
14762.66
14454.68
7480.57
or
68343.97
and you get
110277 - 68343.97
=
41933.03
or 41GB paged out.

Then the million dollar question becomes: What does this mean?
Is there an acceptable amount of paging? If so, is it an amount or a
percentage?
Or does this not matter, what really matters is paging and faulting? If
so, how does one address paging and faulting.
- Shift memory from one pool to another.
- Add memory
- Change applications to use less memory
- Terminate staff to reduce workload on system.
- Move applications to other platforms.
- Move back to paper based business from computer based business. (There's
this ancient horror story from our distant past...)
- and on and on and on...

This system is a bit memory constrained at times and shifting memory from
one pool to the next isn't always the answer as it quickly changes from
one pool to the next. For example, WAS startups often jump from hogging
memory in base (where they run) and from interactive (where they are
started from). So please, no plugs for tuning products that are more
responsive than QPFRADJ.
Sure, startups shouldn't be your main concern (unless you're the IBM guy
connecting in remotely at 11pm helping you get WAS stuff configured),
since startups only occur, well, at startup.

Sys Pool Reserved Max ----DB----- --Non-DB--- Act-
Pool Size M Size M Act Fault Pages Fault Pages Wait
1 5044.38 1300.66 +++++ .0 .0 165.4 442.7 .0
2 24317.51 183.91 1880 .0 2.7 2.7 5.4 55527
3 2284.17 .48 28 .0 .0 .0 .0 1090
4 14762.66 .60 1547 .0 .0 6.3 6.3 1254
5 14454.68 .12 157 .0 .0 .0 .0 .0
6 7480.57 4.57 800 .0 .0 .0 .0 26454


Rob Berendt