When you shutdown the managers with the abort option

Applies to:
Oracle Application Object Library - Version: 11.5.9 to 11.5.10.2
Information in this document applies to any platform.
Goal

When you shutdown the managers with the abort option does it submit a concurrent request that is run straight away with a high priority?

Similarly you shutdown with the normal option, does this job have to wait on an available manager or does it run straight away?
Solution
If you shutdown the concurrent managers with the ABORT option ( using CONCSUB), it will run a concurrent request with a priority of -75 to terminate all requests and shutdown the managers. This is the most important priority for a concurrent request and means that the ABORT request will be run before all other concurrent requests .

If you shutdown the concurrent managers normally ( using startmgr), it will run a concurrent manager with a priority of 0. This is very high priority for concurrent requests.
By default , all the concurrent request have a priority of 50 .
It means that the SHUTDOWN request will be run before all other concurrent requests except the ABORT request .

( -75 is a higher priority than 0 , 0 is a higher priority than 50 ) .