Formatting the CTRACE TRACERES option

Use the IPCS CTRACE,FULL command to format the trace regardless of whether the trace data is available in a dump or in an external data set. You can either type the CTRACE command on the IPCS command panel or use the panel interface. IPCS is also available in batch.

You can use several filters to limit the amount of formatted data. In addition to the CTRACE options such as start and stop time that IPCS provides, you can also use the following options:

JOBNAME: The job name of the application.
ASID: The address space identifier of the application.
CID: The connection identifier of the application with a specific res_init() function call. You can use CID to correlate related resolver calls from the same application.

Examples of the CTRACE TRACERES records

 1  =================================================================00000031
 2  MVSTST    TRACERES  000A0002  15:07:45.880242   Formatted Trace Resolver
 3  ASID....     0024  TCB.... 007FF320  JOBN.... USER23    CID.... 00000222
 4  Resolver Trace Initialization Complete -> 2014/01/07 15:07:45.861906

res_init Resolver values:
 Setup file warning messages = No
 CTRACE TRACERES option = Yes
 Global Tcp/Ip Dataset  = None
 Default Tcp/Ip Dataset = None
 Local Tcp/Ip Dataset   = //'SYS1.TCPPARMS(TCPDATA)'
 Translation Table      = CS390.STANDARD.TCPXLBIN
 UserId/JobName         = USER2
 Caller API             = LE C Sockets
 Caller Mode            = EBCDIC
 System Name            = MVSTST (from VMCF)
 UnresponsiveThreshold  = 25
 (L) DataSetPrefix = CS390
 (*) HostName      = MVSTST
 (L) TcpIpJobName  = TCPCS
 (L) Search        = tcp.raleigh.ibm.com
.
 (L) NsPortAddr    = 53            (L) ResolverTimeout    = 16
 (L) ResolveVia    = UDP           (L) ResolverUdpRetries = 1
 (*) Options NDots = 1
 (*) SockNoTestStor
 (*) AlwaysWto     = NO            (*) MessageCase        = MIXED
 (L) LookUp        = DNS
 (L) NoCache
res_init Succeeded
 1  =================================================================00000037
 2  MVSTST    TRACERES  000A0002  15:07:45.881099   Formatted Trace Resolver
 3  ASID....     0024  TCB.... 007FF320  JOBN.... USER23    CID.... 00000222
 4  res_init Started: 2014/01/07 15:07:45.881065
res_init Ended: 2014/01/07 15:07:45.881088
***************************************************************************
=================================================================0000003E

The following list describes highlighted numbered areas in the CTRACE TRACERES records example:

1: This separator line shows the trace record number of the previous SYSTCPRE component in hexadecimal.
2: The first data line contains the host name (MVSTST), trace option (TRACERES), trace code (000A0002), time, and trace record name. The trace record name is Formatted Trace Resolver for all CTRACE TRACERES records.
3: The second data line contains the application's ASID (0024), the MVS™ TCB address (007FF320), the application's job name (USER23), and the connection identifier (00000222).
Tip: Use the ASID, JOBN, or CID value as input for the ASID, JOBNAME, or CID filter respectively to limit the amount of trace information that is formatted.
4: The contents of a CTRACE TRACERES record that follow the CTRACE headers represent a subset of the same Trace Resolver output as described in Interpreting the Trace Resolver output. The Trace Resolver output might be collected in multiple CTRACE records. In this example, two CTRACE records are necessary to collect all the Trace Resolver outputs that the res_init() processing generates.