HP3000-L Archives

July 2007, Week 4

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:
"Fairchild, Craig D" <[log in to unmask]>
Reply To:
Fairchild, Craig D
Date:
Tue, 24 Jul 2007 18:09:59 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
Hi Tom,

I don't know if this will work for you or not, but we have similar requirements in some of our test suites. We want jobs to execute one at a time. The solution that we use is rather simple, and may only work because of the relatively controlled environment that we're running in. We use the CI's :LIMIT command to set the job limit to 1 more than the number of "background" jobs that we have. On every system there are a number of jobs that are expected to be running all the time in the background. Once you know what that number is (let's say you have five "permanent" jobs), then doing a:

:LIMIT 6

Will not allow more than six jobs to be executing at any one time. The five that are already running will continue and one more will always be available. The OS will take the first job with the highest job priority and run that. As soon as that job completes it will launch the next one.

It's also important to understand the limitations to this simple solution. If one of the five "permanent" jobs terminates for any reason, then the job limit of 6 would allow 2 new jobs to begin executing, which probably is not what you would want. Also, if a new "permanent" job is started (let's say someone starts up a new network service that requires a monitor type job to be running), then you'll need to manually adjust the limit to 7 to allow additional jobs to run.

For complex environments this solution probably won't be reasonable, but it can be helpful if you have sufficient control and a very stable execution environment.

Take Care,
Craig

> -----Original Message-----
> From: HP-3000 Systems Discussion
> [mailto:[log in to unmask]] On Behalf Of Tom Emerson
> Sent: Tuesday, July 24, 2007 10:05 AM
> To: [log in to unmask]
> Subject: [HP3000-L] JMS and HP system jobq's question
...
> We have a "situation" where I'm currently employed where they
> are using JMS to "single thread" a particular process.
...

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

ATOM RSS1 RSS2