msuters
Active Member
RE: UBEs that must run in single-threadedbatch queues - Summary
Thanks to all those who replied to my query about which batch jobs must
be run in single-threaded queues. There were several different views,
ranging from people who run all jobs in single-threaded queues to those
who run most in a multi-threaded queue. We were concerned that JDE's KG
document OTI-00-0156 does not contain an exhaustive list of jobs.
The approach we have takes is this:
1. Create the default job queue as single-threaded.
2. Create a separate single-threaded queue for post jobs, so this occurs
quickly for users.
3. Create a separate single-threaded queue for the nightly schedule,
which includes posting and integrity reports.
4. Create a multi-threaded queue, and assign to this queue all the batch
jobs that can safely run in a multi-threaded queue. (At the moment we
have 5 threads to this queue.) Individual batch versions are assigned to
this queue as part of the version design.
We feel this provides us with a good balance between response time for
the users, and the safety of using single-threaded queues. The important
thing is that the default queue is single-threaded, so if a new version
is created without using the correct queue, system performance may be
affected, but not data integrity.
Regards,
Mark Suters
ERP8, Update 1, SP22_F1, Windows 2000, Citrix XP, SQL Server 2000.
#####################################################################################
Note:
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are not
the intended recipient. Stockland and any of its subsidiaries each reserve
the right to monitor all e-mail communications through its networks.
Any views expressed in this message are those of the individual sender, except where
the message states otherwise and the sender is authorized to state them to be the
views of any such entity.
Thank You.
#####################################################################################
Thanks to all those who replied to my query about which batch jobs must
be run in single-threaded queues. There were several different views,
ranging from people who run all jobs in single-threaded queues to those
who run most in a multi-threaded queue. We were concerned that JDE's KG
document OTI-00-0156 does not contain an exhaustive list of jobs.
The approach we have takes is this:
1. Create the default job queue as single-threaded.
2. Create a separate single-threaded queue for post jobs, so this occurs
quickly for users.
3. Create a separate single-threaded queue for the nightly schedule,
which includes posting and integrity reports.
4. Create a multi-threaded queue, and assign to this queue all the batch
jobs that can safely run in a multi-threaded queue. (At the moment we
have 5 threads to this queue.) Individual batch versions are assigned to
this queue as part of the version design.
We feel this provides us with a good balance between response time for
the users, and the safety of using single-threaded queues. The important
thing is that the default queue is single-threaded, so if a new version
is created without using the correct queue, system performance may be
affected, but not data integrity.
Regards,
Mark Suters
ERP8, Update 1, SP22_F1, Windows 2000, Citrix XP, SQL Server 2000.
#####################################################################################
Note:
This message is for the named person's use only. It may contain confidential,
proprietary or legally privileged information. No confidentiality or privilege
is waived or lost by any mistransmission. If you receive this message in error,
please immediately delete it and all copies of it from your system, destroy any
hard copies of it and notify the sender. You must not, directly or indirectly,
use, disclose, distribute, print, or copy any part of this message if you are not
the intended recipient. Stockland and any of its subsidiaries each reserve
the right to monitor all e-mail communications through its networks.
Any views expressed in this message are those of the individual sender, except where
the message states otherwise and the sender is authorized to state them to be the
views of any such entity.
Thank You.
#####################################################################################
