CA-GSS/ISERV Commands › CA-GSS/ISERVE Operator Commands › TRACE

TRACE

Use the TRACE command to change the current setting of the TRACE flags.

Syntax

Use this format for the TRACE command:

TRACE {ALTer}    {ON|OFF}
      {DEBug}
      {FAILed}
      {LOCation}
      {RESult}
      {SCHEDule}
      {SPACE}
      {SUBcall}

Parameters

The TRACE command takes these parameters.

ALTer

Causes a trace entry on ISRVLOG for each use of the MEMORY() function that alters storage.

DEBug

Causes a trace entry on ISRVLOG of various internal debugging data. This information is useful to CA Technologies Support.

FAILed

Causes a trace entry on ISRVLOG for each IMOD that fails during scheduling.

LOCation

Causes a trace entry on ISRVLOG each time an IMOD is loaded or replaced with a new copy. This IMOD's location and length will be traced.

OFF ON

Disables or enables tracing of the event.

RESult

Causes a trace entry on ISRVLOG at the conclusion of each IMOD that returns a non-null string. The value returned by the IMOD is recorded.

SCHEDule

Causes a trace entry on ISRVLOG for each IMOD task that is scheduled.

SPACE

Causes a trace entry on ISRVLOG at the conclusion of each IMOD, listing the IMOD's memory use. IMODs that do not release all memory are always traced.

SUBcall

Causes a trace entry on ISRVLOG of each call to an external subroutine (IMOD).

Example

------------------------ CA‑GSS/ISERVE Control Panel --------------------------
==> trace debug sched sub on                                           => 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 a trace entry is being made to ISRVLOG for each IMOD that is requested but not available.

SPACE usage

Indicates whether a trace entry is being made to ISRVLOG at the conclusion of each IMOD, listing the IMOD's memory utilization. IMODs that do not release all memory are always traced.

imod LOAD

Indicates whether a trace entry is being made to ISRVLOG each time an IMOD is loaded or replaced with a new copy. This IMOD's location and length will be traced.

imod SCHEDuled

Indicates whether a trace entry is being made to ISRVLOG each time an IMOD is schedule for execution.

member ALTER

Indicates whether a trace entry is being made to ISRVLOG for each use of the MEMORY() function to alter storage.

RESULT

Indicates whether a trace entry is being made to ISRVLOG at the conclusion of each IMOD that returns a non-null string. The value returned by the IMOD is recorded.

DEBUG

Indicates whether a trace entry is being made to ISRVLOG of various internal debugging data. This information is useful to CA Technologies Support.

SUBCALL

Indicates whether a trace entry is being made to ISRVLOG each time an IMOD makes a subroutine call to another IMOD.