HP3000-L Archives

June 2000, Week 1

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:
"VANCE,JEFF (HP-Cupertino,ex1)" <[log in to unmask]>
Reply To:
VANCE,JEFF (HP-Cupertino,ex1)
Date:
Mon, 5 Jun 2000 19:34:38 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
> Last week listers were talking about using "Pause Job=myjob.accout" to
> pause a job until another job finishes.  I've tried this with minimal
> success.  If myjob.account re-streams itself for a later time, or day
> then it appears the job the executes the pause job=myjob.account will
> pause forever.

You could do the pause based on the job number rather than a user.acct
Eg.   :pause job=#J123     or

      !job job,user.acct...
      !#... do some work
      !stream foo
      !pause job=!HPLASTJOB
      !# do some more work...

If it is not easy to get the target job number, you can do some
simple CI programming using the JOBCNT and JINFO functions (in
6.0 PP2).  If this is a viable approach for you I'd be happy to
assist.

You can also put a maximum time limit on the pause, e.g.
      :pause 1200, j@:user.acct
which states to pause until all jobs-only (not sessions) logged
on as "user.acct" terminate, or 20 minutes, whichever occurs first.

> It appears that the "pause job=' command checks for any job in the job
> queue.  The job can be executing, waiting or scheduled.  Am I
> correct in this assumption?

Yes.  You can pause for jobs that are waiting (intro, intro*, susp,
SCHED, or WAIT:n).  The pause ends when the job is no longer waiting
 -- it could be executing, or it could have already ended.


HTH,
 Jeff Vance, CSY

ATOM RSS1 RSS2