timallen
Well Known Member
We have a user who submits many Universal Batch Engine (UBE) jobs at once. On occasion, these jobs process out of order; that is, a job with a submission time of 16:50 reaches status "D" while a job with a submission time of 16:40 is still in "P". I would have thought that the user was wrong, but he's shown me a screen print of it happening.
The enterprise server is configured to have a single queue with only one thread.
[UPDATE]: I didn't mention earlier, but the user is not changing the priority or queue name of the jobs. Just goes to batch versions and starts launching. He *does* have a slow network at times.
Has anyone experienced this? Is there a fix? Thanks in advance.
Here is the pertinent section of the JDE.INI:
[NETWORK QUEUE SETTINGS]
QEnv=PD7333
QUser=JDE
QPassword=JDE
QueueDelay=30
UBEPriority=5
JDENETTimeout=60
UBEQueues=1
UBEQueue1=QB7333
PackageQueues=1
PKGQueue1=QB7333
SpecInstallQueues=1
SpcQueue1=QB7333
KillImmediate=1
The enterprise server is configured to have a single queue with only one thread.
[UPDATE]: I didn't mention earlier, but the user is not changing the priority or queue name of the jobs. Just goes to batch versions and starts launching. He *does* have a slow network at times.
Has anyone experienced this? Is there a fix? Thanks in advance.
Here is the pertinent section of the JDE.INI:
[NETWORK QUEUE SETTINGS]
QEnv=PD7333
QUser=JDE
QPassword=JDE
QueueDelay=30
UBEPriority=5
JDENETTimeout=60
UBEQueues=1
UBEQueue1=QB7333
PackageQueues=1
PKGQueue1=QB7333
SpecInstallQueues=1
SpcQueue1=QB7333
KillImmediate=1