[Info-vax] vms base priority watch

[abrsvc]

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 -

Since VMS uses a preemptive scheduling process, the raising of
priority rarely has much effect unless the process is compute bound.
Most of the time, the process will be in LEF mode (5 points higher
than base priority).  The first task is to lower the priority boost by
1 so that the next interrupt for another process can get CPU.  This
will continue until the process has reached base priority where the
majority of the CPU work will occur.  Raising the base higher than 4
rarely makes too much of a difference for the raised process, it CAN
however affect other processes rather drastically.  Changing
priorities should be done with care.

Perhaps you should gather baseline info about current process
priorities using monitor.  This whole idea of changing the priorities
may be a smoke screen.

Shoot me an Email with contact information/phone should you like to
discuss this further.

Dan

dansabrservices AT yahoo DOT com