Re: Terminating an idle batch job

[pam@xxxxxxxxxxxxx]

In the Lawson case, it sounds like the batch jobs are performing a useful 
function. They are not idle, they are waiting for the next task. They 
should be left alone. Your customer would be in a stronger position to 
defend them if you could identify what function each job is performing. As 
for the company policy itself, I suspect it's either being defined or 
communicated poorly. I would expect terminating idle jobs applies only to 
interactive sessions going unattended, which constitutes a security risk. 

For the Baan case, you've got a porfolio of options from the others about 
how to address that.

Good luck with both.




"trevor perry" <trevorp@xxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/15/2004 11:40 AM
Please respond to Midrange Systems Technical Discussion

 
        To:     <midrange-l@xxxxxxxxxxxx>
        cc: 
        Subject:        Re: Terminating an idle batch job


Thanks for everyone's help, I appreciate all the responses..

This started out because a customer has Lawson - they have batch jobs 
which
are used to connect to a client. Company policy dictates that if a job is
idle for a period of time, it should be ended. These batch jobs are in 
some
wait state - where they are waiting for a client request. I do not know 
any
more detail than that. I do not have the CL and I cannot retrieve it. 
Lawson
do not have a way to end these jobs - even with some cancel message (of
course they should).

Then, I have another customer with some jobs on the system that are
connected to a Baan client. These jobs become disconnected from the 
client,
and need to be ended if they are disconnected. Although I may have another
solution, I thought this might also be solved in the same manner.

I did not mean to send anyone off into solving a specific problem, so I 
was
not specific in my request - I was looking for a generic solution to end
batch jobs which are sitting idle.

So far, the ones that seem to have the most potential have been:
Management Central job monitor (Richard )
ROBOT command CNLIDLEJOB (off list)
Roll your own (several)

Thanks,
Trevor


----- Original Message ----- 
From: "Ron Harvey" <ron.harvey2@xxxxxxxxxxx>
Subject: Terminating an idle batch job


> Trevor,
>
> If the programs are coded to delay when an EOF on a read (I've seen many
software packages do this) and you don't have source code, I know of no 
way
to end the job inside the program. And the program will just sit there and
not end by itself, so anything in the SBMJOB won't help.
>
> The only option I can think of is the 'ol ENDJOB *IMMED.
>
> Ron

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.