Jeff Vance wrote:
>
> This got me wondering if there is *real* value in being able to pause JFOO
> until JBAR is "executing".  (Note: in a 5.0 patch being developed, the PAUSE
> command has been enhanced to be able to pause until a job or jobs have
> terminated.)
>
> I offer a possible way of doing this, but it is important to me that there is
> actually a need to be able to pause one or more jobs until it (or they) have
> reached a certain state (in this case, are executing rather than waiting,
> scheduled or just introduced).
>
> (snip)
>
> I am wondering if there is a need to be able to pause while jobs are not yet
> EXEC* vs. just being able to pause until a job has terminated?
>
 
I personally don't need it today;), but I can remember many a time when I
wished I had it.  What I had done in the past was to have a control file
with values to be checked and verified before a job could execute.
 
Larry Boyd    <[log in to unmask]>
"Talk is cheap because supply is high and demand is low."
  - Someone who knows what they're talking about
(BTW, these opinions are my own and not those of HP's.)