[Info-vax] vms base priority watch

Jan-Erik Soderholm jan-erik.soderholm at telia.com
Mon Jul 11 13:42:45 EDT 2011


pcoviello at gmail.com wrote 2011-07-11 18:58:
> On Jul 11, 12:01 pm, "Richard B. Gilbert"<rgilber... at comcast.net>
> wrote:
>> On 7/11/2011 11:09 AM, pcovie... at gmail.com wrote:
>>
>>
>>
>>
>>
>>> On Jul 11, 10:43 am, "Richard B. Gilbert"<rgilber... at comcast.net>
>>> wrote:
>>>> On 7/11/2011 9:46 AM, Bob Koehler wrote:
>>
>>>>> In article<1f612927-5e98-44e0-91e2-d889916c4... at gh5g2000vbb.googlegroups.com>, "pcovie... at gmail.com"<pcovie... at gmail.com>      writes:
>>>>>> ok well. I did ask a yes/no question! me bad!  yes I understand the
>>>>>> non-prived user would not do this but... we have given users the
>>>>>> rights to do this early in the morning to get their jobs completed,
>>>>>> when there are less users on the system.
>>
>>>>>       If the system is otherwize idle at that time, that should have no affect.
>>>>>       If only some users get to do this in the ealy hours, then it's worth while.
>>
>>>>>       VMS does not delay lowpriorityprocesses just to make them take
>>>>>       longer, it there are no higherpriorityprocesses doing anything.
>>
>>>> I can recall occasions during which a job was getting 99 percent of the
>>>> CPU at PriorityOne.  The "hunt and peck" typists never noticed it!
>>
>>> thanks everyone,  I know it isn't the best solution, but as I said I
>>> just started the job and need to pick and choose what comes first...
>>> thinking about this some more and doing some digging I thought
>>> accounting would tell you who might have issued a command?   after a
>>> year some things are still fuzzy, so haven't come up with anything
>>> yet, but I'm wondering as someone pointed out that what if they hit
>>> the time between the hour!  so it might be best to see if I can audit
>>> who issued the command and see what time?  any ideas?
>>
>> Accounting is not going to tell you who issued a command unless that
>> command created a process.  In Unix you can't blink without starting a
>> process or two.  Not so in VMS!
>>
>> Maybe you should back up a bit and define the problem you are trying to
>> solve!- Hide quoted text -
>>
>> - Show quoted text -
>
> I'm trying to figure out if anyone is raising the priority outside of
> allowed hours ...
>
> thanks
> Paul

And what is the problem if they do ?

I guess that outside of "allowed hours" there are other users that would
be "hurt" if these users raised their prio, right ?

And within "allowed hours" that is not the case. But then, if there is no
other users getting "hurt", there is no reason to raise the prio either !

The whole point of raising the prio is that one *want* other processes
to get "hurt" by that (that is, runnig slower). If not, there is
no point in it.

As many others have said, raising the prio on an otherwise idle system
will not make anything run faster...

Can it be that the mix of batch/interactive users are different ?

Jan-Erik.



More information about the Info-vax mailing list