Steps for preparing CTRACE controls and resources

Before you begin

Before you start CTRACE activity for WebSphere Application Server for z/OS servers, you need to make some decisions about CTRACE controls and resources. You have the option of using default CTRACE values and resources, such as the IBM-supplied CTRACE parmlib member for WebSphere Application Server for z/OS, or you may alter default values and provide your own resources.

Why and when to perform this task

Perform the following steps to prepare CTRACE controls and resources:

Steps for this task

  1. Decide where you want to store CTRACE data. The location of trace data is set through the WebSphere variable ras_trace_outputLocation. Make a note of the value that you want to use; you will set the value later, when you start CTRACE activity.

    Note: Tips:

    • See Setting trace controls for an explanation of and default values for the ras_trace_outputLocation variable.
    • If you decide to use trace data sets, you can use existing or create new data sets now or later, as part of the WebSphere Application Server for z/OS customization process.
    • If you want the CTRACE data for each cell to go into separate data sets, use the ras_trace_ctraceParms variable described in Setting trace controls.
    • When you are installing WebSphere Application Server for z/OS, sending trace data to SYSPRINT can be helpful; however, tracing to SYSPRINT in a production environment can cause spool space to fill up quickly. For production, you can specify a different trace output location through the WebSphere variable ras_trace_outputLocation.
    • To separate trace data from other standard output messages, such as System.output.println from Java applications, you can direct CTRACE data to a separate data set. To accomplish this separation, you need to:
      • Specify a TRCFILE DD statement in the JCL start procedure (proc) for the server.
      • Set the WebSphere variable ras_trace_outputLocation to TRCFILE. Note that you may specify the TRCFILE value with or without additional variable values.

  2. Through modify commands, you have the ability to dynamically and temporarily direct trace data to SYSPRINT or TRCFILE.
    1. You can direct CTRACE data to buffers as part of normal operations.
    2. When an error occurs, you can use the modify command to send trace data to SYSPRINT or TRCFILE.
    3. Then you can use the modify command again, to dynamically reset the trace-output location
    You can complete this sequence of actions without stopping the server that is encountering the problem.
  3. Decide whether you want to accept defaults or provide other values for the following WebSphere variables. Make a note of the values that you want to use; you will set the values later, when you start CTRACE activity.
    • ras_time_local
    • ras_trace_BufferCount
    • ras_trace_BufferSize
    For defaults and valid values, see Setting trace controls
  4. Decide whether you want to use the default JCL start procedure for the CTRACE writer, or code your own JCL proc. WebSphere Application Server for z/OS provides a CTRACE writer proc named bbowtr. If you decide to provide your own CTRACE writer procedure, create the JCL start proc using the rules for source JCL for an external writer in . Place the start procedure in your system proclib.
  5. Decide whether you want to use the default CTRACE parmlib member for WebSphere Application Server for z/OS, or provide your own. The WebSphere parmlib member is named CTIBBO00. If you decide to provide your own parmlib member, create one according to the following rules, and place it in your system parmlib.
    Rules:
    • You must follow the same naming convention; that is, the name must consist of the letters CTIBBO, but you may replace the two zeroes with any two alphanumeric characters.
    • Your parmlib member must contain the following parameters:
             TRACEOPTS       WTRSTART(xxxxxx)   
         ON     /*CONNECT TO CTRACE EXTERNAL WRITER: */       WTR(xxxxxx)  

    Parameters for the CTIBBOxx parmlib member
    Parameter Required or Optional? Description
    TRACEOPTS Required and positional This parameter must be specified first.
    WTRSTART (xxxxxx) Optional This parameter automatically starts the CTRACE writer, using the specified JCL procedure.

    Alternative: You may use the operator command TRACE CT,WTRSTART=xxxxx to start the CTRACE writer. If you use this parameter in the parmlib member, and later issue the operator command, CTRACE issues an informational message to notify you that the writer already has been started.

    ON Required This parameter must be specified before component options.
    WTR (xxxxxx) Required This parameter identifies the JCL procedure to be used to start the CTRACE external writer. The specified value must match the value of the WTRSTART parameter to capture the WebSphere Application Server for z/OS trace data into a trace data set.


  6. Ensure that the DLL named BBORTSS5 is in the link-pack area (LPA).

Results

After you have made these decisions and completed preparations, you are ready to start CTRACE activities using one of the following procedures:

Related reference
Steps for starting CTRACE as part of WebSphere Application Server for z/OS customization
Steps for starting CTRACE while WebSphere Application Server for z/OS servers are active
Setting trace controls



Searchable topic ID:   ttrb_prepCTRACEcontrols
Last updated: Jun 21, 2007 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/ttrb_prepCTRACEcontrols.html

Library | Support | Terms of Use | Feedback