z/TPF business event APIs to query status and info about active events and dispatch adapters

1. Provide zEV API returning the zEV Names of all Deployed and Active z/TPF zEVents
2. A customer written z/TPF program will call the API every "n" minutes to get a list of all deployed and active z/TPF Business Eventing Facility (zEV) Named Events. The API would provide the Caller with a list of names and their current operational status.
3. A customer written z/TPF program can call an API (same or different API from item 2 above) to get a list of all zMQQ Names used in the dispatch adapters.
4. At a minimum, the input to this API is a single event name and the return data includes the list of dispatch adapters used for that event and the zMQQ Name used by each dispatch adapter (if any). Note: a single zEV Name may have multiple z/TPF zEventing Dispatch Adapters (zEVDA) each with its own zMQQ Name.
5. Alternatively, an option might be provided to accept a list of event names and the returned data includes dispatch adapters and zMQQ names for all listed events.
6. (Optional) Consider providing a "trigger" where a customer written z/TPF program is called when a business event or dispatch adapter has changed. This "trigger" might be defined through an API call, configuration option, user exit, or some other option as deemed appropriate. It would mitigate the need to poll.