KN3FCCMD START DBUG

The KN3FCCMD START DBUG command starts the writing of trace messages for the TCP/IP and VTAM® statistics collector to the log files.

Format

Where:

SNAC

Means write trace records for SNA Statistics collection.

TACC

Means write trace records for the product-specific Take Action commands issued by the IBM® Z OMEGAMON® AI for Networks command handler.

TCPC

Means write trace records for TCP/IP Statistics collections. Turning on all of the TCPC component may result in large amounts of trace data being written to the monitoring agent's job logs. To focus on the problem that you are experiencing, IBM® Software Support may ask you to specify additional parameters to only write a subset of the trace records for TCP/IP Statistics collection. Table 1 describes those additional parameters:

Table 1. Components available from subset trace records
Component	Description
APP	TCP/IP Application table
BASE	Base data collection in the KN3ACTC4 task
COMM	Common functions
CSM	CSM Storage table
EEHPR	Enterprise Extender and High Performance Routing tables
FTP	FTP sessions and transfers tables
GIF	Interface data
GGS	Stack Layer data
HASH	Hash functions
INIT	Initialization and control
IPSEC	IP filters and IP security tables
SNA	VTAM Summary Statistics table
SNMP	SNMP data collection
SYSTCP	Functions that access the real-time TCP/IP network management interface (NMI) and pass the retrieved data to the FTP and TN3270 data collection routines. For more information about the real-time interface, see the IBM z/OS Communications Server: IP Programmer's Guide and Reference.
TCON	TCPIP Details table and TCP Connections data stored in the TCPIP Connections table
TLIS	TCP Listener table and TCP Listener data stored in the TCPIP Connections table
TSTO	TCPIP Memory Statistics table
TN32	TN3270 Server Sessions Avail and TN3270 Response Time Buckets tables
UDP	UDP Connections table and UDP Connections data stored in the TCPIP Connections table
ZERT	zERT Summary data collection

debug_level

Is one of the following:

Debug level identifier	Meaning
MIN	Trace data is captured only when an error is detected.
MID	Medium-detail debugging messages are captured. These messages are used by IBM Software Support to diagnose software problems.
MAX	All trace data is captured. These messages are used by IBM Software Support to diagnose software problems.

Purpose

Starts the writing of trace messages for the TCP/IP and VTAM statistics collector to the log files. Additional trace messages will be written to sysout or spool data sets to facilitate investigation of a problem. IBM Software Support might request that you issue this command and then provide a copy of the log files. When the STOP command is issued, the component and subcomponents will capture trace information only when there is an error (MIN level).

Attention: Issuing the KN3FCCMD START DBUG command with the debug level set at MAX may result in the rapid filling of all spool volumes. When all spool volumes fill, system failure may occur.

Usage

These usages notes apply:

You must specify a component before specifying a subcomponent. If you specify a subcomponent without a component, Message KN3FC004 is issued.
When no subcomponent is specified when component is specified, the specified debug_level is applied to all subcomponents of the selected component.
When all TCPC subcomponents are enabled at the MAX debug level (either as part of one command or cumulative), warning message KN3C143W is issued indicating that a significant amount of trace data may be written to the job log.
When multiple subcomponent identifiers are specified, they are separated by spaces.
All components/subcomponents are started at the MIN debug level by default when the agent is started.
Multiple subcomponents may be specified on one command with different levels for trace defined for each component. Each START DBUG command has a cumulative effect.

Examples illustrating these usage points follow. These examples assume the default MIN level debug setting.

This command:

MODIFY procname,KN3FCCMD START DBUG TCPC BASE TN32 MAX

Results in the trace levels for the BASE and TN32 subcomponents of TCPC being set at MAX debug level. All other subcomponents of TCPC are still at the MIN debug level, and the SNAC component is at MIN debug level.

Here is sample output for this command:

KLVOP191 REPLY FROM *MASTER*:                                              
KLVOP191    'KN3FCCMD START DBUG TCPC BASE TN32 MAX'                       
KN3C070I DBUG EXTENDED DIAGNOSTICS MODE STARTED                            
KN3FC000 KN3FCCMD PROCESSING COMPLETE                                      
KLVOP191 REPLY FROM *MASTER*:                                              
KLVOP191    'KN3FCCMD STATUS DBUG'                                         
KN3AHFD3 (TCPC, BASE) KN3AHFD3 EXIT                                        
KN3C074I DBUG EXTENDED DIAGNOSTICS MODE IS ACTIVE                          
KN3C200I FOR TCPC COMPONENT, MAXIMUM TRACING IS ENABLED FOR SUBCOMPONENTS: 
KN3C201I TN32 BASE                                                         
KN3C204I DBUG STATUS DISPLAY COMPLETE                                      
KN3FC000 KN3FCCMD PROCESSING COMPLETE

This command:

MODIFY procname,KN3FCCMD START DBUG TCPC TN32 MID

Results in the trace levels for the TN32 subcomponent being set to MID, but the trace level for the BASE subcomponent is still at MAX. All other TCPC subcomponents and the SNAC component are set at MIN by default.

Here is sample output for this command:

KLVOP191 REPLY FROM *MASTER*:                     
KLVOP191    'KN3FCCMD START DBUG TCPC TN32 MID'   
KN3C070I DBUG EXTENDED DIAGNOSTICS MODE STARTED        
KN3FC000 KN3FCCMD PROCESSING COMPLETE                  
KLVOP191 REPLY FROM *MASTER*:                          
KLVOP191    'KN3FCCMD STATUS DBUG'                     
KN3C074I DBUG EXTENDED DIAGNOSTICS MODE IS ACTIVE                            
KN3C200I FOR TCPC COMPONENT, MAXIMUM TRACING IS ENABLED FOR SUBCOMPONENTS:   
KN3C201I BASE                                                                
KN3C200I FOR TCPC COMPONENT, MEDIUM TRACING IS ENABLED FOR SUBCOMPONENTS:    
KN3C201I TN32                                                                
KN3C204I DBUG STATUS DISPLAY COMPLETE                                        
KN3FC000 KN3FCCMD PROCESSING COMPLETE

This command:

MODIFY procname,KN3FCCMD START DBUG TCPC MAX

Results in the trace levels for all TCPC subcomponents being set to MAX. The trace level for the SNAC component is still set at MIN.

Here is sample output for this command:

KLVOP191 REPLY FROM *MASTER*:                
KLVOP191    'KN3FCCMD START DBUG TCPC MAX'   
KN3C070I DBUG EXTENDED DIAGNOSTICS MODE STARTED               
KN3C143W MAX DEBUG LEVEL SET FOR COMPONENT TCPC               
KN3FC000 KN3FCCMD PROCESSING COMPLETE                         
KLVOP191 REPLY FROM *MASTER*:                                 
KLVOP191    'KN3FCCMD STATUS DBUG'                            
KN3C074I DBUG EXTENDED DIAGNOSTICS MODE IS ACTIVE        
KN3C202I MAXIMUM TRACING FOR COMPONENT TCPC IS ENABLED   
KN3C204I DBUG STATUS DISPLAY COMPLETE                    
KN3FC000 KN3FCCMD PROCESSING COMPLETE