Dave, this is because you have all jobs running in the same queue. If one job hangs it blocks all other jobs in the same queue. I suggest to configure several job queues placing jobs for different applications (or different ljob streams) into different queues. This way if a job in one queue takes longer to run or hanhs it does not affect jobs in other queues.
Another way is to place potentially hanging" jobs in their own dedicated queues so that thay don't affect other jobs. Usually having 3 to 6 job queues should be enough for any processing. To configure new queues you can use Tools/Job Queues menu. In the job properties you can then select which queue to use for that job. Please note that you must restart 24x7 after changing queue setting : SysOP, : First I want to thank you for your quick responses. : I am having a serious problem lately with my 24x7 Server. : I am running multiple jobs and sometimes if a job fails or takes longer to
: run the normal all jobs that are supposed to run after
: that either fail or go into a "hang state".
: The jobs that "Hang" do run when the origial job completes but a
: lot of times it is too late as some of my reports
: are time sensitive.
: Is there anything I can do on the OS(Win 2000 Server) level or 24x7 level
: that can prevent this? As always thanks for your help
|
