Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-lcc!ptsfa!ihnp4!cbatt!ucbvax!USC-OBERON.ARPA!TLI%Sargas From: TLI%Sargas@USC-OBERON.ARPA (Tony Li) Newsgroups: mod.computers.vax Subject: Re: Query about priorities in VMS Message-ID: Date: Thu, 19-Mar-87 02:37:55 EST Article-I.D.: Posted: Thu Mar 19 02:37:55 1987 Date-Received: Sat, 21-Mar-87 05:45:20 EST References: Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 20 Approved: info-vax@sri-kl.arpa Brent, Your management does have a legitamate concern. It is possible to notice the effects of low priority batch jobs under VMS, especially if the memory consumption of those processes is significant. Regardless of the priority of the process, if it starts paging or hogging memory, you will notice the effects. I think that the best way to demonstrate the effects to your management is to get permission to set up a limited test. Create a priority-2 queue with only 1 active job and a limited (but reasonable) amount of memory. And maybe a CPU time limit. Let it run and see if anyone notices any degradation.... As long as the batch job is reasonably behaved and you're not memory poor, the effects should not be noticeable. Cheers, Tony ;-) -------