We just installed Sysview into a new production lpar last weekend and are now seeing high real storage in SYSVUSER. This system is in a plex that has other SYSVIEW & SYSVUSER tasks running. How do we diagnose this?
Release : 15.0
Component : SYSVIEW
Check to see if it can be determined who/what is using the storage:
- Enter command USERS;SELECT JOBNAME = SYSVUSER;SORT T-STG D
Scroll right to the STG fields. Fields G-STG, A-STG and B-STG may need to be sorted on as well.
Then for any high user, use the line command L next to that user to look at their LISTLOG in order to see what they are doing.
For SYSVUSER use a similar command:
ASADMIN;SELECT JOBNAME = SYSVUSER;SORT T-STG D
If there is nothing obvious, and a support case is needed, please collect the following documentation:
1.) Perform the following commands:
Note: Terse the capture dataset just created before sending into the case in .bin format. Again, if the storage continues to climb, please do the same sequence above and send the new capture so that the two may be compared.
2.) Take a console dump of the SYSVUSER address space during the high storage.
3.) The following information will also be helpful in diagnosing the case: