Expediting Express Requests - comment by SmarakDas

Hello Carrie,
Wonderful Article. I have a few questions concerning Expediting Express Requests:
(a) You have mentioned the DBQLogTbl Column "ParserExpTime" denoting the time in seconds for Express Requests. Do the Explain Plan shows any indication of this timing.
(b) In the 2nd paragraph under "Assessing parsing time spent on express requests", you have written "You will see a NULL when no express requests were issued because all the data was found in the data dictionary". It should be 'Data Dictionary Cache of the PE' instead of simply 'Data Dictionary'. Please rectify me if I am wrong. As Express Request deals with DD & DD Cache, this line is kind of confusing for me.
(c) When you say "If there are no AWTs available in the unassigned AWT pool at the time the message arrives, and the three reserves for Work01 are in-use, the message will wait on the queue", I wish to clarify 01 thing. If the Express Request isn't expedited, then the message will wait on the queue after checking the unassigned AWT pool only. The availability of the 03 AWTs reserved for Work01 shouldn't matter as these reserved pool is meant for Work01 message originating from queries of Tactical Workload or expedited requests only. Please rectify me if I am wrong.
 
Thanks In Advance,
Smarak