Job priorities do not provide a mechanism to specify an absolute execution order of jobs. There is no guarantee that a job with a higher priority will execute before another job of lower priority.
Imagine that two jobs are set up, one for a very large software package and one for a very small software package. If these packages require DTS transfers it will take much longer to transfer the large package than the small package. When the transfer of the small package is completed and the job activation time has been reached the job will execute even though it has a lower priority than the job for the large package.
In general, all job containers which have reached their activation time and are available on the scalability server will be considered for execution. Job prioritization affects the order in which those job containers are executed. Job containers still being processed by the manager or in progress of being transferred will not be considered by the scalability server.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|