It details how to set and then monitor changes to the interactive time slice. Wouldnt using Performance Data be helpful to determine how many and which of your jobs are hitting time slice end. I haven't administered systems, for years now, but I am wondering, does the technique I describe still work? I dont think this would be a good strategy on medium to large evironments. I think there are other factors such as the Time Slice End Pool, Performance Adjustment, Dynamic Performance Bands, multiple subsystems, multiple classes in subsystems that are more significant in helping prioritise the work. Has anyone had good success trying some of the things I wrote about? No. I tend to take a more business approach. Sometimes there are business important transactions/processes that are complex but are high priority. The dependency on the TimeSlice alone doesnt take that into account.