HP3000-L Archives

July 1998, Week 2

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:
Gavin Scott <[log in to unmask]>
Reply To:
Gavin Scott <[log in to unmask]>
Date:
Wed, 8 Jul 1998 09:27:52 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
Neil asks:
> On this subject of "daemons", does anyone know if MPE/iX 6.0 will offer
> "hidden" as one of the attributes of it's new multiple job queue?

If the implementation of multiple job queues looks the way we discussed
on the list last year, then it is effectively nothing more than an
automatic :LIMIT management system for controlling which jobs are
allowed to start.  Once a job starts the MJQ functionality won't have
any further effect on it.  So "hidden" would be an attribute of an
executing job, where as MJQ concerns itself with waiting jobs.  Of
course you can probably create a job queue named "hidden" and have
all jobs streamed in this queue log on immediately and have no effect
on any other jobs on the system, which is what you want in a "hidden"
job.  It's just that you'll still *see* the "hidden" jobs in a :SHOWJOB.

If :SHOWJOB is enhanced to select jobs based on which queue they launched
out of, then you could change your :SHOWJOB commands and UDCs to exclude
things that came out of the "hidden" queue.

Again, things may have changed since we first discussed all this, or my
memory may be less than perfect on the details.

G.

ATOM RSS1 RSS2