Information
Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Monitor for Db2 13.1 image-2024-5-19_8-5-1.png .

Start DB2 Trace Request dialog


The initial Start Db2 Trace Request dialog displays a default request for a summary trace, as shown in the TYPE field of the following figure:

                             Start DB2 Trace Request
  COMMAND ===>                                              SCROLL ===> PAGE  
                                                                             
                                                            Target DEEH       
  Trace Attributes:                                                           
  PARM             (Trace Identifier)     START          (hh:mm:ss)           
  TYPE    S        (S-Summary,D-Detail)   STOP           (hh:mm/mins)         
                                                                             
  STORAGE 1000K    (Display Buffer Size)  WRAP  YES      (Y/N wrap buffer)    
  LOGTRAC Y        (Y/N log trace)        RST   HOT      (HOT,PUR,QIS)        
                                                                             
  TITLE   Db2 APPLICATION TRACE                                               
                                                                             
  Specify additional trace options: (*-processed)                             
   Selection Criteria           N  (Y/N)                                      
   Exception Filters            N  (Y/N)                                      
   Detail Trace Options         N  (Y/N)                                      
   Trace Log Data Set Options   N  (Y/N)                                      
                                                                             
   Additional Trace Targets     N  (Y/N)   Context

The Start Db2 Trace Request dialog provides access to additional dialogs that enable you to override default settings such as:

  • Selection criteria - to select the threads to be traced
  • Exception filters - to reduce the amount of data saved
  • Detail trace options - to trace additional events
  • Trace log data set options - to specify additional data set allocation and processing options
  • Additional trace targets - to start the same trace for multiple targets

The following table describes the trace request keywords.


Keyword

Operand/Description

PARM

id

If you want to run multiple trace requests, specify an ID in the PARM field to make the trace unique. The identifier is used to specify which set of trace data is to be displayed with the application trace services.

Warning

Note

Blanks can be used as an identifier for one trace, but BMC does not recommend this usage.

TYPE

S | D

S (the default) requests a summary application trace of completed transactions. D requests a detail application trace that also collects major events in the life of the transaction.

STORAGE

n

Warning

Note

In windows mode, display storage is managed by BMC AMI Ops Infrastructure; the STORAGE keyword is not used.

For full-screen trace displays, this value determines the size of the online trace display buffer to contain the trace entries per active trace. The size is specified in K format, where K is the number of 1024 byte blocks; for example, 200K is

200*1024=204800 bytes

This value is primed from the default specified in DMRBEXxx. If no value is specified, the value from BBIISPxx is used.

For a detail trace, this value must be at least four times TRSIZE. If the specification is less than four times TRSIZE, it will be adjusted upward to the maximum of 16383K.

LOGTRAC

N | Y

This value specifies whether to write all trace records for this request to a unique trace log data set (TLDS) for this trace. If Y is specified with no additional summary or detail trace logging options, a single data set is allocated dynamically using the defaults specified in DMRBEXxx for this Db2.

Warning

Note

The BBI-SS PAS started task user ID must be authorized to use dynamic allocation.

TITLE

c...c

This value defines a title for the trace (1 to 24 characters). If you are logging the trace, BMC recommends that you specify a more specific title to help identify the contents of this trace at a later time.

Warning

Notes

  • Special characters are not valid.
  • Only blanks are valid as separators.

START

hh:mm:ss

This value requests trace start time. If the time specified is more than 10 minutes prior to the current time, 24 hours are added to the specified time and the request is started the next day. To start a request at midnight, specify 24:00:00.

The default is the next full minute.

STOP

nnn | hh:mm:ss

This value requests trace stop limit as a timestamp or number of minutes to process. The default is set from TRTIME in DMRBEXxx.

Processing ends at the end of the last interval before the specified stop time. This time is displayed in the STOP field when the request is viewed with the R, P, M, and W line commands from the CT view.

WRAP

Y | N

The buffer is used in a wraparound method to store the entries and the wrap can be automatic, WRAP=Y (default), or user-controlled, WRAP=N.

RST

HOT | PUR | QIS

This value defines the restart option to be used when a service is quiesced because of an inactive Db2 subsystem or BLK=RRR (restart all monitors) request, as follows:

  • HOT restarts the trace automatically without the loss of previous data.
  • PUR purges the trace automatically when the target Db2 terminates.
  • QIS keeps the trace in a quiesced state until it is purged by an authorized user.
Warning

Note

For dynamic or auto-connected targets, all traces are purged when the target terminates; the RST setting is ignored.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Monitor for Db2 12.2