RE: Ending job has priority 16!?!

This is the result of the new dynamic priority manager in V4R1. If brief: To
prevent CPU starvation and resolve lock conflicts OS/400 may increase the
run priority of jobs without you knowing. This increase will ONLY be shown
in wrksysact. There is no message in the joblog and the dspjob and wrkactjob
screens still show the old priority.

Having said that, I'm surprised that the priority was increased for an
ending job, after all if an ending job is not ending fast enough who cares?.
Unless: Are you using commitment control? Could the ending job have been
rolling back a large commitment control boundary? Once you get above about
5000 records in a boundary you can see the rollback take time.

-Walden

-----Original Message-----
From:   mcsnet!midrange.com!midrange-l-owner@Mcs.Net
[mailto:Rudolf.Wiesmayr@mag.linz.at] On Behalf Of Wiesmayr Rudolf
Sent:   Thursday, January 15, 1998 6:21 AM
To:     'MIDRANGE-L@midrange.com'
Subject:        Ending job has priority 16!?!

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' -

winmail.dat