ITRACE statement

Use the ITRACE statement to control TCP/IP runtime tracing. This statement is used primarily for diagnostic purposes.

Syntax

Rule: Specify the parameters in the order shown here.


>>-ITRACE------------------------------------------------------->

         .-SUBAGENt 1 CONFig 1 COMMAND 1 AUTODAEMON-.     
>--+-ON--+------------------------------------------+-+--------><
   |     +-SUBAGENt level---------------------------+ |   
   |     +-CONFig level-----------------------------+ |   
   |     +-COMMAND level----------------------------+ |   
   |     '-AUTODAEMON-------------------------------' |   
   |      .-SUBAGENt CONFig COMMAND AUTODAEMON-.      |   
   '-OFF--+------------------------------------+------'   
          +-SUBAGENt---------------------------+          
          +-CONFig-----------------------------+          
          +-COMMAND----------------------------+          
          '-AUTODAEMON-------------------------'

Parameters

ON

Specify ON to establish runtime tracing. If specified with no parameters, the trace defaults to CONFIG level 1, SUBAGENT level 1, COMMAND level 1, and AUTODAEMON tracing.

OFF

Specify OFF to terminate runtime tracing. If specified with no parameters, CONFIG, SUBAGENT, COMMAND, and AUTODAEMON tracing is turned off.

SUBAGENT

Turn internal trace for SNMP subagent ON or OFF.

CONFIG

Turn internal trace for configuration ON or OFF.

Restrictions:

To trace the processing of specific TCP/IP profile statements, you must specify the ITRACE statement before the profile statements in the profile data set.
You cannot specify the ITRACE statement inside a block statement. For example, do not place it within a VIPADYNAMIC/ENDVIPADYNAMIC block or a BEGINROUTES/ENDROUTES block.

COMMAND

Turn internal trace for command ON or OFF.

AUTODAEMON

Turn internal trace for the autolog subtask ON or OFF.

level

Indicates the tracing level to be established. Levels are as follows:

Levels for CONFIG
1: ITRACE for all of config
2: General level of tracing for all of config
3: Tracing for configuration set commands
4: Tracing for configuration get commands
5: Tracing for syslog calls issued by config
100: Tracing for the parser
200: Tracing for scanner
300: Tracing for mainloop
400: Tracing for commands

Levels for SUBAGENT
1: General subagent tracing
2: General subagent tracing plus DPI traces
3: General subagent tracing plus extended storage dump traces
4: All trace levels

Levels for COMMAND
1: ITRACE for all commands

Steps for modifying

To modify parameters for the ITRACE statement, use a VARY TCPIP,,OBEYFILE command with a data set that contains a new ITRACE statement.

Examples

ITRACE ON CONFIG 3
ITRACE OFF SUBAGENT

Results:

Subagent trace output is directed to the syslog daemon. This daemon is configured by the /etc/syslog.conf z/OS® UNIX file and must be active.
AUTOLOG trace output goes to the destination specified by the ALGPRINT setting in the TCP/IP cataloged procedure (TCPIPROC).
CONFIG trace output goes to the destination specified by the CFGPRINT setting in the TCP/IP cataloged procedure (TCPIPROC). If CFGPRINT is not specified in TCPIPROC, the CONFIG component dynamically allocates a ddname of CFGPRINT.
Command trace output goes to the hardcopy console log.

Usage notes