RE: Terminating an idle batch job

["Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx>]

Jozsef Petrovszki wrote a tip on job status monitoring for Search400 a while
back that could probably be modified to fit your situation:

http://search400.techtarget.com/tip/1,289483,sid3_gci755877,00.html?FromTaxo
nomy=%2Fpr%2F2f8

I would force the offending jobs into one or two specific subsystems and
just monitor those, I'd hate to globally shut down any batch job that
appeared inactive.

Regards,

Scott Ingvaldson
AS/400 System Administrator
GuideOne Insurance Group

-----Original Message-----
date: Wed, 14 Jan 2004 21:12:39 -0600
from: "trevor perry" <trevorp@xxxxxxxxxxxxxxxx>
subject: Re: Terminating an idle batch job

Yes - waiting jobs. Possibly all of the below - MSGW is the most common.

It does not make a difference - if the job has not used any resources in a
given period of time, I want to the job to end. There is no issue here with
terminating in the middle of a process.

----- Original Message ----- 
Subject: RE: Terminating an idle batch job


> What do you mean by an idle batch job?  What are your batch jobs waiting
on?
> Are you talking about failed jobs with error messages on QSYSOPR?  I can't
> imagine an idle job where the code has not been specifically written to
wait
> on some sort of logic (monitoring a message queue or data queue, or in a
> wait or DLYJOB loop...)
>
> -Jim
>
> James P. Damato
> Manager - Technical Administration
> Dollar General Corporation
   
This message and accompanying documents are covered by the Electronic
Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains information
intended for the specified individual(s) only. This information is
confidential. If you are not the intended recipient or an agent responsible
for delivering it to the intended recipient, you are hereby notified that
you have received this document in error and that any review, dissemination,
copying, or the taking of any action based on the contents of this
information is strictly prohibited. If you have received this communication
in error, please notify us immediately by e-mail, and delete the original
message.