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.
Table 1. Monitoring domain's generic gates
Gate Trace Functions Format
APUE

MN 0601
MN 0602

SET_EXIT_STATUS

APUE
DMDM

MN 0101
MN 0102

INITIALISE_DOMAIN
QUIESCE_DOMAIN
TERMINATE_DOMAIN

DMDM
STST

MN 0401
MN 0402

COLLECT_STATISTICS
COLLECT_RESOURCE_STATS

STST
TISR

MN 0801
MN 0802

NOTIFY

TISR
XMNT

MN 0901
MN 0902

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.
For a cold start, the information comes from the system initialization parameters; for any other type of start, the information comes from the global catalog, but is then modified by any relevant system initialization parameters.
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.



dfhs3_MNgenericGates.html | Timestamp icon Last updated: Monday, 5 June 2017