Inspect Manual

Using Inspect With TAL and pTAL
Inspect Manual—429164-006
13-13
MODIFY
MODIFY

To modify a string data item, use the subscript range form:
-TALOBJ-MODIFY x^string [0:10] := "abcdefghij"

You can specify the name of a structure in a MODIFY WHOLE command, but
Inspect requires that you include the new values in the command. MODIFY does
not prompt for values when you use the WHOLE clause.

As in TAL and pTAL, you can MODIFY a variable that is equated to another
variable.

As in TAL and pTAL, you can apply a subscript to a data item that is not declared
to be an array.
SCOPE

In TAL, the scope of an identifier is always the name of the procedure (not
subprocedure) or data block in which the identifier is declared. TAL and pTAL
provide the ##GLOBAL data block for all global variables that are not declared in a
named block or a private block.

If you have identifiers of the same name in different scope units, be sure that you
qualify the identifiers enough for Inspect to distinguish them.
SET RADIX
Even if you set your input radix to hexadecimal, you must still prefix a hexadecimal
value with a zero (or %H) if its first digit is above nine; otherwise, Inspect interprets the
value as an identifier.
STEP

The STEP command defaults to STATEMENTS if no code-unit is specified.

The STEP command requires caution if CASE statements or FOR loops are in the
path. The stepping behavior of these two statements is unexpected.
Remember that a CASE selects one statement from a set of statements,
depending on the value of a numeric expression. A STEP of one statement from
the beginning of a CASE statement takes you to the end of the entire CASE
statement. A subsequent STEP of one statement will take you to the selected
case or default statement.
If your process is at the beginning of a single-statement FOR loop (the loop body is
a single statement, not a block), entering STEPþ1S gets you to the beginning of
the single statement, and entering STEPþ2S completes execution of the loop.

By default the STEP command steps over procedure and subprocedure calls. In
IN option can be used to step into calls made to procedures/subprocedures that
are contained in the user code or the user library.