OMEGAMON XE for zOS Problem Solving Scenario - Running out of USS Processes
JoeWinterton 110000BXHR Visits (4045)
In the attached PDF we show how OMEGAMON XE for zOS 5.1.0 can prevent a z/OS LPAR from doom by warning the USS Processes pool is close to full.
On slide 2 the e3270ui Situation Event Console workspace alerts me that the SP14 USS Process pool is over 90% full. If it gets to 100% the LPAR is in trouble and may not be able to continue to process work.
On slide 3 you can see that I then went over to look at USS Processes in use of SP14. Who is using most of the 282 processes out of the max of 300?
On slide 4 we see that WAND4 is the user of most of these processes that are not getting freed on SP14. Knowing the WAND4 user - I call the system programmer directly as this is a critical situation that cause the LPAR to go down soon. Actually went up to 96% from 94% while I looked at a few screens. The system programmer is working on configuring a USS server on another LPAR and this work is blocking the SP14 USS work from completing. They stopped the other LPAR work and that freed up SP14 task that took the USS Process pool down to 14% very fast. So in the end SUCCESS !! We saved the SP14 LPAR with very effective alerting of an upcoming issue.
So let the OMEGAMON XE for zOS 5.1.0 product be your watchdog and warn you early of issues.