Jay,
From a purchased solution side of things, all the major job scheduling
packages will allow you to do this. Short of that, I created a command file
that would do basically what you are talking about. The command file
basically pauses as long as it finds a job executing with the name (or
partial name) specified. For example the command "JOBWAIT fred@" in a job
stream would cause the job to wait until there was no other jobs with the
name fred+"anything" executing and then it would continue.
Thanx,
Jonathan (Jon) M. Backus, MPE-CSM ~ President
Tech Group ~ 15 Catawba Place ~ Hagerstown, MD ~ 21742-6515
Email: [log in to unmask] ~ AIM: JMBackus
Vmail: 301.988.0614 ~ Fmail: 301.714.1854
Web: www.TechGroupMD.com
-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
Behalf Of Jay Willis
Sent: Tuesday, June 19, 2001 11:40 AM
To: [log in to unmask]
Subject: Getting jobs to run in proper sequence
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 *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|