Ending job has priority 16!?! -- 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.

Hello all!

I just saw it in WrkSysAct:
There is a user job running with priority=16
and consumes pretty much CPU.

But WrkJob option 3 tells: RunPty=50!

And the job is displayed in WrkActJob 
with RunPty=50 and status=*END!

Does anybody know why the system raises priority for a job
in its ending phase?

Is there any official documentation about this?

Regards,
-----------------------------------------------------------------
Dipl.-Ing. Rudolf Wiesmayr   Tel:     +43 - 0732 / 7070 - 1720
Magistrat Linz, ADV/AE       Fax:     +43 - 0732 / 7070 - 1555
Gruberstrasse 40-42          mailto://Rudolf.Wiesmayr@mag.linz.at
A-4041 Linz                  IBMMAIL: at3vs7vs@ibmmail.com
------ http://www.linz.at <<<--- Digital City Linz, Austria -----
- City of Linz: awarded by 'Speyerer Qualitaetswettbewerb 1996' -

application/ms-tnef

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.