HLASM Toolkit Feature Interactive Debug Facility User's Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


General considerations

HLASM Toolkit Feature Interactive Debug Facility User's Guide
GC26-8709-07

TSO/E TEST and IDF have different command syntaxes. This section does not provide a detailed comparison of the two command sets. However, procedures are described to perform operations equivalent to those under TSO/E TEST.

The expression syntaxes are somewhat different. Instead of TSO/E TEST's "modname.csect.address" IDF uses "(modname.csect)address". The CSECT name may be omitted if the address is unique within the module. The module name may be omitted, if the address is in the qualified module, which is set by the QUALIFY command. For register specifications in expressions IDF uses "n(Rn)" instead of TSO/E TEST's "nR%+n". IDF supports the same "%" and "?" indirection operators as TSO/E TEST. However, the first indirection operator following a register specification is used to determine the size of the address in the register. For more details on expressions in IDF see Address expressions.

Some significant advantages of IDF over TSO/E TEST are:
  • IDF is a full screen debugger
  • IDF can single-step
  • IDF is easy to customize through its REXX macro capabilities.
  • IDF has a sophisticated cursor addressing support which minimizes the amount of typing you have to do. For more details see Intelligent cursor sensing.
TSO/E TEST does have some advantages over IDF:
  • TSO/E TEST has automatic symbol support for all load modules loaded.
    ASMIDF provides the following alternatives:
    • For dynamically loaded modules, the IDF DBREAK command should be used. When the module is fetched into storage, IDF will automatically load symbols.
    • The process of manually identifying extra modules in storage to IDF and loading symbols requires only two commands: MODULE CDE and LOAD SYMBOLS.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014