If it determines that multiple jobs with the same name, user & acct are executing at the same time, it lets the lowest job# run and pauses the others until the first it done.  When that happens it finds the "new" lowest job# and lets that run and pauses the others.
The pause time is one of the parameters in the command.  It does have some overhead to run the program inside of a while loop but it does that only as often as you tell it to run when you specify the pause time.
mike


>>> Dale Pepoon <[log in to unmask]> 11/19/2007 12:41 PM >>>
Ok.  I am curious.  How does a COBOL program do this?
Does it cause an abort of the second job?  Does it reschedule the second 
job for later?
If there are multiple jobs with the same name that need to run, how does 
it decide which job gets to run first?
What flags or indicators are being evaluated by the second job that are 
set by the first job and remain for the duration of the first job?

Thanks
dp




Michael Caplin <[log in to unmask]> 
Sent by: HP-3000 Systems Discussion <[log in to unmask]>
11/19/2007 09:02 AM
Please respond to
Michael Caplin <[log in to unmask]>


To
[log in to unmask] 
cc

Subject
[HP3000-L] single thread job streams with the same name






I searched the archive looking for something that would prevent multiple 
jobs 
with the same job name from running at the same time.  I found some 
solutions but they were not fail-safe so I wrote something that seems to 
be 
fool-proof.  It's a one line command at the front of a stream that invokes 
a 
command file.  The command file runs a small cobol program.  If anyone has 
a 
use for it, let me know.
Mike

* 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 *

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