rgreensl
Active Member
Hi everybody,
I am interested in seeing how people who are using V9.0 or 8.12 are managing their job queues. We currently have a dual threaded (ie one queue in which 2 jobs can run simultaneously) queue which is fine for Xe/coexistence but when we are live on 8.12 we will have much more UBEs running and will need to decide how work management is implemented. I think the main options are as follows...
Do you recommend
one single threaded queue for each application area (such as AR, GL, distribution etc). The issue with this is that there is a lot of version configuration/maintenance required to implement. You can do this with different link user profiles which causes issues with connection pooling being less efficient.
one multi-threaded queue (perhaps 5 jobs at a time) for all default UBE's. Those that need to be single threaded (such as overnight batch) could be run in a seperate queue. This is my preferred option but the issue is identifying UBE's that have to run single threaded (the assumption is that during the daytime operations there won't be many of these).
any thoughts...?
thanks,
Rich
I am interested in seeing how people who are using V9.0 or 8.12 are managing their job queues. We currently have a dual threaded (ie one queue in which 2 jobs can run simultaneously) queue which is fine for Xe/coexistence but when we are live on 8.12 we will have much more UBEs running and will need to decide how work management is implemented. I think the main options are as follows...
Do you recommend
one single threaded queue for each application area (such as AR, GL, distribution etc). The issue with this is that there is a lot of version configuration/maintenance required to implement. You can do this with different link user profiles which causes issues with connection pooling being less efficient.
one multi-threaded queue (perhaps 5 jobs at a time) for all default UBE's. Those that need to be single threaded (such as overnight batch) could be run in a seperate queue. This is my preferred option but the issue is identifying UBE's that have to run single threaded (the assumption is that during the daytime operations there won't be many of these).
any thoughts...?
thanks,
Rich