Dump domain’s generic gates

Table 50 summarizes the dump 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 50. Dump domain’s generic gates
Gate Trace Function Format
DMDM
DU 0001
DU 0002
PRE_INITIALISE
INITIALISE_DOMAIN
QUIESCE_DOMAIN
TERMINATE_DOMAIN
DMDM
APUE
DU 0301
DU 0302
SET_EXIT_STATUS
APUE
STST
DU 0500
DU 0501
COLLECT_STATISTICS
COLLECT_RESOURCE_STATS
STST

For descriptions of these functions and their input and output parameters, refer to the topics dealing with the corresponding generic formats:

Functions and parameters

In preinitialization processing, the dump domain establishes the initial dumping status:

For a cold start, the information comes from the system initialization parameters; for any other type of start, the information comes from the local catalog, but is then modified by any relevant system initialization parameters.

In initialization processing, the dump domain loads the transaction dump table and the system dump table from the global catalog.

In quiesce processing, the dump domain performs only internal routines.

In termination processing, the dump domain closes the transaction dump data set.

DMDM PRE_INITIALIZE function

The PRE_INITIALIZE function of the DMDM gate performs the following functions:

  1. Issue MVS™ GETMAIN for DU anchor block (DUA) and initialize it.
  2. Read DU state record from the local catalog and set values in the DUA.
  3. Initialize to empty the system dump table.
  4. Issue MVS GETMAIN for DU statistics buffer.
  5. Acquire startup information from the parameter manager (PA) domain and set it in the DUA.
  6. Inform the kernel that DU system dump is available by issuing KEDD ADD_GATE for the DFHDUDU gate.

DMDM INITIALIZE_DOMAIN function

The INITIALIZE_DOMAIN function of the DMDM gate performs the following functions:

  1. Load the system dump table from the global catalog.
  2. Load the transaction dump table from the global catalog.
  3. Issue LMLM ADD_LOCK for the dump data set lock (DUDATSET).
  4. Issue LMLM ADD_LOCK for the dump table lock (DUTABLE).
  5. Issue LMLM UNLOCK for DUTABLE lock.
  6. Issue KEDD ADD_GATE for the DU STST, DUDT, and APUE gates.
  7. Initialize transaction dump, including loading DFHDUIO, and indicate that the dump table is available to the DUDU TRANSACTION_DUMP function.
  8. Update DU state record on catalog.
  9. Issue LMLM UNLOCK for DUDATSET lock, thereby making the transaction dump function available.

DMDM QUIESCE_DOMAIN function

The QUIESCE_DOMAIN function of the DMDM gate issues a DMDM WAIT_PHASE function request to ensure all statistics are collected.

DMDM TERMINATE_DOMAIN function

The TERMINATE_DOMAIN function of the DMDM gate issues a DUSU CLOSE request to close the transaction dump data set.

APUE SET_EXIT_STATUS function

The SET_EXIT_STATUS function of the APUE gate sets the exit status flag in the DUA for the specified exit.

STST COLLECT_STATISTICS function

The COLLECT_STATISTICS function of the STST gate is called from the statistics domain. The process flow is:

  1. Issue LMLM LOCK for DUTABLE lock on the transaction dump table.
  2. Acquire KE system dump lock.
  3. Issue STST COLLECT_STATISTICS call to DFHDUTM.
  4. Release DUTABLE lock and system dump lock.

DFHDUTM process flow

If the COLLECT_STATISTICS parameters requested DATA, the following statistics records are written to the statistics domain:

  1. If the RESOURCE_TYPE is not specified or is SYSDUMP, a DFHSDGPS global system dump statistics record is created, using global system dump counts (taken and suppressed) from the DUA. The KE system lock is released while a STATS_PUT request is made to the statistics domain. The lock is obtained again on successful completion of the STATS_PUT.
  2. If the RESOURCE_TYPE is not specified or is TRANDUMP, a DFHTDGPS global transaction dump statistics record is created, using global transaction dump counts (taken and suppressed) from the DUA. The DUTABLE lock is released while a RECORD_STATISTICS request is made to the statistics domain. The lock is obtained again on successful completion of the RECORD_STATISTICS.
  3. If the RESOURCE_TYPE is not specified or is SYSDUMP, a DFHSDRPS statistics detail record is written for every dump code found on the system dump table. The records contain the statistics for that dump code held on the dump table entry. The DFHSDRPS records are buffered and full buffers are written out using a RECORD_STATISTICS call to the statistics domain.
  4. If the RESOURCE_TYPE is not specified or is TRANDUMP, a DFHTDRPS statistics detail record is written for every dump code found on the transaction dump table. The records contain the statistics for that dump code held on the dump table entry. The DFHTDRPS records are buffered and full buffers are written out using a RECORD_STATISTICS call to the statistics domain.

The global system and transaction dump counts (taken and suppressed) in the DUA are also reset to zero. The last_reset_time is also updated in the DUA at this time.

STST COLLECT_RESOURCE_STATS function

The COLLECT_RESOURCE_STATS function of the STST gate is called from an EXEC CICS® command. The process flow is:

  1. Issue LMLM LOCK for DUTABLE lock on the transaction dump table.
  2. Acquire KE system dump lock.
  3. Issue STST COLLECT_RESOURCE_STATS call to DFHDUTM.
  4. Release DUTABLE lock and system dump lock.

DFHDUTM process flow

  1. Validate RESOURCE_TYPE for either SYSDUMP or TRANDUMP. Perform error processing and return INVALID to the caller if it is neither of these.
  2. If the RESOURCE_ID has not been passed, format a global statistics record, using counts of dumps taken and suppressed from the DUA, for either system or transaction dumps, depending on the RESOURCE_TYPE. Return this record to the caller in the RESOURCE_STATISTICS_DATA parameter.
  3. If the RESOURCE_ID is present, it should contain a dump code. Search the relevant dump table (depending on RESOURCE_TYPE). Return ID_NOT_FOUND exception to the caller if the dump code cannot be found. If the dump code is found, format either a DFHTDRPS or a DFHSDRPS statistics record using the dumps taken and suppressed statistics on the dump table entry. This record is formatted in the next available space in the RESOURCE_STATISTICS_DATA buffer.
[[ Contents Previous Page | Next Page Index ]]