I am not so sure that would help. Since the process is hung on the network, it may not be getting CPU time.
just my two cents.
But, it would be very simple to write a job to monitor another job.
Just have the MONITOR job do a SHOWJOB JOB=
Pause 30 minutes and do it again.abort if necessary
-Craig
On Wednesday, May 1, 2019, 6:36:23 AM PDT, Ron Horner <[log in to unmask]> wrote:
There is a ";time=<cpusec>" on the job card that could help. Review the help text in the "job" command.
Ron Horner, Owner
Horner Consulting & Publishing LLC
7114 97th Avenue, Kenosha, WI 53142
(847) 337-2777
"Work quickly, keep the tools unlocked, work whenever."
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf Of John Sommer
Sent: Wednesday, May 01, 2019 7:41 AM
To: [log in to unmask]
Subject: Monitor HP3000 FTP Job
All,
On occasion, we have a FTP job that gets "stuck" every now when it loses its connection to an external server. The job just hangs and stays resident when that happens. It remains running until someone (me) comes in early the next day to discover that all of the nightly jobs are still waiting to run.
Is there a way to have the job monitor itself?If it runs longer than 30 minutes, then it will abort itself.Or maybe there is a utility that monitors jobs?I know there are utilities than monitor sessions.
We do have MPEX, so lots of power there.
Thoughts?
Regards,John
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|