DEBUG Subcommands-DEFINE DEFINE Use the DEFINE subcommand to assign a symbolic name to a specific
storage address. Once a symbolic name is assigned to a storage address
r that symbolic name can be used to refer to that address in any of the
other DEBUG subcommands. The format of the DEFINE subcom.and is: .- I I DEFine symbol hexloc .- , Ibytecountl I I I I L .J L- symbol
hexloc
bytecoun t
is the name to be assigned to the storage address derived from
the second operand r hexloc. Symbol may be from one to eight
characters long r and must contain at least one nonhexadecimal
character. Any symbolic name longer than eight characters is
left-justified and truncated on the right after the eighth
character.
is the hexadecimal storage location
r in relation to the
current origin r to which the name specified in the first
operand (symbol) r is assigned.
is a decimal number
r between and 56 inclusive
r which
specifies the length in bytes of the field whose name is
specifed by the first operand (symbol) and whose starting
location is specified by the second operand (hexloc). When bytecount is net specified
r 4 is assumed. 1. Issuing the DEFINE subcommand creates an entry in the debug symbol
table. The entry consists of the symbol name
r the storage address
r and the length of the field. A maximum of 16 symbols can be
defined in the debug symbol table at any given time.
2. When a DEFINE subcommand specifies a symbol that already exists in
the debug symbol table, the storage address derived from the
current request replaces the previous storage address. Several
symbols may be assigned to the same storage address
r but each of
these symbols constitutes one entry in the debug symbol table. The
symbols remain defined until they are redefined or until an IPL
subcommand loads a new copy of CKS. 3. When you assign a symbolic name to a storage location
r you must
know the current origin (set by the ORIGIN subcommand). The hexloc
you specify is added to the current origin to create the entry in
the symbol table used by DEBUG subcommands. If you change the
current origin, existing entries are not changed.
4. You can use symbolic names to refer to storage locations when you
issue the DEBUG subcommands BREAK r DUKP, GO, ORIGIN, STORE, and X. None.
Section 4. DEBUG Subcommands 267

DEBUG DUMP Use the DUMP subcommand to print part or all of your virtual storage on
the printer. The requested information is printed offline as soon as
the printer is available. First, a heading:
ident FROM starting location TO ending location
is printed. Next r the general registers 0-7 and 8-15, and the
floating-point registers 0-6 are printed, followed by the PSW, CSW, and CAW. Then the specified portion of virtual storage is printed with the
storage address of the first byte in the line printed at the left,
followed by the alphameric interpretation of 32 bytes of storage. The
format of the DUMP subcommand is: r I I DUmp , , , , L- symboll
hexlocl
sy mbol2
hexloc2
*
ident ---, r r , , , svmbol1 , symbo12 , , , hexloc1 I hexloc2 ( ident ] I , , Q , * I , , , II I , , L L J J , -I is the name assigned (via the DEFINE subcommand) to the
storage address that begins the dump.
is the hexadecimal storage location, in relation to current
origin r that begins the dump.
is the name assigned (via the DEFINE subcommand) to the
storage address that ends the dump.
is the hexadecimal storage location, in relation to the
current originr that ends the dump.
indicates that the dump ends at your virtual machine's last
virtual storage address.
is any name (up to eight characters) that identifies the dump.
1. If you issue the DUMP subcommand with no operands
r 32 bytes of
storage are dumpedr starting at the current origin.
2. The first and second operands must designate storage addresses that
do not exceed your virtual machine storage size. Also, the storage
address derived from the second operand must be greater than the
storage address derived from the first operand.
None. 26R IBM CMS Command and Macro Reference