Get yourself a free copy of MasterOp from the CSL tape, or I think you can
still download it from allegro.com, but that is a sweet job scheduler and
there are plenty of options for controlling job initiation using job
completion, failure, etc. - very powerful, relatively low learning curve,
and free :)

At 08:40 AM 6/19/2001, Jay Willis wrote:
>Hi all,
>
>I am seeking suggestions on how we might get a series of jobs to run in the
>proper sequence. Currently the jobs, in turn, build/check for the existence
>of/purge dummy files. I don't care for this approach since a file may
>inadvertently be renamed, purged, etc. between jobs. This happened to us
>recently when a job aborted, thus not building the dummy file that the
>subsequent job was to check for, allowing the user to stream a job out of
>sequence. The users can make changes to the data, based on the reports the
>jobs produce, so that after job A runs, they go over the reports, make
>changes, then stream job B, and so forth.
>
>Any ideas/thoughts gleefully accepted.
>Jay
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *


Regards,

Shawn Gordon
President
theKompany.com
www.thekompany.com
949-713-3276

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *