|
You can use WRKSYSACT to find out if this is happening. It is the only command that I know of that shows the actual run priority that a job is currently running with. All other commands show the run priority that was requested when the job started. Charly Jones "Geezer in Gig Harbor" >From: "R. Bruce Hoffman, Jr." <rbruceh@attglobal.net> >From: Richard Jackson <richardjackson@richardjackson.net> > > >I am concerned when the elapsed time for a priority 50 batch job is > >significantly increased when a priority 99 job runs and there are no > >obviously-overloaded components. > > >The only time I know of that this happens is when there is a lock >held by the lower priority job that the higher priority job wants. The >lower priority job will then have its priority >raised in an attempt to release said lock sooner. > >This has been in the system for some time. > ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.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-2025 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.