The following table gives an overview of all the KDCDUMP statements and their meanings:
Statement | Meaning |
! | Interrupt KDCDUMP and execute system command |
!! | Execute most recently executed system command again |
AFIND | Find address in UTM dump |
scrolling statements | Position cursor in work area |
DUMP | Read complete UTM dump or part of a UTM dump into memory |
EDT | Call editor |
END | Terminate KDCDUMP |
FIND | Find and show table entry |
FGG | Edit all files of an FGG (file generation group) |
FILE | Edit single dump file |
HELP | Display help for KDCDUMP statements |
LIST | Edit table section |
REPFILE | Information about REP file (only BS2000 systems) |
SFIND | Search for a pattern in the dump |
SH | SYS | Start a Bourne shell from KDCDUMP on Unix and Linux systems or open a command prompt window under Windows systems ( |
SYSLST | Activate/deactivate logging |
TABLE | Show table |
Entering KDCDUMP statements
KDCDUMP statements are read from stdin
. A statement may comprise up to 256 characters; longer inputs result in error message K759.
Where statement names can be abbreviated, this is indicated in bold type. Thus, for example AFIND, indicates that you can abbreviate the statement name to AF.
With certain operands, one of the three input formats "C-string", "X-string" or "decimal" must be observed:
Designation | Input format / Example |
C-string | [C]'This is a C-string' |
X-string (hexadecimal) | X'AAAF' or X'aaaf' or X'AaAf' |
Decimal | 12345 |
If indices or displacements/offsets are specified, then these are always interpreted as being positive.
Note for openUTM on Unix, Linux and Windows systems on Intel processors
Hexadecimal inputs are always interpreted as arithmetic, i.e. indices or displacements which are read directly from the hexadecimal edited dump must be entered byte for byte in the reverse order, i.e. as arithmetic, for "little endian" machines (e.g. Intel). Generally, it is unnecessary to enter leading zeros.
Little endian examples
The
The
In the following, "output to terminal" signifies the output to stderr.
The sections which follow describe the KDCDUMP statements in alphabetical order. Only the statements and operands are described here which are used for evaluating the KDCROOT area (see chapter "The KDCROOT area").