Previous Topic: DISPLAY STORAGE

Next Topic: DISPLAY VERSION

DISPLAY TRACE

Use the DISPLAY TRACE command to see what type of trace information is being sent to CA‑GSS' ISRVLOG data set.

Syntax

Use this format for the DISPLAY TRACE command:

Display Trace

Example

----------------------- CA‑GSS/ISERVE Control Panel ------ ROW 1 TO 3 OF 3 ==> display trace => PAGE Target node: * ssid: * Host node: B1MAIN ssid ISRV ============================================================================= FAILed to run: ON SPACE usage: ON imod LOAD: ON imod SCHEDuled: ON member ALTER: ON RESULT: OFF DEBUG: ON SUBCALL: OFF

Fields in the Example

FAILed to run

Indicates whether or not trace output is recorded for each IMOD that is requested but not available.

SPACE usage

Indicates whether or not an IMOD's memory use is recorded when it ends. CA‑GSS always traces IMODs that do not release all memory.

imod LOAD

Indicates whether or not an IMOD's location and length are recorded when the IMOD is loaded or is replaced with a new copy.

imod SCHEDuled

Indicates whether or not trace output is recorded for each IMOD that is scheduled for execution.

memory ALTER

Indicates whether or not trace output is recorded when storage is altered due to use of the MEMORY() function.

RESULT

Indicates whether or not an IMOD's return value is recorded when an IMOD ends and returns a non-null string.

DEBUG

Indicates whether or not various internal debugging data (useful to CA Technologies Support) is recorded.

SUBCALL

Indicates whether or not each subroutine call to an external IMOD is traced.

Usage Notes

You can use the TRACE initialization parameter or the TRACE command to determine what trace output is sent to the ISRVLOG data set.