RE: Running batch jobs in Qinter

[Mike.Barton@xxxxxxxxxxxxxxxxx]

>Original reply:
>
>Try holding jobq QINTER
>
>This works for a while until they notice.
>
>Another option is to change the class .
>By using  a class with a much higher priority (numerically that is)
>- say 99 , any advantage is lost.
>
>HTH
>
>Jeff's reply:
>
>This is not strictly true.  Unless the system CPU is running at close to
>100%, a batch job is still going to get sufficient cpu cycles to cause
>damage performance - this is done by the batch job over-storing the memory
>pages of the interactive jobs.  The priority value of '99' is only relative
>to other jobs in the system, it is therefore likely that 51 (for example)
>would have the same effect.
>
>Running batch jobs in the same subsystem is not actually the problem, it is
>when they run in the same memory pool as interactive jobs that the problems
>can occur.  Since most commonly subsystems only have one pool defined ...
>
>IBM have always recommended, for as far as I can remember, NOT to mix job
>types in the same memory pool.
>
>Jeff bull


Jeff
agreed in that it depends what operating system level u r at.
The latest releases don't 'obey' the level any where near as much as
they used to.

Mike

Removing the QINTER jobq from QINTER subsystem  is a good idea
but as previously suggested, you apear to allow the users to do too much.

They would onl find another jobq to use instead - even QCTL !





This communication and the information it contains: - (a) Is intended for the 
person(s) or organisation(s) named above and for no other person(s) or 
organisation(s). Access to this mail by anyone else is unauthorised. (b) Is 
confidential, and may be legally privileged or otherwise protected in law. 
Unauthorised use, circulation, copying or disclosure of any part of this 
communication may be unlawful. (c) May be susceptible to interference, and 
should not be assumed that it has come in its original form and/or from the 
stated sender or PinkRoccade UK accepts no responsibility for information, 
errors or omissions in this e-mail or use or misuse thereof or any act done or 
omitted to be done in connection with this communication. If you are not the 
intended recipient, please inform postmaster@pinkroccade.co.uk immediately and 
delete it and all copies from your system.