enoft Manual

Introduction to eNOFT and ar
eNOFT Manual527507-005
1-4
<proc-spec>
top half of the 64-bit address was not the sign extension of the bottom half, eNOFT will
give a warning message with the truncated display.
Hexadecimal numbers are prefixed with "0x".
Sizes are represented as decimal values in bytes.
All code outputs are in multiples of 16-byte bundles of instructions.
<proc-spec>
This form of argument specifies the procedure or subprocedure.
<proc-num> | procname
<proc-num> is the procedure number that is available from LISTPROC or LP on
page 2-48.
procname is the procedure name and is case-sensitive in C and C++ but not in
COBOL or pTAL. This option limits the scope to the specified procedure and its
subprocedures. Note the demangled form of the procname cannot be used because
eNOFT does not support blank spaces in the name.
New to eNOFT, a wildcard input string may be entered to search for items containing a
match to the given pattern. For SET SCOPEPROC or SSP
on page 2-6 and
DUMPPROC or DP on page 2-13, only the first item that matches the given pattern will
be shown.
For pTAL, procname.subprocname or subprocname limits the scope to the specified
subprocedure. For COBOL, subprograms beyond the second level can also be
specified.
Only the first subprocedure identified is displayed if there are multiple subprocedures
with the same name. To display other subprocedures, their fully qualified names
(procname.subprocname) must be specified.
The scope of procedures to display is determined by SET SCOPESOURCE or SSS on
page 2-7 or SET SCOPEPROC or SSP on page 2-6 if this option is not used. If no
global scope is set, all procedures are shown.
<source-spec>
Native mode object files are loosely organized in the order compilation units were
compiled into a particular object file. This organization is prevalent in the symbols for
the object file and a loose correlation can also be made for other parts of the object file.
Sometimes this organization can be taken advantage of by using the SET
SCOPESOURCE command to restrict eNOFT to looking at things related to only a
certain compilation unit. A compilation unit typically represents a single relocatable
object file specified to the compiler to form an executable object. This relocatable
object file may be derived from several source files, including preprocessed “include