×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Kirk Goins wrote:
Don't know If I missed this or not.. what does WRKSYSTS and WRKDSKSYS look
like?
WRKSYSSTS looks like around 51% of the system ASP in use. As to the
whole thing:
% CPU used . . . : 142.0 Auxiliary storage:
% DB capability : 22.6 System ASP . . . . . . : 4516 G
Elapsed time . . : 02:13:41 % system ASP used . . : 51.2921
Jobs in system . : 4316 Total . . . . . . . . : 4516 G
% perm addresses : .445 Current unprotect used : 116164 M
% temp addresses : 14.807 Maximum unprotect . . : 131353 M
Type changes (if allowed), press Enter.
System Pool Reserved Max -----DB----- ---Non-DB---
Pool Size (M) Size (M) Active Fault Pages Fault Pages
1 1687.55 205.52 +++++ .0 .0 57.8 60.1
2 1286.27 120.21 248 205.1 3800 414.2 1021
3 300.00 .00 64 50.2 188.9 106.1 235.9
4 10.00 .00 5 20.9 221.5 11.7 29.7
5 1555.41 .00 172 54.6 744.3 130.1 308.2
6 1874.57 .03 80 86.4 1596 289.2 1343
7 158.94 .05 23 .6 1.1 31.8 60.0
As to what WRKDSKSYS looks like, it looks like:
Command WRKDSKSYS in library *LIBL not found.
If you really meant WRKDSKSTS, it shows 53 drives(!), ranging in
utilization from 49.7% to 53.9%
The box in question is a 550, running 3 LPARs. (53 drives?!?)
--
JHHL
midrange.com
