Enabling tracing or performance tracing for the Data Streamer at startup

For certain problems, IBM® Software Support might request that you enable tracing or performance tracing for the Data Streamer at startup by modifying the trace parameter in startup task.

Procedure

  1. Modify the trace parameter in the Data Streamer startup task as shown in the following example.
    • To enable tracing:
      //STDPARM  DD *                              
       PGM /bin/sh                                  
       /usr/lpp/IBM/zcdp/v5r1m0/DS/LIB/startup.sh   
       /usr/lpp/IBM/zcdp/v5r1m0/UI/LIB/Sample.policy
       nnnnn start=w trace=y
    • To enable performance tracing:
      //STDPARM  DD *                              
       PGM /bin/sh                                  
       /usr/lpp/IBM/zcdp/v5r1m0/DS/LIB/startup.sh   
       /usr/lpp/IBM/zcdp/v5r1m0/UI/LIB/Sample.policy
       nnnnn start=w trace=p
      Important: For the Data Streamer, performance tracing data shows the data flow of packets between Threads including Listener, Hopper, Worker and Sender. From the tracing data, you can see the activities of packets between Threads and the size of packets. Performance tracing (trace=p) is not as heavy as regular tracing (trace=y), but usually it is sufficient to determine an issue.
  2. Start the Data Streamer for the trace option to take effect.
  3. Verify that appropriate messages are written in the STDOUT data set.

Results

The tracing output is in the STDOUT data set of the Data Streamer started task.

What to do next

Disable tracing in either of the following ways:
  • Set trace=n and recycle the Data Streamer started task.
  • Run the following command:
    F HBODSPRO,APPL=CLEAR,TRACE