KC_CREATE_DUMP allows you to create a UTM dump for diagnostic purposes (with REASON=DIAGDP) without having to abort the application run.
The dump is created by the process that initiated the KDCADMI call.
Procedure / period of validity / transaction management / cluster
The call is not subject to transaction management. It has an immediate effect. The operations initiated by the call will already have been completed when control is returned to the program unit.
The following applies in UTM cluster applications (Unix, Linux and Windows systems):
The call applies locally to the node, i.e. a UTM dump for diagnostic purposes is only generated in this node application.
KDCDIAG ("KDCDIAG - Switch diagnostic aids on and off"), DUMP operand |
Data to be supplied
Function of the call | Data to be entered in the | |||
parameter area | identification area | selection area | data area | |
Create a UTM dump | KC_CREATE_DUMP | —— | —— | —— |
Parameter settings | |
Parameter area | |
Field name | Contents |
version | KC_ADMI_VERSION_1 |
retcode | KC_RC_NIL |
version_data | KC_VERSION_DATA_11 |
opcode | KC_CREATE_DUMP |
id_lth | 0 |
select_lth | 0 |
data_lth | 0 |
Identification area | |
— | |
Selection area | |
— | |
Data area | |
— |
KDCADMI call |
KDCADMI (¶meter_area, NULL, NULL, NULL) |
Data returned by UTM | |
Parameter area | |
Field name | Contents |
retcode | Return codes |
UTM only returns the codes listed in section "Return codes".