Limited supportBMC 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 CMF 6.3.

TRACE

The TRACE control statement invokes the trace facility of the CMF MONITOR Extractor.

TRACE
[SAMPLE={60|nn}]
[,SRB={NO|YES}]
[,SYSEVENT=(n1,...,n6)]
[,ASID=asid]
[,ID=0|n]
[,NAME=jobname]

The trace facility uses the following sampling methods:

  • SRB—schedules a user-written SRB routine at specified intervals

    A default SRB routine, CX10UMOD, is located in the CMF MONITOR BBSAMP data set.

  • SRM—allows you to trace specified SYSEVENTs

    A trace for a SYSEVENT includes the name of the job for which the SYSEVENT was issued, along with the parameter registers, zero and one. TSEVENT (SYSEVENT zero) includes the TSO command name.

Monitoring modes

One TRACE statement can be specified for each monitoring mode, continuous (CPM) or intermittent (IPM).

Sampler and record types

The TRACE statement controls the TRCE sampler, which produces CMF type 240-18 user records.

Analyzer statements and reports

TRACE

Trace Report

Other BMC Software products

The TRACE control statement is used by the CMF MONITOR Extractor only.

Parameters

Parameters for the TRACE control statement are as follows:

SYSEVENT=

lists 1 to 6 SYSEVENTs that are to be traced

If nothing is specified, the SYSEVENT trace is suppressed. Valid SYSEVENT IDs are 0 through 79. A specification of SRB=NO and no SYSEVENTs results in an error.

Note

SYSEVENT data is traced for all address spaces, unless a NAME or ASID parameter is specified.

ID=

specifies the trace ID to be assigned to the SYSEVENT trace records

The default is zero, which signifies that each SYSEVENT trace record is to be identified with the SYSEVENT ID. If ID is specified, all SYSEVENT trace records receive that ID.

Note

The ID parameter is ignored if no SYSEVENT parameter is defined.

NAME=

specifies the name of the batch job, Started Task, or TSO logon ID for which SYSEVENT data is to be traced

The NAME parameter is invalid if ASID is defined.

Note

The NAME parameter is ignored if no SYSEVENT parameter is defined.

ASID=

specifies the address space identifier for which SYSEVENT data is to be traced

ASID is invalid if NAME is used.

Note

The ASID parameter is ignored if no SYSEVENT parameter is defined.


Examples

Example
TRACE  SAMPLE=1,SRB=YES

This example invokes the trace sampler; a user SRB is scheduled every second.

Example
TRACE  SRB=NO,SYSEVENT=(0,8,9,15,20,21),NAME=TSOUSER

This example invokes the trace sampler with the SRM option. The following SYSEVENTs are traced for TSOUSER:

  • 0—PPMODE
  • 8—job select
  • 9—job termination
  • 15—swap-out complete
  • 20—enqueue hold
  • 21—enqueue release

Each trace entry has the ID of the SYSEVENT number.

Example
TRACE  SAMPLE=10,SRB=YES,SYSEVENT=15,ID=77,ASID=10

This example invokes the trace sampler with both the SRB and SRM options. The user SRB is scheduled every 10 seconds. The swap-out complete system event (SYSEVENT 15) is traced for address space 10, and the trace record (SMF 240-18) is given an ID of 77.

 

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