Specifying trace logging options

This topic describes specifying trace logging options.

To specify additional trace logging options, type Y in the Trace Log Data Set Options field of the Start DB2 Trace Request dialog.

The Trace Log Data Set Options dialog (as shown in following figure) presents additional trace logging options.

---------------------- Trace Log Data Set Options -----------------------
COMMAND ===>                                              SCROLL ===> CSR

Specify trace log data set options:
Number of logs    1
First log DSN    __________________________________
             Low level qualifier of DSN must be V01
             Blank for default: BCVM.BCVDS62C.CCS1.mmmdd.Thhmm.V01
             Names without quotes will be prefixed with BCVM

Overwrite logs    Y        (Y/N) Action when all logs used
Archive PROC      ________ (Blank for none or PROCLIB member name)
Log switch time   _____    (HH:MM that a log switch is requested)

Disposition       NEW      (OLD/NEW) If NEW, specify options below

Volumes           (BAB303,BAB304,BAB305,BAB306,BAB307,BAB308)
Primary CYLS      3               SMS Storage class
Data DSN Suffix   D               SMS Data class
                                   SMS Management class

The Trace Logging Specification panel options shown in following table explains the trace log data set options:

Field	Description
Number of logs	Number of trace log data sets to be allocated For continuous traces, specify more than one. This option allows automatic switching when a log data set is full.
First log DSN	Name of the first log data set to be allocated If left blank, a default name is constructed as &TRPREFIX.&DB2ID.&TRACEID.mmmdd.Thhmm.V01: &TRPREFIX is your user ID or the prefix that is specified in DMRBEXxx. &DB2ID is the target DB2 subsystem ID. &TRACEID is the identifier that is specified in the PARM field on the first Start DB2 Trace Request panel. mmmdd is the current month and day. Thhmm is the current time. V01 is the required suffix. If quotation marks are omitted for the log data set name, the specified value is prefixed with TRPREFIX as specified in DMRBEXxx. If TRPREFIX is not specified, your user ID is used for the prefix. If quotation marks surround the name, it is allocated exactly as specified. For example, if there is no TRPREFIX specification in DMRBEXxx, you can specify TEST.V01 to allocate userid.TEST.V01. You can specify up to an eight-character suffix for the data component (see the Data DSN Suffix description in this table). If you want a name totally different from the cluster data set name, you must preallocate the data set. Warning Note If the specified prefix is longer than 8 bytes, MainView for DB2 excludes the date (mmmdd) node and, if necessary, the time (Thhmm) node.
Overwrite logs	Y \| N Action to be taken when a log data set is about to be used for trace data without having been reset: Y- existing data can be overwritten. N- logging should be quiesced. Warning Note This field has no effect if the data set has been reset.
Archive PROC	Name of the entry in PROCLIB to archive a log data set when it is full, when logging is switched to the next data set, or when the trace is completed normally See the sample archive job in BBSAMP member DZTBARC.
Log switch time	hh:mm Time an automatic log switch from the current log to the next log will occur Valid only if Number of logs> 1. Warning Note If another log is not available at that time (status of EMPTY or RESET), the switch cannot be made.
Disposition	OLD \| NEW Status of the data sets OLD indicates all the data sets exist and are valid trace data sets. (See the sample job for allocating a trace log data set in BBSAMP member JXT011.) Existing data is overlaid if Overwrite Logs = Y. NEW (default) indicates none of the data sets exist. All the data sets are allocated when the trace request is processed. If any of the data sets cannot be allocated, the trace request fails and the data sets that were successfully allocated are deleted. Warning Note If your user authorization specifies TRALLOC=NO, only OLD is accepted.
Volumes	Volumes to use when allocating a trace log data set You can specify up to seven volumes. The default value specified in DMRBEXxx with the TRVOLS keyword is SYSDA. When the number of logs is one, the data set is allocated on the first volume. When the number of logs is greater than one, the data sets are allocated alternately on each specified volume (if there is enough space) until all data sets are allocated. Warning Note A volume specification replaces any SMS class specification. However, if your data center is SMS-controlled, the volume specified may be overridden by your SMS criteria. SMS-controlled sites do not need to specify volumes. Non-SMS-controlled sites must specify volumes to avoid an IDCAMS-defined cluster error.
Primary CYLS	Primary allocation in CYLS for trace log data sets The default value specified in DMRBEXxx with the TRCYL keyword is 3. Warning Note Allocating a very large data set (with several hundred cylinders) can cause a delay because of formatting by VSAM. In this case, specifying a preallocated and preformatted log data set is preferable.
Data DSN Suffix	Suffix to be appended to the cluster DSN to make the DSN of the data component The default value specified in DMRBEXxx with the TRSUFFIX keyword is D.
SMS Storage class	Name of the SMS Storage Class to be used to allocate this trace data set The default is specified in DMRBEXxx with the TRSMSSCL keyword.
SMS Data class	Name of the SMS Data Class to be used when allocating this trace data set The default is specified in DMRBEXxx with the TRSMSDCL keyword.
SMS Management class	Name of the SMS Management Class to be used to allocate this trace data set The default is specified in DMRBEXxx with the TRSMSMCL keyword.

Specifying trace logging options

MainView for DB2 6.1

On this page