Wirt Atmar wrote:
>
> James writes:
>
> > Note: HP does not support increasing the priority of INETD or any user
> >  applications to a priority in the BS queue.
> >
> I am not sure what the above means.  However, while I have no direct
experience with NETTD, I have previously had a lot of experience with
running NetTD like programs in the B queue.  Note:

1.  NETTD is NOT an application.  It is a quasi system program.
2.  IF the installation needs to allow logons under high activity
    situations so that users will not wonder if the system is down
    than the obvious way to do it is to run in the B queue.
3.  Of course, making it a system process would also work, but why
    go to the additional trouble?  Also you loose flexibility because
    some may not want this high priority for logons under high
    activity conditions.
4.  A small but possibly significant additional factor is that putting
    a process in the B queue prevents it from being swapped out
    because of a elapsed time and is therefor more efficient - cuts
    down on possible thrashing.

BTW, I am surprised the B queue is not used more often for critical
short duration transactions.  Swapping in and out is a CPU time
wasting exercise except where necessary for "time sharing".

Nick D.