HP3000-L Archives

March 2005, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Bruce Collins <[log in to unmask]>
Reply To:
Bruce Collins <[log in to unmask]>
Date:
Wed, 23 Mar 2005 11:47:18 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (43 lines)
If your pause is of the form:

PAUSE JOB=jobname;EXIST

It sounds like you are out of luck if the job restreams itself under the
same jobname as the EXIST parameter will pause as long as a job exists by
that jobname.

If you could figure out the job number of the job that you want to wait for
and use the number in your pause statement that should work.



----- Original Message -----
From: "Greg Stigers" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Wednesday, March 23, 2005 2:11 AM
Subject: [HP3000-L] pausing for a job


> Our daily processing shuts down various jobs before the backup, and then
> aborts those that do not shut down. I had noticed that some jobs took
> longer
> to shut down than this process allowed, so I added times pauses for these
> jobs to shutdown. Later, I noticed that one pause always gave an error
> that
> the time for pause had been exceeded. Then I noticed that this job was
> being
> rescheduled to start before the backup. So of course, it existed, and
> pause
> waited on it. Is there a simple way around this, to pause for the
> executing
> job while it is shut down, but not for the scheduled job?
>
> Greg Stigers
>
> * 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 *

ATOM RSS1 RSS2