Jim,
With all due respect, most people try to size their system as necessary,
but there are just some jobs that take longer than we would like. File
re-orgs, OPNQRYF, SQL requests, purges and the like take a long time. I
think you are asking for trouble killing these jobs. In the olden days,
killing these types of jobs would leave damage on your system, but IBM has
fixed many of those types of jobs. But please whatever you do, do not kill
my purge program.
Al
Al Barsa, Jr.
Barsa Consulting Group, LLC
400>390
"i" comes before "p", "x" and "z"
e gads
Our system's had more names than Elizabeth Taylor!
914-251-1234
914-251-9406 fax
http://www.barsaconsulting.com
http://www.taatool.com
http://www.as400connection.com
Jim.McLean@farrow
.com
Sent by: To
midrange-l-bounce MIDRANGE-L@xxxxxxxxxxxx
s+barsa=barsacons cc
ulting.com@midran
ge.com Subject
Automatically killing long running
jobs
11/12/2007 11:35
AM
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
Hi Everyone,
I'm looking for a solution to my problem of long running reports. Everyone
once in a while a user gets carried away and submits a very, very large
report to the system. What I would like to do is kill any reports that run
for more than X minutes. These reports run in our reporting
queue/subsystem, so it would be safe to kill any job in that subsystem
that's been running for more that X minutes.
Any ideas on how best to accomplish this? Or am I off the mark in trying
this?
--
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.
As an Amazon Associate we earn from qualifying purchases.