Ah,

I've discovered another major problem.  If you try to stream a job into a
queue that doesn't exist, you will get a warning, but the job will stream
anyway and sit in a wait state.  This is annoying, but the bad part is that
the job cannot be aborted without shutting down the system.  You cannot
create the queue after the fact.

Anyone run into this one?

shawn





Gavin Scott <[log in to unmask]> on 01/27/99 01:08:33 PM

Please respond to Gavin Scott <[log in to unmask]>

To:   [log in to unmask]
cc:    (bcc: Shawn Gordon/IS/FHM/FHS)
Subject:  bugs in new job queues?




Shawn ponders:
> I've been messing with the new job queues in 6.0, and other than the
> oversite of the JOBFENCE, I found something rather odd.  If I do a
LISTJOBQ
> the HPSYSJQ show's a job limit of 3500 even though my job limit is 30.

All job queues have a LIMIT that is separate from the one true system
LIMIT.  This includes the default HPSYSJQ.  The 3500 default is a number
large enough that you should never run into the case where the existence
of this second, unobvious, limit on normal jobs affects you.

I suspect that you can reduce your entire operations and support staff
to a whimpering, twitching, paranoid mass by executing the command:

   :LIMIT 0;JOBQ=HPSYSJQ

and then watching while they attempt to figure out why jobs won't log on,
even though :SHOWJOB indicates that the system LIMIT should allow them
to.

G.