Publishing Engine Programmer's Guide > The Arbortext Publishing Engine Request Manager > Predefined Dynamic Components > Pre-Defined Queues > Transaction Scheduling Options
  
Transaction Scheduling Options
You can configure the queue parameter scheduling-option in e3config.xml to one of the following values
strict-complete
No transaction shall start executing until all previous transactions on the queue have finished executing, including held transactions. Note that choosing this value means that transactions from this queue will never execute in parallel.
strict-parallel
No transaction shall start executing until all previous transactions on the queue have started executing, including held transactions.
relaxed (the default)
A transaction can start execution after every previous transaction on the queue that is not held has started executing.
This value allows a transaction to start executing even if earlier transactions on the queue are held or are unable to execute for some reason.