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


  • Subject: RE: Ending job has priority 16!?!
  • From: Neil Palmer <npalmer@xxxxxxxxxxx>
  • Date: Thu, 15 Jan 1998 14:21:33 -0600

I THINK (don't hold me to this) that the system does that internally to
expedite ending the job - especially if it's taking a while to kill it.
Depending on the LOG values set for thos job however, this could cause
it to spend a LONG time producing a massive joblog.  One way to prevent
this when killing a job with ENDJOB is to make sure you limit the # of
log entries produced with the LOGLMT parameter.  Maybe something
reasonable like a couple of hundred entries (if you want to try to see
what's happened if the job may be looping) or just LOGLMT(1) if you
don't care about the joblog.

... Neil Palmer                                     AS/400~~~~~      
... NxTrend Technology - Canada     ____________          ___  ~     
... Thornhill, Ontario,  Canada     |OOOOOOOOOO| ________  o|__||=   
... Phone: (905) 731-9000  x238     |__________|_|______|_|______)   
... Cell.: (416) 565-1682  x238      oo      oo   oo  oo   OOOo=o\   
... Fax:   (905) 731-9202         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
... mailto:NPalmer@NxTrend.com          http://www.NxTrend.com


                -----Original Message-----
                From:   Rudolf.Wiesmayr@mag.linz.at
[SMTP:Rudolf.Wiesmayr@mag.linz.at]
                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' -

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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-Ups:

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.