|
F5 will not reset stats accumulated over time. Pressing F10 will reset these internal averages, so that current workload is displayed as opposed to average workload over a period of time. Eric DeLong Sally Beauty Company MIS-Sr. Programmer/Analyst 940-898-7863 or ext. 1863 -----Original Message----- From: midrange [mailto:midrange.mail@sfmco.com] Sent: Thursday, June 21, 2001 8:45 AM To: MIDRANGE-L@midrange.com Subject: RE: WRKACTJOB and WRKSYSSTS we were both using f5 to refresh -----Original Message----- From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com]On Behalf Of Finucci Domenico Sent: Thursday, June 21, 2001 8:16 AM To: 'MIDRANGE-L@midrange.com' Subject: 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 +--- +--- | 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 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.