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 CICS Trace Request dialog.

The Trace Log Data Set Options dialog displays additional trace logging options.

Related topic

CICS-application-trace-ATRAC

---------------------- 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 following table explains the trace log data set options:

Option	Description
Number of Logs	Shows the number of allocated trace log data sets Specify more than one for continuous traces to allow for automatic switching when a log data set is full.
First Log DSN	Shows the name of the first log data set to be allocated Note The BBI-SS PAS started task user ID must be authorized to create, read, and update the specified data set. If this option is left blank, a default name is constructed as &TRPREFIX.&CICSID.&TRACEID. mmmdd. Thhmm.V01 where &TRPREFIX is your user ID or the prefix specified in BBPARM member CMRBEX00. &CICSID is the target CICS region ID. &TRACEID is the identifier specified in the PARM field on the first Start CICS Trace Request dialog. mmmdd is the current month and day. Thhmm is the current time. V01 is the required suffix. Note If a generated trace name exceeds 44 bytes, BMC AMI Ops Monitor for CICS excludes the date (mmmdd) node and, if necessary, the time (Thhmm) nodes. If quotation marks are omitted for the log data set name, the specified value is prefixed with TRPREFIX as specified in BBPARM member CMRBEX00. 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 BBPARM member CMRBEX00, you can specify TEST.V01 to allocate userid.TEST.V01. You can specify up to an 8-character suffix for the data component (see the Data DSN Suffix description in this table). However, if you want a name to be totally different from the cluster data set name, you must preallocate the data set.
Overwrite logs	Y \| N This field indicates the action to be taken when a log data set is about to be used for trace data without having been reset. Y means that existing data can be overwritten; N means that logging should be quiesced. Note This field has no effect if the data set has been reset.
Archive PROC	Contains the name of the entry in PROCLIB to archive a log data set when it is full, logging is switched to the next data set, or the trace completes normally. For more information. see the sample archive job in BBSAMP member CMRBARC in Archiving-a-trace-log-data-set.
Log switch time	hh:mm This field specifies the time an automatic log switch from the current log to the next log will occur. The value is valid only if Number of Logs > 1. Note If another log is not available at that time (status of EMPTY or RESET), the switch cannot be made.
Disposition	OLD \| NEW OLD indicates all the data sets exist and are valid trace data sets. For more information. see the sample job for allocating a trace log data set in BBSAMP member JXT011 at Defining-a-trace-log-data-set. Existing data is overwritten if Overwrite logs = Y. NEW (the 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 successfully allocated are deleted. Note If your user authorization specifies TRALLOC=NO, only OLD is accepted.
Volumes	Identifies the volume(s) to use when allocating a trace log data set You can specify up to 7 volumes. The default value specified in CMRBEX00 with the TRVOLS keyword is SYSDA. When the number of logs is 1, the data set is allocated on the first volume. When the number of logs is greater than 1, the data sets are allocated alternately on each specified volume (if there is enough space) until all data sets are allocated. 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 volume(s). Non-SMS-controlled sites must specify volume(s) to avoid an IDCAMS-defined cluster error.
Primary CYLS	Is the primary allocation in CYLS for trace log data sets The default value specified in BBPARM member CMRBEX00 with the TRCYL keyword is 3.
Data DSN Suffix	Is the suffix to be appended to the cluster DSN to make the DSN of the data component The default value specified in BBPARM member CMRBEX00 with the TRSUFFIX keyword is D.
SMS Storage Class	Is the name of the SMS Storage Class to be used when allocating this trace data set The default is specified in BBPARM member CMRBEX00 with the TRSMSSCL keyword.
SMS Data Class	Is the name of the SMS Data Class to be used when allocating this trace data set The default is specified in BBPARM member CMRBEX00 with the TRSMSDCL keyword.
SMS Management Class	Is the name of the SMS Management Class to be used when allocating this trace data set The default is specified in BBPARM member CMRBEX00 with the TRSMSMCL keyword.

Specifying trace logging options

On this page