HP3000-L Archives

February 2002, 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:
Michael Berkowitz <[log in to unmask]>
Reply To:
Michael Berkowitz <[log in to unmask]>
Date:
Thu, 28 Feb 2002 12:02:27 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (35 lines)
John Keener writes


Today I had a perfect application for the NEWJOBQ feature in MPE/iX 6.5. We
have two groups of users. One group submits jobs that take about 30 seconds
each. Typical jobs for the other group take about 5 minutes each. So I
thought I'll give the second group of users their own job queue.

NEWJOBQ ALTJOBQ;LIMIT=1
LIMIT 1    (for HPSYSJOBQ)

Now I submit a long job into the ALTJOBQ queue, and a quick job into the
default job queue. The second job goes into the WAIT state. Why?

It seems that the JOBQ feature has not been thought through completely. Am I
right, or am I full of corral dust?

Thanks for any help


John Keener
-------------------------------------------------------
You might want to dust yourself off.  Your NEWJOBQ statement is correct, but
your second statement didn't do what you thought.  To put a limit of one on
the HPSYSJQ job queue, your statement should read :LIMIT 1;JOBQ=HPSYSJQ.  By
saying :LIMIT 1, you are changing the total job limit on the system to one.
Since the total limit is one, and the long job in ALTJOBQ is still running,
the second job waits even though he is the only job in his queue.

Mike Berkowitz
Guess? Inc.

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

ATOM RSS1 RSS2