location

    Denotes a program region (scope) to be used for the
    interpretation of symbols that you specify without a path-name
    prefix. A location can be any of the following, unless you
    specify /CURRENT or /MODULE.

    path-name      Specifies the scope denoted by the path-name
    prefix         prefix. A path-name prefix consists of the
                   names of one or more nesting program elements
                   (module, routine, block, and so on), with each
                   name separated by a backslash character (\).
                   When a path-name prefix consists of more than
                   one name, list a nesting element to the left of
                   the backslash and a nested element to the right of
                   the backslash. A common path-name prefix format is
                   module\routine\block\.

                   If you specify only a module name and that name is
                   the same as the name of a routine, use /MODULE;
                   otherwise, the debugger assumes that you are
                   specifying the routine.
    n              Specifies the scope denoted by the routine which
                   is n levels down the call stack (n is a decimal
                   integer). A scope specified by an integer changes
                   dynamically as the program executes. The value 0
                   denotes the routine that is currently executing,
                   the value 1 denotes the caller of that routine,
                   and so on down the call stack. The default scope
                   search list is 0,1,2, . . . ,n, where n is the
                   number of calls in the call stack.
    \              Specifies the global scope-that is, the set of
    (backslash)    all program locations in which a global symbol is
                   known. The definition of a global symbol and the
                   way it is declared depends on the language.

    When you specify more than one location parameter, you establish
    a scope search list. If the debugger cannot interpret the symbol
    using the first parameter, it uses the next parameter, and
    continues using parameters in order of their specification until
    it successfully interprets the symbol or until it exhausts the
    parameters specified.