z/OS DFSMSdfp Diagnosis
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Starting the record management trace function

z/OS DFSMSdfp Diagnosis
SC23-6863-00

There are two methods for starting the R/M trace function:
  • Using PARMLIB member IDAVDTxx and started task IDAVDT.
  • Using AMP=('TRACE=(subparameters)') on the DD card of the JCL. Note that this method has several limitations: It does not support dynamically allocated data sets, cannot be enabled dynamically and requires that you take down the application to insert trace parameters and open the data set before the trace can be enabled.

With either method, begin as follows:

  1. Review the GTF reserved common storage buffer size to ensure that the buffer is large enough to hold the resulting trace records. The default size is 40K. IBM® recommends that you increase it to at least 1024K. Refer to z/OS MVS System Commandsz/OS MVS System Commands for information on how to define GTF reserved common storage buffer.
  2. Activate GTF on your system. When you start GTF, specify USR or USRP with an AM01 event identifier, which is X'FF5'. If neither USR or USRP is specified, GTF ignores the data passed to it by trace.

Then complete the tasks for the method you choose, as described in Using PARMLIB member IDAVDTxx and IDAVDT and Using AMP=('TRACE=(subparameters)') in the DD card.

When tracing catalogs opened in the Catalog address space, you must issue this command to allow tracing to start:
F CATALOG,CLOSE(catalogname)

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014