When a business event is created (signal event or data event), the binary event is put on a business event dispatch queue for dispatch processing.  Business event dispatch processing reads binary events from dispatch queues, formats each event, and transmits the formatted event to one or more event consumers.   When dispatch processing is formatting an event, the size of the formatted event can be several times larger than the binary event size.  For example, a 12 KB binary event can be 40 - 60 KB when the event is formatted as a JSON or XML document, which can then be transmitted to multiple event consumers.  As a result, formatting and transmitting an event might consume several times more system resources compared to the binary event that is stored on the local dispatch queue.

Previously, business event dispatch processing processed events without considering available system resources. If dispatch processing formatted and transmitted events faster than the formatted events could be sent to event consumers, dispatch processing would continue consuming system resource even if the z/TPF system was low on resources.

With business event dispatch resource checking, business event dispatch processing checks available resources by using the IBMHI resource priority class and suspends processing when system resources are low. In this way, dispatch processing will not consume additional system resource when the z/TPF system is low on system resources.  Business event dispatch processing automatically resumes when enough system resources become available

In addition, the ECB owner name for the business event dispatch ECB (BEVQ) is updated to differentiate between dispatch ECBs for the business event system default queue and user defined dispatch queues. ECB owner names for the dispatch ECBs are as follows:

• Dispatch ECBs for the business event system default queue:  IBEV.DISPATCH.SYSTEMQUEUE

• Dispatch ECBs for business event user defined queues:  IBEV.DISPATCH.USERQUEUE