Re: Job CPU% -- MIDRANGE-L

× 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.

Subject: Re: Job CPU%
From: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
Date: Tue, 26 Mar 2013 16:10:16 -0500
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>

Be Really really really, no really careful with WRKSYSACT. That command takes the user to priority 1. If you push the right set of keys you can cause "interesting results" (read: systems that can become very sick)

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On 3/26/13 3:43 PM, Mike Krebs wrote:

WRKSYSACT we use for trouble shooting. Put in auto-update mode and can see CPU percent for that time slice.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Job CPU% , rob

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.