Monitoring domain's generic gates
Table 1 summarizes
the domain's generic gates. It shows the level-1 trace point IDs of
the modules providing the functions for the gates, the functions provided
by the gates, and the generic formats for calls to the gates.
| Gate | Trace | Functions | Format |
|---|---|---|---|
| APUE | MN 0601 |
SET_EXIT_STATUS |
APUE |
| DMDM | MN 0101 |
INITIALISE_DOMAIN |
DMDM |
| STST | MN 0401 |
COLLECT_STATISTICS |
STST |
| TISR | MN 0801 |
NOTIFY |
TISR |
| XMNT | MN 0901 |
MXT_CHANGE_NOTIFY |
XMNT |
In initialization processing, the monitoring domain sets
the initial monitoring options:
- Monitoring control table suffix
- Initial monitoring status
- Initial exception class monitoring status
- Initial performance class monitoring status
- Initial transaction resource class monitoring status
- Initial converse option
- Initial syncpoint option
- Initial time option
- Initial frequency option
- Initial subsystem id.
In addition:
- If necessary, the monitoring control table (MCT) is loaded and initialized.
- If performance class monitoring is active, CPU timing is started.
- The monitoring domain user exit gate is enabled.
- Messages are sent to the console to indicate whether monitoring is active, and what MCT suffix (if any) is being used.
In quiesce processing, the monitoring domain waits for all transactions that it is monitoring to terminate. Then the final data in the performance class buffer and the transaction resource class buffer, if any, is written to SMF.
The monitoring domain does no termination processing.