On Fri, 12 Jan 1996 14:58:12 -0800 <[log in to unmask]> said: >Jeff [Vance] writes: >> That said, I would like to keep open the possibility of a jobQ having >> additional properties, like: jobfence, jobpri, jobsecurity, etc. > >I would too, and I don't think my way limits this possibility And let's tack on a cpulim, and outclass (with env= if you can swing it). >> Unless a jobQ has runtime properties, like PRI, there would be no impact on >> moving an EXEC job from one jobQ to another. Right?? > >Someone else pointed this out but briefly: > >:ALTJOB on a WAITing job requires only evaluating whether you can now launch >that job (it got moved to a queue with available limit slots). > >:ALTJOB on an EXECuting job only requires evaluating whether a different job >can now launch because we just freed up a slot in the queue we were in. Yuck... I see no need to alter the queue after the job reaches INTRO/EXEC. No, no, no; overly complicating things. Jeff Kell <[log in to unmask]>