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



In addition, you can use WRKSYSACT to get a more accurate figures (if you
have performance tools installed).

Regards,

Oliver

> -----Ursprüngliche Nachricht-----
> Von:  Finucci Domenico [SMTP:Domenico.Finucci@Fiditalia.it]
> Gesendet am:  Donnerstag, 21. Juni 2001 15:16
> An:   'MIDRANGE-L@midrange.com'
> Betreff:      R: WRKACTJOB and WRKSYSSTS
> 
> Wich key did you used to refresh ? F5 OR f10 ?
> Having the cursor on the percentage, press F1 while in WrkActJob display:
> you will get an explanation on CPU % and elapsed time.
> 
> Sincerely
> 
> Domenico Finucci
> Fiditalia , Milano, 02- 4301-2494
> 
> 
> -----Messaggio originale-----
> Da: midrange [mailto:midrange.mail@sfmco.com]
> Inviato: giovedě 21 giugno 2001 14.45
> A: MIDRANGE-L
> Oggetto: WRKACTJOB and WRKSYSSTS
> 
> 
> 
> I've got a question about WRKACTJOB....
> 
> We had a situation yesterday where one of our developers noted that the
> system appeared to be sluggish.  When he looked at WRKACTJOB  he noted
> that
> the CPU% was 99.9.  When I looked at the CPU% it was at 53.8.  We both
> were
> using the WRKACTJOB command and we were both refreshing at the same time.
> Does anyone know why the display sessions would be different?  In this
> particular case we had an interactive session that had ended abnormally
> and
> was steadily "eating" CPU%.  On my developers display this particular
> interactive session had 40% of the CPU, where as, on my display it only
> showed this session having 10%.
> 
> The difference was also noted using the WRKSYSSTS command.
> 
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.