Core processor utilization Was: Cumulative PTF w/o Technology Refresh -- MIDRANGE-L

Subject: Core processor utilization Was: Cumulative PTF w/o Technology Refresh
From: rob@xxxxxxxxx
Date: Wed, 15 May 2013 14:49:00 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Trying to tie the information available on HMC to that available from
other limited resources. For example, if I display this on my HMC

Processing Units
Minimum: 0.10
Sharing mode: Uncapped
Assigned: 1.25
Weight: 128
Maximum: 7.00
Shared processor pool: DefaultPool (0)

Virtual Processors
Minimum: 1.0
Assigned: 3.0
Maximum: 8.0

What would match this on 5250 or iNav?
I don't see a match using
wrkhdwrsc *prc
wrksysact
wrksyssts

And, short of display/alter/debug, nothing sticks out in SST.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Core processor utilization Was: Cumulative PTF w/o Technology Refresh , Anderson, Kurt
Re: Core processor utilization Was: Cumulative PTF w/o Technology Refresh , Jack Kingsley

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.