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


  1.  Home
  2. MIDRANGE-L
  3. August 2013

Re: ENDSBS *ALL in a batch job

On 8/13/2013 3:44 PM, rob@xxxxxxxxx wrote:
ENDJOBABN requires that I wait 10 minutes after running ENDJOB *IMMED.

ENDSBS *ALL *CNTRLD DELAY(120) says try killing all jobs controlled for
two minutes. If they are still running after two minutes then try to kill
those jobs with *IMMED.

So, I need to wait a minimum of 12 minutes after running ENDSBS *ALL
*CNTRLD DELAY(120) before running ENDJOBABN on any job, correct?

Looks right. The catch is that you can detect the need for ENDJOBABN
before you can handle it.

00.00 UPS pgm: ENDSBS *ALL DELAY(120)
00.00 UPS pgm: DLYJOB 120
00.00 OS: start killing jobs
02.00 OS: JOB X will not die
02.00 UPS pgm: wake up and detect rogue job
02.00 /* must wait 10 minutes to be eligible for ENDJOBABN */
02.00 UPS pgm: DLYJOB 600
12.00 UPS pgm: Wake up and ENDJOBABN

--buck

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
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.