Parameters

The parameters for SETGTZ DEBUG are:

ACTION=ABEND

For matching GTZTRACK requests, the system triggers a non-percolating ABEND with system completion code X'E77' and with a reason code as specified by REASON. This action is recommended when a matching track request is made when SLIP processing is available, since SLIP allows a number of actions for when this ABEND is trapped, including creating an SVC dump. For example:

SLIP SET,ENABLE,ID=TRAK,COMP=E77,REASON=34,ACTION=SVCD,END

If no SLIP is set, an entry in LOGREC will be made, but no dump will be taken.

To help identify the occurrence of what is being tracked, the following registers at the time of the abend will contain the information shown:

R2: The address of the GTZTRACK parameter list. See the program listing of the GTZTRACK invoker for a mapping.
R3: The HOME-ASID of the GTZTRACK caller.
R4: The eight characters of the HOME-jobname of the GTZTRACK caller.
R5: The eight characters of the event-jobname, associated with the EVENTASID parameter of the GTZTRACK request.
R6: The eight characters of the PROGRAM name as derived from the EVENTADDR parameter of the GTZTRACK request, or the address of the derived PROGRAMPATH.
R7: The program OFFSET as derived from the EVENTADDR parameter of the GTZTRACK request.

ACTION=DUMP

For matching GTZTRACK requests the system triggers a percolating ABEND with system completion code X’E77’ and with a reason code as specified by REASON. A dump according to the current job’s DUMP options will be created. This action is only recommended when a matching track request is made and SLIP processing is not available yet, otherwise ACTION=ABEND is recommended.

See ACTION=ABEND for special register contents being set by the system.

REASON=user-reason-code

Specifies which reason code to tag the debug action with.

The reason code:

has to be in the range of 0000x - 0FFFx.
can be specified in hexadecimal format, for example as X'02C1' or 02C1x or '02C1'X or x2C1.
can be specified in decimal format, for example as 705.

LIMIT=(action-limit|NOLIMIT)

Requests that this DEBUG statement should not trigger more than action-limit number of debug actions of the specified kind for all future, matching GTZTRACK requests. The limit has to be in the range of 1 - 65535 or NOLIMIT has to be used.

Once the limit has been reached and you want to "reset" the limit to allow additional debug actions in the future, IBM recommends to use the CLEAR DEBUG command and then to add any DEBUG statement(s) again. You can combine this in a separate GTZPRMxx parmlib member and use the SET GTZ=xx command to have the tracking facility process these statements.

filter

Any new tracked instance which matches the whole filter (all the filter pieces, OWNER, SOURCE,... match their GTZTRACK based counterparts) and has not reached its limit yet will trigger the requested DEBUG action.

See Parameters for more information.