CTRACE - RESOLVER

Component Trace (CTRACE) is used for the RESOLVER component (SYSTCPRE) to collect debug information. The TRACE RESOLVER traces information about a per-application basis and directs the output to a unique file for each application. The CTRACE shows resolver actions for all applications (although it might be filtered).

The CTRACE support allows for JOBNAME, ASID filtering, or both. The trace buffer is located in the Resolver private storage. The trace buffer minimum size is 128K, maximum 128M, default 16M. Trace records can optionally be written to an external writer.

The Resolver CTRACE initialization PARMLIB member can be specified at Resolver start time. Using the sample Resolver procedure shipped with the product, enter the following console command:

S RESOLVER,REUSASID=YES,PARMS='CTRACE(CTIRESxx)'

where xx is the suffix of the CTIRESxx PARMLIB member to be used. To customize the parameters used to initialize the trace, you can update the SYS1.PARMLIB member CTIRES00.

Note: In addition to specifying the trace options, you can also change the Resolver trace buffer size. The buffer size can be changed only at Resolver initialization.

If the CTIRES00 member is not found when starting the Resolver, the following message is issued:

IEEE538I CTIRES00 MEMBER NOT FOUND in SYS1.PARMLIB

When this occurs, the Resolver component trace is started with a buffer size of 16MB and the MINIMUM tracing option.

After Resolver initialization, you must use the TRACE CT command to change the component trace options (see TCP/IP services traces and IPCS support). Each time a new component trace is initialized, all prior trace options are turned off and the new options are put into effect.

Trace options:

ALL: The standard set of CTRACE options for tracing resolver processing.
Rule: The TRACERES option is not included.
MINIMUM: The minimum set of options traces exceptions, Resolver initialization and termination, Resolver CTRACE changes, and Resolver operator messages.
TRACERES: Collects Trace Resolver information as Resolver CTRACE records.

The following sample shows the PARMLIB member. End of change

/*********************************************************************/ 
/*                                                                   */ 
/*  IBM Communications Server for z/OS                               */ 
/*  SMP/E Distribution Name:  CTIRES00                               */ 
/*                                                                   */ 
/*  PART Name:  CTIRES00                                             */ 
/*                                                                   */ 
/*                                                                   */ 
/*  Copyright:                                                       */ 
/*                Licensed Materials - Property of IBM               */ 
/*                5694-A01                                           */ 
/*                (C) Copyright IBM Corp. 2001, 2003                 */ 
/*                                                                   */ 
/*                                                                   */ 
/*  Status:       CSV1R5                                             */ 
/*                                                                   */ 
/*                                                                   */ 
/*  DESCRIPTION = This parmlib member causes component trace for     */ 
/*                the TCP/IP provided Resolver to be initialized     */ 
/*                with a trace buffer size of 16M                    */ 
/*                                                                   */ 
/*                This parmlib member only lists those TRACEOPTS     */ 
/*                values specific to the TCP/IP Resolver. For a      */ 
/*                complete list of TRACEOPTS keywords and their      */ 
/*                values see:                                        */
/*                z/OS MVS INITIALIZATION AND TUNING REFERENCE.      */
/*                                                                   */
/*                                                                   */
/* $PARMS(CTIRES00),COMP(RES ),PROD(TCPIP ): Resolver Component Trace*/
/*                                           SYS1.PARMLIB member     */
/*                                                                   */
/*********************************************************************/
 TRACEOPTS                                                             
 /* ---------------------------------------------------------------- */
 /*   Optionally start external writer in this file (use both        */
 /*   WTRSTART and WTR with same wtr_procedure)                      */
 /* ---------------------------------------------------------------- */
 /*        WTRSTART(wtr_procedure)                                   */
 /* ---------------------------------------------------------------- */
 /*   ON OR OFF: PICK 1                                              */
 /* ---------------------------------------------------------------- */
           ON                                                          
 /*        OFF                                                       */
 /* ---------------------------------------------------------------- */
 /*   BUFSIZE: A VALUE IN RANGE 128K TO 128M                         */
 /*             CTRACE buffers reside in Resolver Private storage    */
 /*             which is in the regions address space.               */
 /* ---------------------------------------------------------------- *
           BUFSIZE(16M)                                               
 /*        JOBNAME(jobname1,...)                                     */
 /*        ASID(Asid1,...)                                           */
 /*        WTR(wtr_procedure)                                        */
 /* ---------------------------------------------------------------- */
 /*   OPTIONS: NAMES OF FUNCTIONS TO BE TRACED, OR "ALL"             */
 /* ---------------------------------------------------------------- */
 /*        OPTIONS(             */                                    
 /*                'ALL     '   */                
 /*                'TRACERES'   */                                    
 /*               ,'MINIMUM '   */                                    
 /*                )            */

When formatting the Resolver trace, use the CTRACE command. See TCP/IP services traces and IPCS support for the syntax for formatting a CTRACE. For the Resolver, the following formatting OPTIONS are available:

ASCII: Resolver trace data is displayed with ASCII translation only. The default is EBCDIC.
BOTH: Resolver trace data is displayed with both EBCDIC and ASCII translations. Each line of formatted data contains the offset, the hexadecimal display, the EBCDIC translation, then the ASCII translation. The default is EBCDIC.
EBCDIC: Resolver trace data is displayed with EBCDIC translation only. This is the default.
HEX: Resolver trace data is displayed only in hexadecimal (no ASCII or EBCDIC translation). The default is EBCDIC.

Guidelines:

If the formatted CTRACE display wraps on the screen, use the IPCS PROFILE LINESIZE(nn) command, where nn is the largest number of characters that displays on one line.
The choice of ASCII or EBCDIC translation does not apply to CTRACE TRACERES records.