1—function traces

The Function Traces option on the Traces panel is used to establish criteria for recording the names of dialog service calls, the service parameters, and return code in the ISPF log. If either a dialog or Dialog Test processing causes a service call, that call is recorded in the trace. An example of Dialog Test processing that causes a service call is the use of the Panels option (7.2) to display a panel. Whenever a new application or function causes data to be recorded, a header is placed in the trace.

When you select the Function Traces option, you are shown a panel that you can scroll (Figure 1). The pop-up window can also be resized using the RESIZE command. The panel lists all currently defined function traces.

You can add, delete, and change function trace definitions by using this panel, either before calling a function or at a breakpoint.

Figure 1. Function traces panel (ISPYRFP)

 ┌────────────────────────────── Function Traces ──────────────────────────────┐
 │   Menu  Utilities  Help                                                     │
 │ ──────────────────────────────────────────────────────────────────────────  │
 │                                                            Row 1 to 7 of 13 │
 │                                                                             │
 │ Add, delete, and change traces.  Underscores need not be blanked.           │
 │ Enter END command to finalize changes.                                      │
 │                                                                             │
 │         Function    Active       Dialog services to be traced               │
 │        (Required)  (YES,NO)     (No entry=all)                              │
 │                 (No entry=YES)  ("OR" is assumed between names)             │
 │                                                                             │
 │         ALL           NO                                                    │
 │                                                                             │
 │                                                                             │
 │                                                                             │
 │                                                                             │
 │                                                                             │
 │                                                                             │
 │                                                                             │
 │ Command ===>                                             Scroll ===> PAGE   │
 │  F1=Help        F2=Split       F3=Exit        F4=Expand      F5=Rfind       │
 │  F6=Resize      F7=Backward    F8=Forward     F9=Swap       F10=Actions     │
 └─────────────────────────────────────────────────────────────────────────────┘

Each line defines a function trace, showing a line command area and these fields:

Function

The name of the user function that should contain the trace, or ALL to trace every dialog function. Initially, ALL is presented on the display but is not started. Change the NO to a YES in the Active column to start such a trace. If you want to trace a function whose name is ALL, enclose the name in single quotes to distinguish it; that is, type 'ALL', not ALL.

Active

Whether the trace is to be active now:

YES: The trace is currently active.
NO: The trace is currently not active.
Blank: The trace is currently active.

Dialog services to be traced

Names of dialog services to be traced. No entry in this field shows all calls to dialog services for the function are to be traced.

All function traces exist until you leave Dialog Test, or until you delete them from this panel. Enter new information by typing over the existing data. The underscores are pad characters to show the starting and ending positions for each field; you do not need to blank them out. You can create several function traces before you press the Enter key.

During dialog processing, to determine whether the criteria for a function trace have been met, Dialog Test processes a logical AND of the Function, Active, and Dialog services fields specified for that function trace. Dialog Test also processes a logical OR within the Dialog services field to determine whether a particular dialog service has been matched. Therefore, if you want more than one trace for a function, you should create multiple rows.