When you discover a user that is hogging the system just issue the altproc
commnand against their session and drop them to the "E' queue.  That way
their "quick" report won't be so quick!



john edwards wrote:

> Just re-read this and I must apologise for the grammer and spelling.
> Let me add another observation. In a well ordered shop it is usually a
> programmer or operator that is hogging the system. Running something in
> a session that should be done in batch. An operator doing a
> store/restore from a session will do it everytime. A programmer running
> a "quick" report or QUERY FIND ALL, REPORT with SORT will not only
> knock back the batch jobs, but also impact all the legitimate on-line
> processes. Once you have found the culprit an education session,
> followed by a course in manners accompanied by a big stick should
> resolve your problems without resorting to changing the queues.
> Sometimes that does not work. We had one programmer who never used
> batch and selfishly ignored the impact on other users. The solution was
> simple. Everyday we used GLANCE to knock his session back to the DQ and
> left him there. This went on for a year and he never found out and we
> never had a problem with him hogging the system.
> Regards
> John