Inspect Manual

High-Level Inspect Commands
Inspect Manual—429164-006
6-97
Default Values
BOTH
instructs the ICODE command to list the correspondence between TNS and
TNS/R instructions for accelerated programs. Refer to the examples for more
details. The BOTH option does not show TNS/E instructions for an OCA
process on a TNS/E system.
Default Values

INSTRUCTIONS are assumed if no unit is specified and an address expression is
specified.

STATEMENTS are assumed for non-COBOL programs if no unit is specified and a
source-level location is specified using the AT clause.

VERBS are assumed for COBOL and COBOL85 programs if no unit is specified
and a source-level location is specified using the AT clause.

A count of one is assumed if no count is specified.

By default, this command lists TNS instructions, unless the BOTH or TNS/R
options are specified.

As with the SOURCE command, pressing RETURN immediately after an ICODE
command has been issued will repeat the ICODE command, starting at the
location following the last location listed.
Output

TNS addresses are output in 5-digit octal with a leading “%”.

TNS/R addresses are output in 8-digit hexadecimal with a leading “%h”.

When listing TNS/R call instructions (JAL and JR) the name of the target
procedure or millicode routine is listed.

When a source location is specified, output includes line and/or statement numbers
(depending on the current LOCATION FORMAT).

The BOTH report lists the correspondence between TNS and TNS/R instructions in
a vertical format. It lists a block of TNS instructions and the corresponding block of
TNS/R instructions. Memory-exact points determine the block boundaries. In
output, blocks are separated by a blank line or a line/statement number (if
applicable). This output is illustrated in the examples section.

For accelerated programs, instructions are annotated in the standard way to mark
memory-exact and register-exact points, a “>” and an “@”, respectively.

Since procedure names may be up to 255 characters in length, strings listed for
some call instructions may overflow the allocated field width. If the string will fit on
the current output line, it is allowed to overflow into subsequent fields as
necessary. If not, it is output at the beginning of the next line and folded across as
many lines as necessary.