HP3000-L Archives

May 2000, 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:
Barry Lake <[log in to unmask]>
Reply To:
Barry Lake <[log in to unmask]>
Date:
Mon, 22 May 2000 10:32:00 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
At 8:11 AM -0400 5/22/00, [log in to unmask] wrote:
>On Mon, 22 May 2000 00:36:39 -0700, Barry Lake <[log in to unmask]> wrote:
>>I don't think we can get a clear picture of what's happening without seeing
>>the output of the SHOWJOB;JOBQ command.
>
>Sure. Count 'em up, I think you'll agree something's amiss.


Agreed, something's not right. I've said this privately to an HP
representative, and now I'll repeat it here: I applaud HP for implementing
user defined job queues, however the current implementation has some ragged
edges. Your situation clearly demonstrates another example of this.

If you're able, I'd be interested to know what would happen if, for
temporary testing purposes only, you were to create a new queue, say
"SERVER2", set its limits to match the SERVER queue, and then ALTJOB all
the jobs which are currently executing in the SERVER queue to the new
SERVER2 queue. Then take a look at the LISTJOBQ output again. Your problem
will likely not be solved, but doing this might help shed some light on
where the root of the problem lies...

...then again, it might not.


Barry Lake                                 [log in to unmask]
Allegro Consultants, Inc.                  www.allegro.com
(408)252-2330

ATOM RSS1 RSS2