RE: Class Time Slice

 Good stuff, thanks.
?

>
>
> Looking at the V5R1 Work Management manual has some interesting
> stuff here.
>
> Jobs ending are often reduced in run priority (higher numeric) by
> 10, time
> slice is reduced to 100, and purge is *YES. Result is, the ending job has
> less impact on other jobs - the others get the CPU faster because of the
> lower time slice.
>
> OTOH, in order to give an emergency job more priority, it suggests
> increasing the time slice to 20000.
>
> And this recommendation:
>
> When observing job transitions, it is usually advisable to complete a
> transaction during a single time slice. This reduces the number of times
> the job enters and leaves main storage. Therefore, the
> active-to-ineligible
> transitions should be 0. However, long running transactions should not
> occupy activity levels for the entire transaction. You should establish a
> time slice value that allows 90% of the transactions in your
> environment to
> finish in a single time slice. An example of a time slice value
> is: 3 × the
> average CPU per transaction. For more information about job transition
> data, see ?Thread State Transitions? on page 263.
>
> HTH
>
> Vern
>
> At 01:16 PM 3/25/2003 -0500, you wrote:
>
> >  IBM still has the default for the interactive class time slice at 2000.
> >This has been in place since the beginnings of OS/400.  With today's
> >superior processors what is the suggested value?  Does a table exist
> >anywhere that shows settings for different generations of systems?  I'm
> >running my 830 with the QINTER class time slice set at 100 or 200.
> >
> >  Comments.

>