Subject: | |
From: | |
Reply To: | |
Date: | Fri, 12 Jan 1996 23:21:46 EST |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On Fri, 12 Jan 1996 23:24:14 GMT Steve Cooper said:
>In all of this great discussion on Multiple Job Queues, I have not
>seen specific reference to one special type of job. It may be obvious
>and it may not have any special requirements, but I thought I'd
>mention it, just for the sake of completeness.
>Every system seems to have some number of jobs that are supposed to be
>running ALL of the time. These are equivalent to what UNIX might call
>"daemons".
I'm hoping my post on this was sent out OK; Gavin has replied to it so I
presume it is, maybe Steve is just as backlogged on mail as I am :-) But
I agree 100%, it was my #1 need.
The other issue Gavin and I disagree on, in a nutshell, is how can you
run a job RIGHT NOW. Gavin suggests moving an active job in the queue in
question to another queue, I suggest a HOT queue with an implicit ;HIPRI
that could be restricted to OP/SM users. I will address that further in
a follow-up to his reply; meanwhile I'm reading ahead to make sure that I
don't duplicate myself again :-)
Jeff Kell <[log in to unmask]>
PS - The "daemon" queue idea is related to a similar enhancement request
at the last IPROF for a "system-adopted process", same idea, but perhaps
a more traditional implementation as a special job queue (IMHO).
|
|
|